1. Johannes Le Roux
Leroux@jari-consuling.com

2. New G/L Migration Roadmap and
Cockpit
Johannes Le Roux, Satreno North America
(USA)

3. Main Message
• Introduction – SAP New General Ledger
• Migration to SAP New General Ledger
• Migration Cockpit
• Key Points to Take Home
• Summary
• Questions

4. Introduction - Migration to New G/L
Business Drivers why to move to the New GL……..
• Need single general ledger for company-wide financial reporting and
decision making
• Improve management reporting at the profit-center level with real-time
balance sheets using the document-splitting feature
• Need better visibility across all reporting units
• Need Reporting in different accounting standard and Multiple Currencies
across the world
• Need a faster closing process
• Need Multiple Fiscal year variants

5. Introduction - Migration to New G/L
SAP New General Ledger will combine three ledgers into one
Legal Reporting
Classic • Company code
General • Account
Ledger • Business area
Legal & Management
Management Reporting New Reporting
• Company code General • Company code
Profit • Account • Account
Center • Profit center
Ledger • Business area
Ledger • Plant • Prot center
• Trading partner • Trading partner
• Functional area
Products Management • Destination country
Special Reporting
Purpose • Company code
Ledger • Account
• Business area
• Profit center
• Trading partner
• Destination country

6. Introduction - Migration to New G/L
Parallel Ledger/Valuation
Leading Ledger - 0L
Accounting Standard can
No Ledger
not Change LATER.
Specified
Company 1
Ledger
Specified
Local Ledger – 0A
Futures in Parallel Ledger Local - GAAP Company 2
• Separate ledger for each accounting standard
• Multiple Valuations – Based on Company Code/Local Ledger
• Parallel valuation Display Local Ledger – 0B
• Specific Postings to Ledgers Based on accounting standard IAS
• Statements By Accounting Standard Company 3
Classic ledger – Accounts, Special ledger and in in some Local Ledger – 0C
cases Company codes was used to allow parallel valuation
IFRS
• Multi-Ledger/ Multi Currency Updates Local Ledger – 0D
• Multi- Dimensional reporting (Segment, Profit center,
etc) IASB

7. Introduction - Migration to New G/L
Benefits……..
• Single source of financial information
• Enriched profit-center balance sheet reporting
• Balance sheet analytics with real-time document splitting
• Better financial closing efficiency achieved by reducing errors, manual
rework, and cycle times
• Foundation for simplifying accounting, improving efficiency, increasing
working capital visibility, and cutting IT costs
• All reporting done from a single source of data
• Reporting in multi currencies
• New General Ledger no longer requires Ledger reconciliations

8. Migration to New G/L
• This Scenario is straightforward and can be
Scenario 1 • Merging FI, PCA and SPL completed in the least amount of time.
• This Scenario is used where there is not
splitting or parallel valuation, and no
financial statement below company code
Scenario 2 • Includes document splitting level
• Includes parallel ledgers with
Scenario 3 no splitting • This is the Complex Migration Scenarios
• This Scenario includes document splitting
and adding of Parallel ledgers.
• Includes document splitting • This Scenario is normally used where there
Scenario 4 and parallel ledgers is splitting or parallel valuation used to
produce balanced financial statements
below company code level
• Adding splitting after initial
Scenario 5 migration
• You choose Scenario 1,2 & 4 and then want
to do a subsequent implementation with
• Adding splitting after initial
Scenario 6 migration
document splitting this will require an
additional migration project

9. Migration to New G/L
• This Scenario allow Companies already on
New GL to add a Parallel ledgers.
• NOTE: This is only required if the Company
• Add Parallel ledger on already in production with data posted to
Scenario 7 current New GL system it.
• This Scenario allows companies already on
• Switch from Parallel using Parallel accounting to switch to
parallel Ledgers.
Scenario 8 accounting to Parallel • EXAMPLE: Companies using account base
Ledger to split localized reporting and know they
are required to do IFRS as well. By splitting
the ledger will safe them from adding
additional accounts

10. Migration to New G/L
Roadmap
Upgrade Project New Ledger Implementation/Migration
Phase 0 Phase1 Phase 2
Planning & Blueprint Customize Go-live
SAP ECC New G/L and Test New Migrate to
G/L New G/L
• Complete Upgrade before • Planning of migration • Year-end close of • Perform migration
starting Migration project • Analyze business old fiscal year • Transfer Data into new tables:
• Define Customizing • Customize new G/L FAGLFLEXA/FAGLFLEXT
• Define Processes change • Customize migration • Run carry forward of fiscal year into new
• Define document splitting if • Activate split check totals table: FAGLFLEXT
needed • Test Migration • Update of split Info if needed.
Migration principles:
• Recommendation is that Date of migration is at the beginning of a fiscal year
• Year-end closing of old fiscal year must be completed prior to activation of new G/L
• Source ledger of migration data must be determined by company code and account

