SAP General Ledger Migration Service

Special Requirements forSubsequent Implementation of Further Functionality withinNew G/L

SAP AG

October 2010

The subsequent implementation of further functionality within new G/L includesfollowing scenarios

Scenario 6: subsequent implementation of document splitting.Scenario 7: subsequent implementation of a further ledger.Scenario 8: subsequent change from account solution to ledger solution.

AvailabilityScenario 6 on mySAP ERP 2004, SAP ERP 6.0Scenario 7 on mySAP ERP 2004 (SP19), SAP ERP 6.0 (SP12), SAP ERP 6.0 EhP2 (SP02)Scenario 8 on SAP ERP 6.0 (SP12), SAP ERP 6.0 EhP2 (SP02)

General

New general ledger must already be live.SAP General Ledger Migration service is required.Scenario 6 and 7 cannot be performed for the same company codes at the same time. Theprojects have to be performed one after the other in case of same migration date or same fiscalyear is required see slide “Scenario 6 and Scenario 7 - in Same Fiscal Year“.

Also refer to SAP Notes and documentation about migration from classic tonew general ledger accounting.

Important Information

The following prerequisites apply for subsequent implementation of documentsplitting:

Document splitting must not be activated in the company codes to be migrated.If cross-company code postings are used

any company code to be migrated must clearly be assigned to one companyall company codes involved must be assigned to the same migration plan

For document splitting criteria that are defined as mandatory field, document summarizationmust not be active for the company codes to be migrated.Subsequent implementation of document splitting must not be performed in the same fiscalyear as the migration from classic to new G/L.As of migration date all relevant account assignment fields (e.g. segment) must be filledduring posting.The technical prerequisite of the migration functionality is SAP Note 1086181. Also refer to therelated notes.Validation of document splitting is strongly recommended (only available with SAP ERP6.0).

Also refer to the SAP Notes and documentation about document splitting.

Prerequisites for Subsequent Implementationof Document Splitting (Scenario 6)

Preparation Steps for SubsequentImplementation of Document Splitting

Before posting into the new fiscal year the following preparations must be inplace:

General ledger migration cockpit is installed and a migration plan for subsequentimplementation of document splitting is created.Document splitting is fully customized in the production system, but not live.Validation of document splitting is configured and activated.All relevant master data (i.e. profit centers, segments, business areas, if used as documentsplit criteria) are finally and completely defined in the production system.Profit center and business areas have to be assigned to all relevant objects, e.g. materialmaster, cost centers.Segments are assigned to the profit centers.Interfaces into accounting are changed. Relevant account assignments are sufficientlyhanded over. (For HCM see also SAP Note 1039346.)Document splitting characteristics can only be used if the corresponding scenarios are alreadyassigned to the relevant ledgers in the production system.

If document splitting is already active for some company codes, the settings ofdocument splitting cannot be changed.

ExamplesNew characteristics must not be added.Existing document splitting characteristics cannot be deleted.Existing characteristics must not be changed (for example switch to balance 0 or required-entry-field).See also SAP Note 891144.

In one system subsequent implementation of document splitting in variousclients is only possible one after the other.

All ledgers that have relevant document splitting scenarios assigned must bemigrated.

Important Information for SubsequentImplementation of Document Splitting

The following prerequisites apply for subsequent implementation of ledgers:

The subsequently implemented ledger must not be the leading ledger (no switch possible).The general ledger accounting scenarios required in the new ledger as well as any customerfields are already assigned to at least one of the existing ledgers from which data can becopied or you need to post/repost the balance carry-forward per characteristic duringmigration. (In cases involving more than one financial statement characteristic, combinationsof their values must also be taken into account).The currencies required in the new ledger are already updated in the leading ledger.If document splitting information is needed in this ledger, the document splitting functionalitymust be already active with the necessary split criteria or implemented separately (seemigration scenario 6).SAP General Ledger Migration service is required to build the data of a subsequentlyimplemented ledger.Subsequent change from account to ledger solution (scenario 8) must not be performed in thesame fiscal year as the migration from classic to new G/L.The technical prerequisite of the functionality is SAP Note 1229202 or 1272843 (EhP4). Alsorefer to the related notes.

