Professional Documents
Culture Documents
SAP New GL Activation and Migration From Classic GL
SAP New GL Activation and Migration From Classic GL
SAP New GL Activation and Migration From Classic GL
GL
During a new installation, the New G/L accounting in the standard system is set to
active. While the use of classic General Ledger is theoretically also possible for new
customers. As SAP advises, we should do SAP New GL activation in the initial
installation to avoid migration effort & cost later on.
The checkbox for activating New General Ledger Accounting is Active is set for each
client.
A migration should always begin as a project, with all of the elements of a project:
Phases, milestones, tests and so on. The migration project represents only a sub-
project of the larger project for New G/L.
Before the New G/L Migration Service becomes active, the implementation project
begins and the design and customising of New G/L gets completed.
An exact and complete configuration of New G/L is required before New G/L
accounting is set to active. In parallel with the configuration of New G/L work
continues in the classic General Ledger.
Project Duration
We cannot generalise about the duration of a project because it depends on various
factors. You can accelerate the project by addressing the following issues:-
a. Can test systems be quickly built and transport immediately available? In any
case, the parties concerned should have the opportunity to familiarise
themselves with the procedure in a test system so that affected areas can
access existing challenges.
b. How does the staffing for the project look from the customer side? What
background experience do members bring to the project team and is the
company prepared to invest in training?
c. The customer’s project team or the implementation partner’s team should
consist of members with well-grounded expertise in SAP ERP Financials and
Migration.
Migration date –The migration date with the beginning of migration: between phase
0 and phase 1 of the migration.
In phase 0, you implement the design and customising of New G/L. These activities
are followed by functional and integration tests in a test system. Additionally, you
start to plan and design the subsequent migration. If you use a scenario including
document splitting, you must implement the customizing in the production system.
Besides these activities, you must also consider the posting data. No single
documents are copied from phase 0 before the migration date. For non-open item-
managed accounts, such as the G/L account, a carry forward is made into the
migration year.
This content relates to support during the technical migration of the source data from
the classic application into New G/L. For support with the blueprint and customizing
of New G/L, you can use SAP Consulting from an appropriate local company or
consulting partner.
Migration Scenarios
Migrations primarily involve moving existing data. For example, if you want an
existing classic profit centre accounting to be mapped in New G/L in the future, data
must be copied from table GLPCT into the new totals table FAGLFLEXT.
Standardised methods and program packages therefore must be delivered with
the New GL Migration scenarios created by SAP to provide secure and effective
support for the migration within a project. This section differentiates between the
terms service-based and project-based migration and introduces you to the
scenarios of service-based migration.
Development System
In the development system, you configure New G/L Development of BAPI or your
programs also occur in this system.
Quality system
The quality assurance system is a copy of the production system that is
representative master and transaction data available. Additionally, the new
configuration and programming are transported from the test system to the quality
system, so this system is suitable for test migrations to New G/L.
Production System
In the production system, you can access the configuration only to a very limited
extent. Only when the last test migration has been completed successfully should
you change to the live operation.
During the migration project, you must ensure that the Customizing for New G/L
Accounting has no negative effects on your current day-to-day activities. You must
prevent an “ accidental activation” by all means. If you use a scenario with document
splitting. It is necessary and useful to transport the configuration before the migration
to the production system.
Conclusion
The migration service ensures the quality of the data and minimises possible risks
associated with the project. The migration cockpit simplifies the handling of the
migration and significantly reduces its complexity. The migrations that already have
been performed and the related experiences that have been gained allow you to
minimise risk and successfully implement the functional added value of New G/L.