sap migrating to the new gl. here's how to design and execute a successful migration project26091411

Migrating to the New G/L? Heres How to Design and Execute a Successful Migration Project

Gary FullmerSAP Labs

Basic Steps in New G/L Migration

SAPs New G/L Migration Service

Wrap-up

Project Overview

Planning Phase 0

Data Migration Project Phase 1


End of Project Project Phase 2

SAP AG 2007, 3

Timeline

Project Timeline for New G/L Implementation

Schedule for the implementation to new G/L Complete upgrade from SAP R/3 to mySAP ERP New G/L implementation project

Blueprint of new G/L (determination of business requirements) Customizing and implementation of new G/L Customizing of migration Migration execution

Upgrade

Project

SAP R/3 mySAP ERP

Separate projects for mySAP ERP upgrade and new G/Limplementation

Migrationto new G/L

Blueprint new G/L

New G/L Implementation Project

Customizing& implementing

new G/L

SAP AG 2007, 4

Migration is a Consulting Project

Things to consider: Migration is more than just a simple transfer of data from one data table

to another The migration process should be considered as a major project, requiring:

- Blueprinting- Scheduling of milestones- Extensive testing and certification of results- Final signoff on project results

Fundamental prerequisites for the migration Successful upgrade to mySAP ERP 2005 or mySAP ERP 2004 Migration date must be the start of a new fiscal year Prior fiscal year-end closing must be completed prior to project kickoff

Warning

SAP AG 2007, 5

Migration is a Consulting Project (cont.)

Additional things to consider: The migration does not require the:

Installation of mySAP ERP 2005- Easier with mySAP ERP 2005- For mySAP ERP 2004 projects, SP10 must be installed

Implementation of parallel accounting- Multi-ledgers

Implementation of segments or Profit Center Accounting (PCA) is recommended

- PCA and Segment Accounting is very difficult to install after the Go-Live date- Changeover of the leading valuation, if parallel valuation is already used

Consideration of scenarios with the company code approach - Not supported at this time

Simultaneous changeover of the leading depreciation area Change to chart of accounts or conversion of chart of accounts

SAP AG 2007, 6

Perform migration Transfer documents of

Phase 1 into new tables: FAGLFLEXA/FAGLFLEXT

Run carryforward for the new fiscal year into the new totalstable FAGLFLEXT

Subsequent update of split infotable for single items of old fiscal years that were open per migration date

Year-end close of oldfiscal year

Customize new G/L Customize migration Activate split check (only

relevant if document splitting is to be used)

Create blueprint for new G/L Planning of migration Customize new G/L Analyze business

processes if document splitting is to be used

Customize document splitting

New G/L Phased Migration

Note: These migration principles Date of migration is at the beginning of a fiscal year (current or future) Year-end closing of old fiscal year must be completed prior to activation of new G/L Source ledger(s) of migration data must be determined by company code and account

Old Fiscal Year

Date of Migration Date of Activation

Phase 0 Planning Phase 1 Migration and Testing

Phase 2 Go-Live

New Fiscal Year

New G/LClassic G/LClassic G/L

Project Overview

Planning Phase 0Data Migration Project Phase 1



SAP AG 2007, 8

Project Planning Phase 0

Project planning and blueprinting The project plan should include:

The final design of the new G/L- Reporting requirements- Legal issues- Initial configuration structure

Migration planning complex vs. simple- Many features can be added later

z Switch from account-based to parallel ledger accountingz Online document splittingz Real-time data update from controllingz Segment and profit center reporting

Project schedule- Fiscal year close- Start configuration of the new G/L- Switch off old G/L

SAP AG 2007, 9

Project Planning Phase 0: Summary

Basic requirements that should be completed prior to Phase 1: Project blueprint.

Desired outcome.

Initial configuration of the new G/L. Parallel accounting. Real-time updates for controlling.

Configuration of migration plan or plans. How many and what company codes?

Will document splitting be used initially? Will open items from old fiscal year be split and posted?

Configure document splitting. Use delivered method or customized method.

Project Overview




SAP AG 2007, 11

Begin the G/L Data Migration and Testing Phase 1

Date of migration established Must be fiscal year-end

Prior fiscal year-end closing completed and locked against further posting

Configuration of new G/L completed Document splitting configured, if required

Migration plan or plans configured Company codes selected for each migration plan Parallel ledgers configured and assigned to company codes

- Additional currency selected for company codes- Multi-fiscal year variants assigned to company codes

Phase 0 must be complete prior to data migration start

SAP AG 2007, 12

Update Documents to Ledgers


Update Items to Ledgers


Migration Project Data Flow and Testing Phase 1

Create Worklists

OpenItemsPriorFiscalYear

Documentsfrom

CurrentFiscalYear

Build Document Splitting Information

Build Document Splitting Information



BAdI

Document SplittingCustomizing

AlternativeCustomizing for

Document Splitting

Phase 2

Phase 2

Update New G/L Data Tablesand

Build Balance Carryforward

Build New G/L Data Tables