Prerequisites for Subsequent Implementationof Ledgers (Scenarios 7 & 8)

Preparation Steps for SubsequentImplementation of Ledgers

Before posting into the new fiscal year the following preparations must be inplace:

General ledger migration cockpit is installed and a migration plan for subsequentimplementation of a further non-leading ledger is created.The migration plan is defined for all relevant company codes and the ledger to beimplemented.The ledger to be implemented subsequently is activated in customizing (V_FAGL_T882G)and assigned to a migration plan.

Detailed information can be found in the migration guide for subsequentimplementation of further functionality within new G/L.

To decided whether you have to perform a migration or not refer to SAP Note1378630.Also refer to the SAP Notes and documentation about general ledger migration.

Important Information for SubsequentImplementation of Ledgers

The subsequently implemented ledger must not be activated in customizing(V_FAGL_T882G) without an existing migration plan for the activated company code andledger

If the ledger was activated without migration plan assignment, inconsistencies in previousyear data and balance carry forward values have to be resolved. (For assistance fromSAP contact remote consulting XX-RC.)

As soon as the subsequently implemented ledger is assigned to the company code in themigration plan documents are posted into the new ledger.If the subsequently implemented ledgers shall have a fiscal year different from the sourceledger: see slides “Subsequent Implementation of a further ledger with a different fiscalyear“

If the subsequently implemented ledger shall have a different fiscal year, i.e. the beginning ofthe fiscal of the new ledger shall be different from the beginning of the fiscal year of thesource ledger, the following applies:

The migration date must be the begin of the fiscal year of the source ledger.For the new ledger a special fiscal year variant with two shortened fiscal years must bedefined and assigned to the new ledger (see example on the following slide)

The begin of one of the shortened fiscal years must be identical to the begin of thefiscal year of the source ledgerThis special fiscal year variant must be defined so far in the past as open itemsexist

SAP Notes 1507535 and 1508986 must be implemented

Subsequent Implementation of a further ledgerwith a different fiscal year

ExampleSource ledger: AA, fiscal year variant XX (July – June), not year dependentMigration date = July 1, 2010 (begin of fiscal year of the source ledger)New ledger : BB with fiscal year = calendar yearAs the fiscal year for the new ledger is different from the fiscal year for the source ledger, a special fiscal yearvariant YY must be defined and assigned to the new ledger BB

Subsequent Implementation of a further ledgerwith a shifted fiscal year

Fiscal year variant YY:year dependentfiscal year 2009 and 2010 must bedefined as shortened fiscal years(each shortened year contains 6months)calendar year 2009 and less must bedefined with year shift -1calendar year 2010 contains month 1to 6 with year shift -1 (representingfiscal year 2009) plus month 7 to 12with year shift 0 (representing fiscalyear 2010)calendar year 2011 and following mustbe defined with year shift 0 (fiscal yearcorresponding with calendar year)

Scenario 6 and Scenario 7 - in Same FiscalYear

Migration dateFinish closing of

previous fiscal year

Phase 0 Phase 1

Prepare document splitcustomizing inclusively allsettings necessary for newledger (e.g. characteristicsonly updated in the newledger)

Ensure account determinationfor all splitting characteristics

New ledger must be definedand scenarios must beassigned to the ledger but theledger must not be activatedfor the company codes

Create scenario 6 and performsetup phase ( include allrelevant + leading ledgers inthe migration plan)

Postings into oldfiscal year

Postings into newfiscal year withdocument splitvalidation (includingsplit characteristicfor new ledger *)

No ledger specificpostings into newledger possible

Finish scenario 6

Create scenario 7for subsequent non-leading ledger andperfom all phasesback-to-back

* Postings with ledger groups using the new ledger, but not the leading ledger:split characteristics only updated in the subsequent (not yet activated) ledger willnot be validated

© SAP 2009 / Page 13

Copyright 2009 SAP AGAll rights reserved

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 changedwithout prior notice.

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

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective 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 andassociated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains 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. 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.

Alle Rechte vorbehalten.