Best Practices Migrating to the New General Ledger A Three Phase Approach

  • by Gary Fullmer, Solution Architect, MI6 Solutions
  • February 15, 2006
Use this three-phased approach to upgrade to the new G/L in mySAP ERP.
MySAP ERP 2005 includes a migration tool to assist in the upgrade project.
Key Concept

By selecting the option to upgrade to SAP’s new General Ledger structure, you must understand this is a full-blown consulting project, and should be treated as such.

mySAP ERP 2005 comes with several new tools to help you migrate your financial records from the classic G/L structure to the new mySAP ERP G/L functionality. I’ll describe those tools and how they are used within the three-phase upgrade project you will need to execute. The migration tools, found in the 2005 IMG, consist of work lists, a migration plan, splitting simulation tools, and result reporting. The sidebar, “Upgrade Options,” has more information on your upgrade options by release.


When migrating to the new mySAP ERP G/L, keep in mind this important fact: The migration process is not just a plug-and-play modification that you can complete over a short period of time. This project requires several different project phases. Each phase – data migration, testing procedures, and final data certification – requires extensive planning, data verification, and final approval prior to beginning the next phase or completing the project.


You need to understand at the start the meaning and impact of two project dates –  the start and finish of the migration project. The first date, the most important, is the actual date of data migration. This date must be identified very early in the project planning phase and must always be the beginning of your new/upcoming fiscal year.


The second project date is the actual date of activation for the new mySAP ERP G/L. Unlike the date of migration, this is not a fixed date, but is determined at the end of the project after you have completed all data migration, testing, and final certification.


As a standard procedure, you will most likely choose to run parallel general ledger systems initially to certify your new G/L structures. This is a suggested best practice, but understand that both the old and new G/L tables will receive the same postings during this period. Of course this has a detrimental effect on your system performance, and you should keep this period of parallel operation as short as possible. To shorten this window, it is essential that you complete a good project plan prior to the actual migration date.

Gary Fullmer

Gary Fullmer is currently associated with MI6 Solutions as a solution architect. Prior to MI6 Gary recently worked for SAP Labs for 13+ years. While at SAP Labs, he spent his first four years as a CO instructor developing and delivering all CO courses offered in the SAP course catalog. For the next six years, he assumed the role of a FI/CO solution manager, where he focused on interfacing with customers for CO, SEM, and FI solutions. During the remainder of his time with SAP, he worked on SAP General Ledger migration techniques, the SAP IFRS adoption model, and SAP’s enhanced financial closing, and continues to consult on these topics. His educational background includes an MBA from Rensselaer Polytechnic Institute, an MS from Utah State University, and a BS from Utah State University.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.