ClosingBalance

of Non-OI

ManagedAccounts

Update Balance Carryforward to

LedgersOI = Open Items

SAP AG 2007, 13

G/L Data Migration and Testing Phase 2 Summary

Basic requirements that should be completed prior to Phase 2 Old fiscal year-end closing completed and locked Migration plans activated Worklists created for both open items and new documents Simulation of document splitting Migrate the data to the new data tables Test and certify the migration results Reset the migration plans as required Repeat the data migration as required Retest and certify the data as required Move to Phase 2 of project and set the switch to close the project

Project Overview




SAP AG 2007, 15

End the Migration Project Phase 2

IMG menu option All data must be checked and certified prior to this activity

Final step (NO return)

Effects All migration plans are deactivated Other migration functions used during the migration process are

also deactivated- Manual adjustments to balance carryforward items (transaction type FBCB)

Once this step is complete, the migration plans are deactivated

SAP AG 2007, 16

Demo: Actual Migration Project



Wrap-up

Benefits of New G/L Migration Service

Details of New G/L Migration Service

Availability of New G/L Migration Service


SAP AG 2007, 19

Customer Benefits

SAPs Migration Support Team is our customers Trusted Advisorduring their entire new G/L migration project from start to finish Objective is to provide our customers with a smooth and successful

transition from classic G/L to the mySAP ERP-based new G/L Migration customers will receive the following support services:

Review of critical steps and results during new G/L configuration and data migration

- New G/L design- Document splitting settings that are a key component of your project- Migration plan configuration- Results of migration and review of migrated data

Availability of preconfigured new G/L scenarios to add in the overall configuration of the new G/L

- Based on your specific requirements Direct engagement with back-office support contacts

- Highly skilled and qualified SAP financial consultants 247 support Final review and discussion of migration results

- Prior to new G/L Go-Live

SAP AG 2007, 20

Customer Benefits (cont.)

Reduced complexity of migration due to scenario-based functionality and guidance Efficient and targeted data migration Easier to handle

Safe data migration and quality assurance of migration project via service sessions Lower risk of migration project

Additional assistance by competent and experienced SAP experts in new G/L migration back office Knowledge Base and Knowledge Ware

Lower cost of data migration through standardized and high quality migration procedure Overall cost of the new G/L implementation project will

be reduced

Migration service is based on procedure certified by auditor

+

+

+

+

+

SAP AG 2007, 22

How the New G/L Migration Service Supports the Project

Old Fiscal Year

Date of Migration =

Fiscal Year Change Date of ActivationNew Fiscal Year

Run New G/LRun Classic G/L

Close Old Fiscal Year

Run Classic G/L

Phase 0 Phase 1 Phase 2

Validation of migration scenario selected by customer

Scenario-related migration programs

Back-office support

Scenario-related guidance through the migration process

Plausibility checks of migration customizing against target customizing of new G/L

Technical plausibility checks of migrated test system

Back-office support

New G/L migration service provides: Back-office support

SAP AG 2007, 23

Content of New G/L Migration Service

Complete migration service offered at a fixed price

Scenario-based new G/L migration cockpit Step-by-step guidance through the migration via process tree and monitor Status administration with logs

Remote service sessions Service session to assure right migration approach Service session including technical validation and plausibility checks in

migrated test data

Development support On call 24 hours/day development support for production weekend Development support for test migrations during working hours

SAP AG 2007, 24

New G/L implementation project at customer site

New G/L

F

e

e

b

a

c

k

S

e

s

s

i

o

n

R

e

q

u

e

s

t

Q

u

o

t

a

t

i

o

n

M

i

g

r

a

t

i

o

n

S

e

r

v

i

c

e

F

e

e

d

b

a

c

k

S

e

s

s

i

o

n

Q

u

o

t

a

t

i

o

n

A

d

d

i

t

i

o

n

a

l

C

o

n

s

u

l

t

i

n

g

Test by Customer

P

r

o

d

u

c

t

i

v

e

M

i

g

r

a

t

i

o

n

I

n

c

l

u

d

e

s

O

n

C

a

l

l

2

4

H

o

u

r

s

/

D

a

y

B

a

c

k

-

O

f

f

i

c

e

S

u

p

p

o

r

t

New G/L Migration Service Sessions/Back Office

Q

u

e

s

t

i

o

n

n

a

i

r

e

S

c

e

n

a

r

i

o

V

a

l

i

d

a

t

i

o

n

F

e

e

d

b

a

c

k

S

e

s

s

i

o

n

T

e

s

t

V

a

l

i

d

a

t

i

o

n

New G/L Consulting

Service Session 1 Service Session 2

SAP AG 2007, 25

First Service Session: Scenario Validation

Data checks are carried out in mySAP ERP production or recent test system

General data checks New G/L inactive at client and company code level Currencies (number and consistencies) Controlling areas (e.g., when segmentation is to be implemented)

Financial accounting data checks Transaction data records in GLT0, GLFUNCT, GLT3, and others Balance sheet adjustment (SAPF180) Documents and line items (document types, required accounts, etc.)

