masterguide glm v1 2

Master Guide

SAP General LedgerMigration Cockpit

For

mySAP ERP 2004SAP ERP 6.0

Document Version 1.2 – July 2009

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks 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 IBMCorporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder 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, andother SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of theirrespective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

SAP Library document classification: PUBLIC

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

http://www.sap.com/

Typographic ConventionsType Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide: SAP General Ledger Migration Cockpit

4 July 2009

Contents

1 Getting Started.................................................................................51.1 Available Documentation ................................................................61.2 Features of SAP General Ledger Migration Cockpit ....................7

1.2.1 Overview .............................................................................................. 71.2.2 Process Monitor .................................................................................. 71.2.5 User Roles and Registration Functions ............................................ 8

1.3 Important SAP Notes .......................................................................82 SAP General Ledger Migration Overview .....................................9

2.1 System Landscape.........................................................................102.2 Preparations for SAP General Ledger Migration ........................10

2.2.1 Considering Business Implications of the Migration..................... 102.2.2 Choosing a Package ......................................................................... 112.2.3 Installing the Software and Preparing the System......................... 12

2.3 Phases of a General Ledger Migration.........................................132.3.1 Setup Phase....................................................................................... 132.3.2 Checkup Phase.................................................................................. 142.3.3 Preparation Phase............................................................................. 142.3.4 Migration Phase................................................................................. 142.3.5 Validation Phase................................................................................ 152.3.6 Activation Phase ............................................................................... 15


July 2009 5

1 Getting StartedThis master guide provides a central starting point for the technical implementation,configuration and use of the SAP General Ledger Migration cockpit. The SAP GeneralLedger Migration cockpit is an integral part of the SAP General Ledger Migration servicetogether with two remote service sessions, which will be delivered by the SAP GeneralLedger Migration back office during the migration project.

This master guide provides the information about which actions and which guides arerequired during a migration from the classic general ledger to the new general ledger. It isrelevant for everyone who participates in a migration project.

Getting Started contains valuable information about using this document and relatedinformation (documentation and SAP Notes). In addition, it gives you a short introductionto the SAP General Ledger Migration cockpit, its features, user roles etc.

SAP General Ledger Migration Overview provides you with information about thenecessary steps for the set-up and preparation of the project and gives you an overviewover the various phases of the project

Note: As mentioned above, this master guide concentrates on the tool-related aspects ofSAP General Ledger Migration. Information concerning the service sessions of the SAPGeneral Ledger Migration service can be found under http://service.sap.com/GLMIG. Inaddition, it is important to keep in mind that migration to new general ledger should never beseen as an isolated project, but as part of a general ledger implementation project.

http://service.sap.com/GLMIG.


6 July 2009

1.1 Available DocumentationApart from this master guide, different documentation types at different levels of detail areavailable. The following paragraphs give an overview of all documentation types that may berelevant in the context of the migration to the new general ledger.

SAP Library

The SAP Library http://help.sap.com/ is a collection of function- and process-orienteddocumentation for SAP components.

Target group:

Relevant for all target groups

Activity Documentation

All configuration activities and related tasks are shown in the SAP General Ledger Migrationcockpit.

Documentation is available for each activity. To read the documentation, select the requiredactivity and choose Display Text.

Target group:

Migration project team members

Consultants

Security Guide

Security guides are available for mySAP ERP 2004 and SAP ERP 6.0. In addition, there is aseparate security guide for the SAP General Ledger Migration cockpit.

Target group:

General ledger migration project team members

Security specialists

System administration

Additional Information

Important additional information about the SAP General Ledger Migration service, such aspresentations and the migration guide (German: Migrationshandbuch) can be found in SAPService Marketplace under: http://service.sap.com/GLMIG

Target group:

Relevant for all target groups

Terminology

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30languages, as well as many definitions and glossary entries in English and German.

Target group: Relevant for all target groups

http://help.sap.com/

http://service.sap.com/GLMIG


July 2009 7

1.2 Features of SAP General LedgerMigration CockpitThe SAP General Ledger Migration cockpit includes the following specific features that helpyou to carry out your activities conveniently and efficiently.

1.2.1 OverviewWhen you have installed the relevant software in the system, start the transactionCNV_MBT_NGLM to access the general ledger migration overview. You can then find furtherinformation about how to use this transaction by klicking on the information button.

A detailed introduction to the migration cockpit as well as the migrationprocess is given in the SAP standard training AC212 – Migration to the newgeneral ledger.

You use this overview screen to carry out all tasks that are not related to an individualmigration package. For example, you can create a project or package and register users.

