In the case of both migration and a new system implementation with subsequent legacy data transfer, you have to initiate a separate project with the corresponding project phases for the procedure. Hint: Both this implementation project and a new General Ledger Accounting project have to resolve both technical and process-related aspects. They are not table swaps. Note: To learn more about the default configuration of an SAP system and the activation of new General Ledger Accounting, read SAP Note 756146.

These are some example parameters you should evaluate when setting up a migration project: Which SAP components do you already use or have you been using to date? Are you required to portray your accounting figures according to more than one set of

accounting principles (using parallel accounting)? What does your target configuration in new General Ledger Accounting look like?

Which FI characteristics would you like to use in new General Ledger Accounting? Do you want to produce a profit and loss statement according to cost of sales

accounting or period accounting?

This figure describes at which organizational structure level in SAP you activate the new General Ledger Accounting.

All Financial Accounting (FI) documents for phase 1 that will be used in document splitting (phase 2) should be checked to determine whether the postings can be used in new General Ledger Accounting. This makes it easier to subsequently post the documents during the migration. Hint: This check takes place in the system using validation of document splitting.

This is an example to make the migration phase model easier to visualize.

It is clear that SAP is not using the SAP General Ledger Migration service to carry out the entire new General Ledger Accounting project. The service only supports the customer project. Consulting services which may be required are not included in the service.

The components of the SAP General Ledger Migration service are as follows: The SAP General Ledger Migration service

SAP service for migrating data from the classic General Ledger to new General Ledger Accounting.

Service session for scenario validation and system analysis (SV) Service event designed to check whether the migration package ordered by the customer matches the customer’s business scenario. To do this, SAP extracts the required information from the customer system and evaluates the data in one of its own systems.

New General Ledger Accounting Migration Cockpit User interface enabling the customer to perform the migration, consisting of the Migration Monitor and the Process Tree. The Migration Monitor is a process monitor in which you can see the status and results of the migration. The Process Tree resembles Customizing and maps all the steps to be carried out. These depend on the package and are therefore put together on a scenario basis. In this way, the customer receives tailor-made guidance through the migration process.

Service session for test validation (TV) Service event comprising technical plausibility checks on the migrated data.

The SAP General Ledger Migration service ensures the quality of the project for migration to new General Ledger Accounting and minimizes possible risks associated with the project. As described, the service sessions verify the approach to the project and the performance of the data migration and, therefore, contribute to ensuring data consistency after the migration. The

Migration Cockpit simplifies the handling of the migration and makes the process considerably less complex.

On the Web page, you can find all the information you need before the start of a migration to new General Ledger Accounting.