Service session to assure right migration approach

SAP AG 2007, 26

Second Service Session: Test Validation

Data checks in test system after test migration

Data checks Open items list

Other checks

Ensure that the test migration was consistent from a technical point of view

SAP AG 2007, 27

Scenarios Supported by New G/L Migration Service

Scenario 1: Merge of FI ledger Merging of classic G/L ledger, consolidation preparation ledger, and

cost-of-sales ledger

Benefits: Reduced data redundancy Reduced effort for period end closing Harmonized reporting

Scenario 2: Merge of FI, PCA and/or Special Ledger Scenario 1 and additional merging of PCA and Special Purpose

Ledger

Benefits: Replacement of Special Purpose Ledger accounting by new G/L Enhanced auditability Better integrated reporting

SAP AG 2007, 28

Scenarios Supported by New G/L Migration Service (cont.)

Scenario 3: Scenario 2 + document split (e.g., for profit center, segment, or business area reporting)

Document split allows balance sheet on additional dimensions, such as profit center or segments

Benefit: Flexible reporting on entities other than company code

Scenario 4: Scenario 2 + change to ledger solution for parallel accounting

Switch from parallel accounting by parallel accounts to parallel ledger

Benefit: More transparent chart of accounts, reporting, and auditability

SAP AG 2007, 29

Scenarios Supported by New G/L Migration Service (cont.)

Scenario 5: Scenario 3 + change to ledger solution for parallel accounting

See descriptions of scenarios 2, 3, and 4

Any scenarios that differ from the above standard scenarios are migrated project-by-project based on Scenario 5

SAP AG 2007, 30

Migration Guidance: Process Tree/Monitor

Draft

SAP AG 2007, 31

Migration Guidance: Process Tree/Monitor (cont.)

Draft

SAP AG 2007, 32

Demo: New Migration Cockpit

SAP AG 2007, 34

Planned Availability of New G/L Migration Service

First pilot shipments for mySAP ERP 2004 Scenarios 1-3 plus scenario validation session: As of November 20, 2006 Scenarios 1-5 plus scenario validation session and technical test

validation session planned for late Q1 2007

General availability for mySAP ERP 2004 Scenarios 1-3 plus scenario validation session: Planned for

January 2007 Scenarios 1-5 plus scenario validation session and technical test

validation session planned for Q2 2007

First pilot shipments for mySAP ERP 2005 Scenarios 1-3 plus scenario validation session: Planned for

January 2007 Scenarios 1-5 plus scenario validation session and technical test

validation session planned for late Q2 2007



Wrap-up

SAP AG 2007, 36

Resources

New G/L and migration to new G/L is covered in greater depth in the following SAP training courses: AC210: New (Flexible) General Ledger AC212: Migration to new General Ledger Accounting

Pre-version covering the first three scenarios planned for first quarter 2007 Full version covering five scenarios planned for mid 2007

Refer to the SAP Education Service to find out when these courses are being held in your region You can also find this information at www.service.sap.com/trainingcatalog*

Additional information about the new G/L migration service: SAP Service Marketplace, http://service.sap.com/GLMIG *

Also see the Migration Guide on this page

Note 812919 (and related notes) If you have further questions or want to order the service, please send

an email to [email protected]

* Requires login credentials to the SAP Service Marketplace

SAP AG 2007, 37

Resources (cont.)

Additional information about the new G/L in mySAP ERP SAP Service Marketplace, http://service.sap.com/gl *

SAP General Ledger Notes to consider: 826357 Profit Center Account and the New G/L 756146 General Information New General Ledger 741821 Release Restrictions mySAP ERP 2004 852235 Release Restrictions mySAP ERP 2005 812919 Migration to New General Ledger mySAP ERP 2004 862523 Support Pack 10 mySAP ERP 2004 Features and Functions 950183 How to Access Migration Tool Kit (Apply for Migration Key) 779251 Parallel Accounting Discussion Ledger vs. Account Based

* Requires login credentials to the SAP Service Marketplace

SAP AG 2007, 38

7 Key Points to Take Home

New G/L migration support service is mandatory for all new G/L migration projects

Plan on a six month timeline for your migration project Expect to have some issues around data cleansing during your

project mySAP ERP must be live prior to the new G/L migration It is not a requirement to run the new G/L within my SAP ERP

2004 or 2005 SAP will continue to support the classic G/L format for the

foreseeable future New G/L migration process is a consulting project

Ensure that only well-qualified and highly experienced financial consultants are utilized for your project

SAP AG 2007, 39

Your Turn! Questions?

Contact Information:Gary Fullmer

Solution Management [email protected]

SAP AG 2007, 40

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Copyright 2007 SAP AG. All Rights Reserved

sap migrating to the new gl. here's how to design and execute a successful migration project26091411

Documents

new gl planning of migration

new gl implementationschedule

migration process

new tables

data migration project

new gl complete upgrade

migration successful

mysap erp upgrade