Migration the New GL in SAP is a strategic decision. Though migrating to New SAP GL has its benefits, the implementation can turn out to be a complicated project. Most companies make the mistake of treating migration to New GL as a simple technical issue in SAP like change managment. Best practice suggests that migration to New SAP GL should be taken up as a project. One of the key reasons for taking up migration to GL New SAP as a project is that implementation of New GL is not only a technical transfer of data, many conceptual changes may also apply during the process of implementation.

SAP suggests a 'Phased Model' for implementation of SAP New GL. The phased model suggests 3 phases for migration to new gl and data transfer.

Phase 0 - Single documents are not migrated from Phase 0. In Phase 0, accounts which are managed as 'Open Items' are such as vendor and customer open items are migrated individually. For accounts not managed as open items, the balance carry forward for these accounts is migrated ie. transferred to the migration year.

Phase 1 - In Phase 1, migration programs are used to transfer documents. Such migration programs post the documents subsequently during the implementation process. The decision to implement SAP New GL with document split or without document split will have an effect in this phase. In any case, the posting of documents will be completed here.

Phase 2 - This is looked upon as the last phase, where the New General Ledger Accounting is active and configurations made during the earlier phases are used.

One important point to note here is that New SAP GL cannot be activated for individual company codes alone. This is beacuse New General Ledger can only be activated across all SAP clients after data migration. So all 'productive' company codes need to be included in the New GL migration.

Related Posts

SAP Schedule Manager - Period End Closing
Tolerance Limits in SAP R3
Field Status Control in SAP SD MM
SAP xApps Analytics Beginner's Guide