The overview screen shows all existing projects and packages for the given client. You canaccess all items listed there if you have the required authorizations and registrations. (Fordetails on the authorization and registration concepts, see section 1.2.3).

1.2.2 Process MonitorWhen you have created a new migration package, the process monitor for this package isdisplayed. It contains a list of the activities to be executed in this migration package (processtree) as well as the status information you need for monitoring purposes, and providesaccess to all existing activity execution logs for your package.

There are different types of activities:

Activities with an executable function: Depending on the nature of the relatedstep, this function will either start a program in the background or call a selectionscreen in which you make the required entries. To execute the function, select therequired activity and choose Execute.Activities can be either mandatory or optional or mandatory only under specificcircumstances. If an activity is optional, this is mentioned in the activity text in theprocess tree.

Note that the SAP General Ledger Migration cockpit has a special kind ofoptional activities:When you execute such an activity for the first time, the system asks you ifyou really want to execute the activity or not.If you choose to continue and execute the activity, this activity is no longeroptional, but becomes mandatory. This means that you cannot proceed to thenext phase until this activity has a yellow or green status light.If you choose not to execute this activity, you can skip it and proceed with thenext activities and phases.


8 July 2009

Activities with confirmation function: When you have read the documentation foran activity of this type and taken all required action, select the activity in the processtree and choose Execute. A dialog box is displayed in which you confirm that youhave completed the activity. This is important for documentation purposes.

Activities for information purposes: These activities have documentation, but noexecutable function. The documentation contains important information related to thegiven stage of your general ledger migration project and tips for activities outside theprocess tree.

The activities in the process tree are clustered into phases. Only one phase is active at agiven point in time. You can execute only activities that belong to the active phase, but noactivities from previous or subsequent phases.

For each activity, you can create a note and/or store additional documents so that you haveall information related to an activity in one place and the project team members as well as theauditors can refer to it at any time.

1.2.3 User Roles and Registration FunctionsDepending on the role users are assigned, they have certain authorizations and can executedifferent tasks in a project or package. The definitions of the roles are shipped together withthe software. For more information, see security guide.

1.3 Important SAP NotesYou must read the SAP Installation Notes before you start the installation. These SAP Notescontain the most recent information on the installation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in theSAP Service Marketplace under: service.sap.com/notes

List of Related SAP Notes

SAP NoteNumber

Title Description

1014364 NewGL migration:Prerequisite/performance

Provides information about technicalprerequisites for the migration and tips forruntime improvements

1041066 Installation NMI Content 2006_1 Explains how to install the add-onNMI_CONT 2006_1

1138250 NMI_CONT: Information aboutSupport Packages

Explains the Support Package concept forNMI_CONT and informs you about anyspecifics you need to consider forindividual Support Packages

1014369 NewGL migration: Availability ofDevelopment Support

Explains how to obtain developmentsupport for the go-live of the migration

1072121 New general ledger migration: What iscovered by Support?

Explainss when a customer’s request fornormal support is free of charge, or whenthey would need to pay a consultancy fee.

1070629 FAQs: New General Ledger Migration Comprehensive list of questions andanswers regarding the SAP GeneralLedger Migration and related topics


July 2009 9

2 SAP General Ledger MigrationOverviewDifferent migration scenarios are imaginable for the transition from classic general ledger tonew general ledger, ranging from the straightforward merge of existing ledgers to a totallynew concept of accounting, such as the introduction of segment reporting for compliance withnew accounting principles. Also for the subsequent implementation of further functionalitywithin new general ledger different migration scenarios are possible.

The SAP General Ledger Migration cockpit covers the most commonly used migrationscenarios. It provides the framework to guide you step by step through the migration of yourdata, specific to your migration scenario. The cockpit contains the process tree (see 1.2.2)with the individual steps that have to be carried out for the migration, and a monitor whichallows you to follow the status of the migration. It is generated in your system when youcreate a migration package (see 2.2.3).

Regarding the scenarios which are supported by the SAP General Ledger Migration cockpit,see section 2.2.2.

In addition to the cockpit, the SAP General Ledger Migration service contains two servicesessions, which are delivered remotely by the SAP General Ledger Migration back office.These are:

1. Scenario validation session

2. Test validation session

Scenario validation session

The aim of this session is to verify that the scenario you have identified and ordered for yourmigration fits your system configuration. Thus the session ensures that the right migrationapproach is followed.

Test validation session

The aim of this session is to carry out technical plausibility checks in a migrated test systemin order to ensure data integrity following the migration.

