You are on page 1of 29

Johannes Le Roux

Leroux@jari-consuling.com

New G/L Migration Roadmap and


Cockpit
Johannes Le Roux, Satreno North America
(USA)

Main Message

Introduction SAP New General Ledger


Migration to SAP New General Ledger
Migration Cockpit
Key Points to Take Home
Summary
Questions

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

Introduction - Migration to New G/L


SAP New General Ledger will combine three ledgers into one
Classic
General
Ledger

Profit
Center
Ledger

Special
Purpose
Ledger

Legal Reporting
Company code
Account
Business area
Management Reporting
Company code
Account
Profit center
Plant
Trading partner
Products Management
Reporting
Company code
Account
Business area
Profit center
Trading partner
Destination country

New
General
Ledger

Legal & Management


Reporting
Company code
Account
Business area
Prot center
Trading partner
Functional area
Destination country

Introduction - Migration to New G/L


Parallel Ledger/Valuation
No Ledger
Specified

Leading Ledger - 0L
Accounting Standard can
not Change LATER.
Company 1

Ledger
Specified

Local Ledger 0A

Futures in Parallel Ledger

Local - GAAP

Local Ledger 0B

Separate ledger for each accounting standard


Multiple Valuations Based on Company Code/Local Ledger
Parallel valuation Display
Specific Postings to Ledgers Based on accounting standard
Statements By Accounting Standard

Classic ledger Accounts, Special ledger and in in some


cases Company codes was used to allow parallel valuation

Multi-Ledger/ Multi Currency Updates


Multi- Dimensional reporting (Segment, Profit center,
etc)

Company 2

IAS
Company 3
Local Ledger 0C

IFRS
Local Ledger 0D

IASB

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

Migration to New G/L


Scenario 1

Merging FI, PCA and SPL

Scenario 2

Includes document splitting

Scenario 3

Includes parallel ledgers with


no splitting

Scenario 4

Includes document splitting


and parallel ledgers

Scenario 5

Adding splitting after initial


migration

Scenario 6

Adding splitting after initial


migration

This Scenario is straightforward and can be


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
level

This is the Complex Migration Scenarios


This Scenario includes document splitting
and adding of Parallel ledgers.
This Scenario is normally used where there
is splitting or parallel valuation used to
produce balanced financial statements
below company code level

You choose Scenario 1,2 & 4 and then want


to do a subsequent implementation with
document splitting this will require an
additional migration project

Migration to New G/L

Scenario 7

Scenario 8

Add Parallel ledger on


current New GL system

Switch from Parallel


accounting to Parallel
Ledger

This Scenario allow Companies already on


New GL to add a Parallel ledgers.
NOTE: This is only required if the Company
already in production with data posted to
it.

This Scenario allows companies already on


using Parallel accounting to switch to
parallel Ledgers.
EXAMPLE: Companies using account base
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

Migration to New G/L


Roadmap
Upgrade Project

SAP ECC

Complete Upgrade before


starting Migration project

New Ledger Implementation/Migration


Phase 0
Planning & Blueprint
New G/L

Planning of migration
Analyze business

Phase1
Customize
and Test New
G/L
Year-end close of
old fiscal year

Define Customizing

Customize new G/L

Define Processes change

Customize migration

Define document splitting if

Activate split check

needed

Test Migration

Phase 2
Go-live
Migrate to
New G/L
Perform migration
Transfer Data into new tables:
FAGLFLEXA/FAGLFLEXT
Run carry forward of fiscal year into new
totals table: FAGLFLEXT
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

Migration to New G/L


New Ledger Implementation/Migration
Phase 0

Phase 1

Planning/Blueprint

Old Fiscal Year

Run Classic G/L

Phase 2

Migration and Testing

GO-Live

New Fiscal Year

Run Classic G/L

Run New G/L

Year-end close of
old fiscal year
Date of Migration of Fiscal
Year change
ALL Data Migrated

Date of Activation
De-activate Classic Ledger

Migration to New G/L


It is required to use SAPs 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
Validation Session 1

Review
Session

Review
Session

Test
Validation
Customer
Configuration
& Testing

Service
Session 2

Review
Session

Customer Migration project Site Satreno/Client Team

Production
Support

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.

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.

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.

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

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

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

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

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.

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

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

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

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

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 RunCutover
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

Summary
Plan a Timeline for your migration project around six-eight months
depending on you company culture.
SAPs 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

Questions

Slide 28

Johannes Le Roux
Leroux@jari-consuling.com

You might also like