11. Migration to New G/L
New Ledger Implementation/Migration
Phase 0 Phase 1 Phase 2
Planning/Blueprint Migration and Testing GO-Live
Old Fiscal Year New Fiscal Year
Run Classic G/L Run Classic G/L Run New G/L
Year-end close of
old fiscal year
Date of Migration of Fiscal Date of Activation
Year change De-activate Classic Ledger
ALL Data Migrated

12. Migration to New G/L
It is required to use SAP’s Migration service for the migration to New G/L
Phase 0 Phase 1 Phase 2
Planning/Blueprint Migration and Testing GO-Live
SAP Migration Services
Questionnaire Scenario Service Test Service Production
Validation Session 1 Validation Session 2 Support
Customer
Configuration Review
Review Review & Testing
Session Session Session
Customer Migration project Site – Satreno/Client Team

13. Migration to New G/L
SAP 2 Service Sessions……
Service session 1: Scenario Validation
• Assure correct migration approach –Selection of Scenario
• Data Check – Support pack level, Currencies, Organizational
structures.
• Transactional Data Check – Tables, document and line items and
document types used.
• Checks of migration customizing against target customizing of
new G/L
This Service session is to help the client select the correct
migration package and to validate the fit for the package selected.

14. Migration to New G/L
SAP 2 Service Sessions……
Service session 2: Test Validation
• Validate that the testing was done as required from a technical
standpoint
• Check Components in use
• Validating process of migration
• Validate and review all data migration log and tables.
This Service session is to help the client validate that all data will
migrate as required based on new configuration.

15. Migration to New G/L
What about History Data……
• Historical data from the classic GL tables, PCA tables, and any SPL
is not migrated.
• Only Open items, and non-open item account balances are
migrated to the new tables.
• New GL Statements will only have current fiscal Year Data and
account balances rolled forward from previous fiscal year – No
detail available for Previous Fiscal Year.

16. Migration to New G/L
What does other companies do to bridge
reporting GAP?
• For historical comparison reporting in BW to combine the detailed
data from the past year and current year.
• Use Excel base reporting Tools like E-Server and Spreadsheet
Server
• Business Object consolidation reporting

17. Migration Cockpit
• Migration Cockpit is used to assist you in managing and guiding
you through the tree phases of the project.
• The tool enable project management to see tasks and monitor
progress of the migration project
Notes to apply to load Cockpit
• 1138250 – NMI_CONT: Information about Support Pack
• 1041066 – Installation of NMI Content 2006_1
When Cockpit is loaded access with transaction
CNV_MBT_NGLM

18. Migration Cockpit
Migration Cockpit
Step to setup Cockpit:
1 . Access migration Cockpit

19. Migration Cockpit
Migration Cockpit
Steps to setup Cockpit:
2. Create project

20. Migration Cockpit
Migration Cockpit
Steps to setup Cockpit:
3. Select Migration Package Scenario
• Each Scenario has it own migration cockpit package – Once
you defined the Scenario you will load the pack and follow
the step for the specific Scenario.

21. Migration Cockpit
Migration Cockpit
Steps to setup Cockpit:
4. Process TREE – Provide step by step process to complete migration

22. Migration Cockpit
Migration Cockpit
Step to setup Cockpit:
5. Create Migration plan
6. Set Migration Date - Migration Cockpit will select a date based on the migration plan
defined

23. Migration Cockpit
Migration Cockpit
Step to setup Cockpit:
7. Assign Company Codes and ledgers required – This can only be done after
configuration is completed for New GL in ECC

24. Migration Cockpit
Migration Cockpit
Step to setup Cockpit:
8. Check to be done before migration can start.

25. Key Points to Take Home
• New GL is not just a data migration project
• Significant effort needed for business process testing
• Strong communication required with Basis and ABAP
• Never underestimate the importance of your data
• Look for inconsistencies in your data now
• Guidance from New GL experienced SAP consultants essential to
project success
• Strong business sponsorship an absolute must
• Practice makes perfect
• Start cutover plan as early as possible
• Perform at least one full “Dry Run”Cutover
• Create data validation plan and convene SAP FI-CO and Business
Validation teams during migration
• Make log of Ledger differences during migration weekend and take
action later

26. Summary
• Plan a Timeline for your migration project around six-eight months
depending on you company culture.
• SAP’s New G/L migration support service is mandatory for all new
G/L migrations.
• Upgrade to ECC must be completed prior to the new G/L migration
• SAP will continue to support the classic G/L
• New G/L migration process is a consulting project – Only use
Consultant with New Ledger Experience
• NEW GL
– Faster Closing of book – Better integration and lest steps
– Improved reporting and analysis
– Improved Productivity

27. Questions

28. Slide 28

29. Johannes Le Roux
Leroux@jari-consuling.com