For further information about theses service sessions, please refer to the SAP ServiceMarketplace under: http://service.sap.com/GLMIG

http://service.sap.com/GLMIG


10 July 2009

2.1 System LandscapeThe SAP General Ledger Migration cockpit is typically used in a landscape with development,test and productive system where:

The development system is used to set up customizing, create BAPIs, implementSAP Notes, do customer specific developments, etc.

The test system is used to consolidate corrections, changes in customizing andcustomer specific developments, and to test those changes before transporting themto the production system

The production system is used for productive operation of the solution – with onlylimited or even no access to customizing and/or repository objects.

Once the SAP General Ledger Migration cockpit is installed in a system, it replaces thecorresponding migration functions that come with the IMG (Implementation Guide), so that allmigration-related functions, reports etc. are only available through the cockpit.

In order to follow the concept of having separate development, test and production systems(as described above), the cockpit has to be installed and operated in each participatingsystem.

2.2 Preparations for SAP GeneralLedger MigrationA migration project is not a purely technical data migration, but must be seen in a widercontext: It is always related to a new general ledger implementation project and mustconsider the existing financials environment as well as business requirements to the targetrelease.

Please note that the blueprint and the customizing of the new general ledger functionalityhave to be finished before the migration to it can be carried out. For further information aboutthe new general ledger, the various phases of a new G/L implementation project and thenecessary preparatory steps for the migration from a business point of view, please refer tothe information provided in SAP Service Marketplace under http://service.sap.com/GL.

2.2.1 Considering Business Implications of theMigrationWhere traditional general ledger solutions required the reconciliation of multiple applications,the new general ledger now provides a unified structure that includes individual ledgers, suchas the cost of sales ledger, profit center accounting and the consolidation staging ledger.

Depending on your specific scenario, the implementation of the new general ledger and themigration to it could mean a significant change to your accounting system and to your livedatabase. These have to be accompanied and approved by your auditor.

http://service.sap.com/GL.


July 2009 11

2.2.2 Choosing a PackageWhen you create a package, choose the scenario that you have ordered and that has beenverified by the scenario validation session (see section 2).

The current version of the cockpit supports the following scenarios:

Scenarios for migration from classic to new G/L:

Scenario 1: Merge of FI ledger

Merging of classic G/L ledger, consolidation preparation ledger and cost-of-salesledger

Scenario 2: Merge of FI, PCA and/or SL ledger

Scenario 1 and additional merging of Profit Center Accounting and SpecialLedger

Scenario 3: Scenario 2 + document splitting (e.g. to support theimplementation of segment reporting)

Document splitting allows for balance sheets on additional dimensions such asprofit center and segments

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

Switch from parallel accounting by parallel accounts to parallel ledger

Scenario 5: Scenario 3 + change to ledger approach for parallel accounting See descriptions of scenarios 2,3,4

Scenarios for subsequent implementation of further functionality within new G/L:

For these scenarios, the service sessions are delivered in a shortened form.

Scenario 6: Subsequent implementation of document splitting

New general ledger has been activated without document splitting; now it has tobe implemented subsequently for one or more company codes.

New general ledger has been activated with document splitting in severalcompany codes; now document splitting is needed in a further company code,where originally document splitting has been deactivated.

Scenario 7: Subsequent implementation of a further ledger

Extend an existing new G/L by a further non-leading ledger

Introduction of a non-leading ledger (parallel accounting was not used before)

Scenario 8: Subsequent change from account approach to ledger approach

Implementation of ledger approach in new G/L for parallel accounting, andreplacement of existing account solution


12 July 2009

2.2.3 Installing the Software and Preparing theSystemAll information you need for installing the SAP General Ledger Migration cockpit software andsetting up the SAP General Ledger Migration cockpit in your SAP systems is provided in SAPNote 1041066.

When you try to blend a package for the first time, the system asks you for anaccess key. If you do not have this access key, contact the SAP GeneralLedger Migration back office.


July 2009 13

2.3 Phases of a General LedgerMigrationThe process tree in the migration cockpit consists of phases that guide you through themigration process from the configuration to the completion of the migration. The phasescontain activities or subphases that in turn contain activities.

There are the following phases:

Setup phase

Checkup phase

Preparation phase

Migration phase

Validation phase

Activation phase

The following chapters describe the content of the individual phases.

