newglmigration1-110531152638-phpapp02

8/12/2019 newglmigration1-110531152638-phpapp02

http://slidepdf.com/reader/full/newglmigration1-110531152638-phpapp02 1/29

Johannes Le Roux

[email protected]

mailto:[email protected]






Johannes Le Roux, Satreno North America

(USA)

New G/L Migration Roadmap andCockpit



Main Message

• Introduction – SAP New General Ledger

• Migration to SAP New General Ledger

• Migration Cockpit

• Key Points to Take Home

• Summary

• Questions



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

NewGeneral

Ledger

Legal Reporting

• Company code

• Account

• Business area

Management Reporting• Company code

• Account

• Profit center

• Plant

• Trading partner

Products ManagementReporting

• Company code

• Account

• Business area

• Profit center

• Trading partner

• Destination country

Legal & Management

Reporting• Company code

• Account

• Business area

• Prot center

• Trading partner

• Functional area

• Destination country



Parallel Ledger/Valuation

IAS

Local - GAAP

IFRS

IASB

Leading Ledger - 0L

Accounting Standard can

not Change LATER.

Local Ledger – 0A

Local Ledger – 0B

Local Ledger – 0C

Local Ledger – 0D

No Ledger

Specified

Ledger

Specified

Futures in Parallel Ledger• 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

• Multi-Ledger/ Multi Currency Updates

• Multi- Dimensional reporting (Segment, Profit center,

etc)

Company 2

Company 1

Company 3


Classic ledger – Accounts, Special ledger and in in somecases Company codes was used to allow parallel valuation



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, manualrework, 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




• Merging FI, PCA and SPLScenario 1

• Includes document splittingScenario 2

• Includes parallel ledgers withno splittingScenario 3

• Includes document splittingand parallel ledgersScenario 4

• Adding splitting after initialmigrationScenario 5

• Adding splitting after initialmigrationScenario 6

Migration to New G/L

• This Scenario is straightforward and can becompleted 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



• Add Parallel ledger oncurrent New GL systemScenario 7

• Switch from Parallelaccounting to ParallelLedger

Scenario 8


• Add Parallel ledger oncurrent New GL systemScenario 7

• Switch from Parallelaccounting to ParallelLedger

Scenario 8

• 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 theyare required to do IFRS as well. By splitting

the ledger will safe them from adding

additional accounts




New Ledger Implementation/Migration

SAP ECC

Phase 0

Planning & Blueprint

New G/L

Phase1

Customize

and Test New

G/L

Phase 2

Go-live

Migrate to

New G/L

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

• 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.

• Year-end close of

old fiscal year

• Customize new G/L

• Customize migration

• Activate split check

• Test Migration

• Planning of migration

• Analyze business

• Define Customizing

• Define Processes change

• Define document splitting if

needed

Upgrade Project

• Complete Upgrade before

starting Migration project

Roadmap




Old Fiscal Year New Fiscal Year

Run Classic G/L Run Classic G/L

Phase 0 Phase 1 Phase 2

Run New G/L

Date of Migration of Fiscal

Year changeDate of Activation

De-activate Classic Ledger

Year-end close of

old fiscal year

New Ledger Implementation/Migration

ALL Data Migrated

Planning/Blueprint Migration and Testing GO-Live



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

Questionnaire

Customer Migration project Site – Satreno/Client Team

Scenario

Validation

Review

Session

Service

Session 1

Customer

Configuration

& Testing

SAP Migration Services

Test

Validation

Review

Session

Service

Session 2

Review

Session

Production

Support



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 correctmigration package and to validate the fit for the package selected.




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.




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 – Nodetail available for Previous Fiscal Year.




What does other companies do to bridgereporting 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




Notes to apply to load Cockpit• 1138250 – NMI_CONT: Information about Support Pack

• 1041066 – Installation of NMI Content 2006_1When Cockpit is loaded access with transaction

CNV_MBT_NGLM

• 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

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


3. Select Migration Package Scenario

Migration Cockpit

• Each Scenario has it own migration cockpit package – Onceyou defined the Scenario you will load the pack and follow

the step for the specific Scenario.



Migration Cockpit


4. Process TREE – Provide step by step process to complete migration

Migration Cockpit



Migration Cockpit


5. Create Migration plan

6. Set Migration Date - Migration Cockpit will select a date based on the migration plandefined

Migration Cockpit



Migration 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


8. Check to be done before migration can start.

Migration Cockpit



• 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 toproject 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 BusinessValidation teams during migration

• Make log of Ledger differences during migration weekend and takeaction later

Key Points to Take Home



• 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

Summary



Questions



Slide 28






Johannes Le Roux

[email protected]





newglmigration1-110531152638-phpapp02

Documents

Transcript of newglmigration1-110531152638-phpapp02