new gl migration 1

29
Johannes Le Roux [email protected]

Upload: johannes-le-roux

Post on 25-Dec-2014

11.727 views

Category:

Documents


6 download

DESCRIPTION

 

TRANSCRIPT

Page 2: New gl migration 1

Johannes Le Roux, Satreno North America (USA)

New G/L Migration Roadmap and Cockpit

Page 3: New gl migration 1

Main Message

• Introduction – SAP New General Ledger

• Migration to SAP New General Ledger

• Migration Cockpit

• Key Points to Take Home

• Summary

• Questions

Page 4: New gl migration 1

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

Page 5: New gl migration 1

SAP New General Ledger will combine three ledgers into one

Introduction - Migration to New G/L

ClassicGeneralLedger

ProfitCenterLedger

SpecialPurposeLedger

NewGeneralLedger

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 & ManagementReporting• Company code• Account• Business area• Prot center• Trading partner• Functional area• Destination country

Page 6: New gl migration 1

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

Introduction - Migration to New G/L

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

Page 7: New gl migration 1

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

Introduction - Migration to New G/L

Page 8: New gl migration 1

• Merging FI, PCA and SPLScenario 1

• Includes document splittingScenario 2

• Includes parallel ledgers with no splittingScenario 3

• Includes document splitting and parallel ledgersScenario 4

• Adding splitting after initial migrationScenario 5

• Adding splitting after initial migrationScenario 6

Migration to New G/L

• 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

Page 9: New gl migration 1

• Add Parallel ledger on current New GL systemScenario 7

• Switch from Parallel accounting to Parallel Ledger

Scenario 8

Migration to New G/L

• Add Parallel ledger on current New GL systemScenario 7

• Switch from Parallel accounting to Parallel Ledger

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 they are required to do IFRS as well. By splitting the ledger will safe them from adding additional accounts

Page 10: New gl migration 1

Migration to New G/L

New Ledger Implementation/Migration

SAP ECC

Phase 0 Planning & Blueprint New G/L

Phase1 Customize and Test New G/L

Phase 2Go-live Migrate toNew 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

Page 11: New gl migration 1

Migration to New G/L

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 change

Date of ActivationDe-activate Classic Ledger

Year-end close of old fiscal year

New Ledger Implementation/Migration

ALL Data Migrated

Planning/Blueprint Migration and Testing GO-Live

Page 12: New gl migration 1

It is required to use SAP’s Migration service for the migration to New G/L

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

ServiceSession 1

Customer

Configuration

& Testing

SAP Migration Services

Test Validation

Review Session

ServiceSession 2

Review Session

Production Support

Page 13: New gl migration 1

SAP 2 Service Sessions……Service session 1: Scenario Validation

• Assure correct migration approach –Selection of Scenario

• Data Check – Support pack level, Currencies, Organizationalstructures.

• Transactional Data Check – Tables, document and line items anddocument types used.

• Checks of migration customizing against target customizing ofnew G/L

This Service session is to help the client select the correctmigration package and to validate the fit for the package selected.

Migration to New G/L

Page 14: New gl migration 1

SAP 2 Service Sessions……Service session 2: Test Validation

• Validate that the testing was done as required from a technicalstandpoint

• 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 willmigrate as required based on new configuration.

Migration to New G/L

Page 15: New gl migration 1

What about History Data……

• Historical data from the classic GL tables, PCA tables, and any SPLis not migrated.

• Only Open items, and non-open item account balances aremigrated to the new tables.

• New GL Statements will only have current fiscal Year Data andaccount balances rolled forward from previous fiscal year – Nodetail available for Previous Fiscal Year.

Migration to New G/L

Page 16: New gl migration 1

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 SpreadsheetServer

• Business Object consolidation reporting

Migration to New G/L

Page 17: New gl migration 1

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

Page 18: New gl migration 1

Migration Cockpit

Step to setup Cockpit: 1 . Access migration Cockpit

Migration Cockpit

Page 19: New gl migration 1

Migration Cockpit

Steps to setup Cockpit: 2. Create project

Migration Cockpit

Page 20: New gl migration 1

Migration Cockpit

Steps to setup Cockpit: 3. Select Migration Package Scenario

Migration Cockpit

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

Page 21: New gl migration 1

Migration Cockpit

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

Migration Cockpit

Page 22: New gl migration 1

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

Page 23: New gl migration 1

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

Page 24: New gl migration 1

Migration Cockpit

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

Migration Cockpit

Page 25: New gl migration 1

• 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

Key Points to Take Home

Page 26: New gl migration 1

• Plan a Timeline for your migration project around six-eight monthsdepending on you company culture.

• SAP’s New G/L migration support service is mandatory for all newG/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 useConsultant with New Ledger Experience

• NEW GL

– Faster Closing of book – Better integration and lest steps

– Improved reporting and analysis

– Improved Productivity

Summary

Page 27: New gl migration 1

Questions