It is important to keep in mind that there is a difference between the technical phases in theprocess tree and the migration phases of your project. More information about the migrationphases is provided in the migration guide in SAP Service Marketplace(http://service.sap.com/glmig).

The following table shows typical relations between the phases in the migration cockpit andthe phases of a migration project. It also contains information about when the variousactivities in the process tree are typically executed.

Short description Phase0

Phase1

Phase2

Setup phase Configuration of the migration and BAdIdevelopment

Yes(a) Yes No

Checkupphase

Plausibility checks of the data in preparation tothe actual migration

Yes Yes No

Preparationphase

Preparatory activities directly before themigration

No Yes No

Migrationphase

Activities for technical migration of the dataincl. reconciliation of migrated data

No Yes No

Validationphase

Data check and documentation of results No Yes No

Activationphase

Completion of the migration and activation ofnew general ledger or new functionality

No No Yes

(a) Mandatory for packages 3, 5, 6, 7 and 8 (that is, migration with document splitting or withimplementation of new ledgers)

2.3.1 Setup PhaseIn the setup phase, the configuration of the migration takes place. In addition, the processtree contains references to a number of activities that should be carried out in preparation to

http://service.sap.com/glmig).


14 July 2009

a migration, such as estimating the data volume in the new totals table or checkingmodifications (and bringing them in line with the SAP standard, if required).

The most important activities in this phase are as follows:

Creation of the migration plan

Definition of the participating company codes for the migration as well as the ledgersthat need to be considered by the migration package

Setting the migration date, that is, the date for which open items and balancecarryforwards are migrated.

In addition, the migration can be extended by means of customer-specific BAdIs you candefine in the setup phase. In particular, packages 3, 5 and 6 (migration including documentsplitting) require that you define one or more account assignments for the BAdI forsupplementing open items. Other BAdIs are optional.

Validation of document splitting (available with SAP ERP 6.0) (for packages 3, 5 and 6) andthe configuration of the new non-leading ledger (for packages 7 and 8) are important aspectsto be mentioned here.

2.3.2 Checkup PhaseThis phase includes plausibility checks for the data in relation to the new G/L customizing. Itassumes that the new general ledger has not been activated (valid for migration from classicto new general ledger). The checks cover the existing customizing settings, new G/Lcustomizing, and transaction data. For instance, the new G/L scenarios are checked basedon your current data and settings. You can find detailed descriptions of the individual checksin the documentation for the related activities. In addition to these checks, the checkup phasealso includes check programs for document splitting.

2.3.3 Preparation PhaseDuring the preparation phase, you begin with the preparations for the actual migration. Duringthis phase, current postings must be stopped, and the required compare reports (at least inthe form of a balance sheet and P&L statement) must be created. In addition, the classicgeneral ledger is reconciled with the special ledgers. If you do not transfer balancecarryforwards from the classic general ledger (ledger 0 in table GLT0) or transfer balancecarryforwards from different ledgers, you need to make sure that the data has beenreconciled at account level. You can then upload the reports or lists as attachments for therelated activities (using the Business Document Navigator).

The prior year must be closed by the time you start working on this phase. It is no longerpossible to open the prior year or to reverse clearing postings that were made before themigration date.

2.3.4 Migration PhaseThe migration phase includes the activities you need for the technical data transfer. Makesure to do a data backup for the system before you start with the migration. In this phase, youcreate the work lists for the migration and then transfer the open items and balancecarryforwards from prior years. After that, you can transfer the documents from the currentyear to the new general ledger. If you use packages 3, 5 or 6, you also provide the necessaryinformation for document splitting. Finally, you do a technical ledger comparison. You mayalso do the reconciliation at the level of further account assignments.

If you find out that the migrated data is incorrect, and that corrections or troubleshootingactivities must take place before the migration can be repeated, you can completely reset themigrated data in the next phase (validation phase).


July 2009 15

2.3.5 Validation PhaseIf the data reconciliation was successful on a value basis as well as from the technicalperspective, what needs to be done next (in this phase) is to check the content of themigrated open items and documents from the current year for correctness. This is particularlyimportant if you use BAdIs for supplementing account assignments during the runtime of themigration. Correctness of these postings is of crucial importance for your future businessprocesses. If, for example, you want to create your annual financial statements for each profitcenter and/or segment, the opening balance sheets must be created at this level as well. Youcan then upload the reports or lists you created as attachments to the related activities (usingthe Business Document Navigator).

If necessary, you can reset the migration during the validation phase.

2.3.6 Activation PhaseDuring the activation phase, you complete the migration. In this phase, you also getinformation about activities related to the migration. For example, you can deactivate certainupdates (classic profit center accounting etc.). For more information about this, read thedocumentation for the individual activities.

masterguide glm v1 2

Documents