ac212 - migration to the new general ledger

5/26/2018 AC212 - Migration to the New General Ledger

1/210

SAP AG 2006

SAP AG 2007

SAP ERP 2005

2006/Q2

Material number: 50083987

Contact for Buying any SAP Module Materials: [email protected] Visit: www.sapfans.co.nr


2/210

SAP AG 2006

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 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 the Open Group.

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

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World WideWeb 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 technologyinvented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.



3/210

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products andservices 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 bereproduced, 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 otheragreement 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 theaccuracy 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 particularpurpose, 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 controlover 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.



4/210

SAP AG 2006



5/210

SAP AG 2006



6/210

SAP AG 2006

Duration: 3 daysContent: Migration scenarios 1 3Certification option: No

AC212 course version / coll. 63Duration: 4 or 5 daysContent: Migration scenarios 1 5Certification option: Yes

New GL Migration

It is envisaged that in the second half of 2007, SAP will offer participants on the three day course

the option of attending a type of delta workshop to learn the differences between both course

versions quickly and easily.



7/210

SAP AG 2006

These course materials are not suitable for self-learning. The information you will get from your

course instructor is essential to completing the materials.

In some cases, there may not be enough time to perform all the exercises during the course. Theexercises provide additional examples that are covered during the course. You can also go through

the exercises yourself after the course, to reinforce what you have learnt.



8/210

SAP AG 2006



9/210

SAP AG AC212 1-1

SAP AG 2006

Unit 02: The Subproject Basics

Unit 03: How Might a New GL Project Proceed?

Unit 04: New GL Migration Service and Standard Migration Scenarios

Unit 05: Configuring the New General Ledger (with Regard to Migration Scenario 2)

Unit 06: Working with/in the Migration Cockpit

Unit 07: Migration Based on Migration Scenario 2


Unit 09 Appendix 1: Preview of Migration Scenarios 4 and 5

Unit 10 Appendix 2: Experiences

Unit 11 Appendix 3: New GL Migration and Industries



10/210

SAP AG AC212 1-2

SAP AG 2006



11/210

SAP AG AC212 1-3

SAP AG 2006



12/210

SAP AG AC212 1-4

SAP AG 2006

The individual advantages will be shown briefly in the following slides...

Despite all the new features, the interfaces for entering the data and for posting are almost identicalwith those of previous releases.

Important: The advantages listed can be used in combination or independently of one another.



13/210

SAP AG AC212 1-5

SAP AG 2006

The field is now stored in the General Ledger too. This means that you are nolonger obliged to activate the cost of sales ledger 0F to create a profit and loss statement in

accordance with cost of sales accounting.

The field (and the field) is also included in the General Ledger.You can therefore use the General Ledger to conduct management analyses.

The (characteristic/category) available is the field. You can use this to carry outsegment reporting.

The table structure in the New General Ledger can be . This means that can be included and their totals updated.

are available for all the purposes listed above.



14/210

SAP AG AC212 1-6

SAP AG 2006

(and/or two cost centers, profit centers, or business areas)

The document splitting function obviously your ability to yourdataset, as the is much improved.

Both the appearance and entry procedures for the FI document are identical to those in previousreleases.

The input tax rate is taken to be 10 %.

We currently recommend that the is on the basis of the informationand support this procedure. The profit center can in turn be derived from a cost center, a CO internal

order, or a project, for example.

A BAdI is also provided for deriving segments, in case deriving them on the basis of the profit

center is not a feasible option.



15/210

SAP AG AC212 1-7

SAP AG 2006

The layout/display variant of the document sorts (in ascending order) by segment with subtotals on thecolumn!

It is important that you activate in order to ensure uniform splitting of thecharacteristic (or any other entity)! Uniform segmentation means that a is reached for the corresponding entity in each and every posted document.

Splitting documents online dispenses with the need for various period end activities such as (program ) and (program ).

Document splitting also works with subsequent processes such as payment (entered manually orperformed in a payment run). Any cash discounts or cash discount expenses that may occur are

distributed across the entities in accordance with the amount of the original postings (for example, a

vendor invoice).



16/210

SAP AG AC212 1-8

SAP AG 2006

The following now occurs in

The following now occurs inIn

a

for wages/salaries(

account 420000) is entered!

is also assigned and is used to derive

the

.

In

a

for wages/salaries

(

account 420000) is entered!

is also assigned and is used to derive

the

.

420000 + 500,

The value for

is now transferred by a

to the

however, the cost center is assigned to

.

The value for

is now transferred by a

to the

however, the cost center is assigned to

.

420000 + 500,

420000 - 500,

0,

420000 + 500,

This slide shows the using the characteristic orcriterion as an example. Real-time integration can also be defined for the criteria and , however. The selection is not aneither/or decision - you can also activate real-time integration for all of these characteristics at once.

Postings are made in (for each CO document). A reconciliation ([only] summarized foreach expense account or cost element) using the reconciliation ledger in Cost Element

Accounting with transaction KALC is therefore not necessary.

It is a that does not require . However, clearing accounts are still

required in SAP ERP, for example, for cross-company code transactions. You can jump from the CO document to the FI follow-on document generated in real-time

in order to analyze the CO document in more detail (with the corresponding

authorizations).

This is a considerable improvement in making accounting documents more comprehensible.

The CO FI real-time integration documents can be logged and analyzed with a .



17/210

SAP AG AC212 1-9

SAP AG 2006

Example:

One ledger in New General Ledger Accounting has the role of "leading" ledger. This ledger isgenerally used to map group accounting.

Other ledgers can be used in addition to the leading ledger for parallel accounting in the NewGeneral Ledger.

In an SAP ERP context, this is known as the

This does not refer to ledgers belonging to the Special Ledger component, for example, forthe R/3 Enterprise release.

Parallel accounting can still be mapped, as previously recommended, using additional accounts( ). In this case, there is only one ledger (the leading ledger) in the General

Ledger.

In SAP ERP, both the ledger approach (in the New General Ledger) and the accounts approachshould initially be regarded as equal see also

A ledger in the New General Ledger is always similar to a general ledger, and is therefore not thesame as a special ledger belonging to the FI SL component.



18/210

SAP AG AC212 1-10

SAP AG 2006

1000

9900

1I

1I

1I

1402

EUR20,00Input tax154000403

1000A0400EUR200,00Purch. services417000402

EUR220,00-Vendor V1000V10003111000

In order to evaluate information about

and

(at totals level) in the classic SAP world, the system has to generate

in addition to the FI document:

Document Number: 1900000000

You can call the documents that follow on from the original FI document in the document display(transaction) from the menu path

.



19/210

SAP AG AC212 1-11

SAP AG 2006

1000

9900

1I

1I

1I

1402

1402

1402

EUR20,00Input tax154000403

1000A0400EUR200,00Purch. services417000402

EUR220,00-Vendor V1000V10003111000

about , and

Document Number: 1900000006

You can call the documents that follow on from the original FI document in the document display(transaction) following the menu path

.



20/210

SAP AG AC212 1-12

SAP AG 2006

We generate a balance sheet and profit and loss statement at the profitcenter / store level. The function for online document splitting enables a

very high degree of automation

The elimination of manual postings and other processes at the end ofthe period significantly reduces the number of errors and thus greatlycontributes to ensuring compliance

Overall, we have attained an unprecedented level of data quality andincreased transparency by 30 % 40 %

New General Ledger Accounting provides optimum support for parallelaccounting

has worked with the New GL in different countries since 2006

Considerable degree of automation thanks to document splitting a balance sheet and profit andloss statement are generated at market (PC) level.

Since a lot of work that is normally carried out at the end of the period can now be performed ona transactional basis, the number of errors is significantly reduced which in turn plays a

significant role in ensuring compliance.

About compliance: Compliance is the duty of a company to ensure that current legal statutes andregulations are observed.

The quality of the data increases considerably transparency is improved by 30 40 %.

There is optimum support for parallel accounting.

Author's note: The Metro Group uses the so-called accounts approach for parallel accounting.



21/210

SAP AG AC212 1-13

SAP AG 2006



22/210

SAP AG AC212 1-14



23/210

SAP AG AC212 2-1

SAP AG 2006

Unit 01: New GL An Overview of the Main Functions

Unit 03: How Might a New GL Project Proceed?











24/210

SAP AG AC212 2-2

SAP AG 2006



25/210

SAP AG AC212 2-3

SAP AG 2006



26/210

SAP AG AC212 2-4

SAP AG 2006

A is used totransfer data from the legacy system to the SAP systemwith activated New General Ledger Accounting.

A transfersthe data from classic General Ledger Accounting to

New General Ledger Accounting.

In the case of both a migration and a new system implementation with subsequent legacy datatransfer, you have to initiate a separate project with the corresponding project phases for the

procedure.

This implementation project or New GL project will have to address and resolve both technical andprocess-related aspects.

With regard to the default configuration of an SAP system and the activation of the new GL, consultSAP Note 756146.



27/210

SAP AG AC212 2-5

SAP AG 2006

you treat the implementation of the New GL, and the

too, as an : For example, we recommend you carry out the

migration as part of a technical upgrade to SAP ERP.

A migration or implementation of the New GL is not only a . In many

cases (depending on the content of the project) will also occur.

(Implementation of New GL)

The term "project content" stands for the precise description of the initial situation. For example:

Which SAP components do you already use?

Are you required to portray your accounting figures according to more than one set of accountingprinciples (using parallel accounting)?

....

What is your target scenario like?

Which characteristics do you want to use in your valuations in New General Ledger Accounting?

Do you want to produce a profit and loss statement according to cost of sales accounting orperiod accounting?

.

The technical is a project that you need to finish first.

The next project is then the . Part of this projectdeals with the migration of the classical data.



28/210

SAP AG AC212 2-6

SAP AG 2006

It is feasible to convert the previous "parallel logic", but the replacement ofthe company code solution is not supported.

*

This applies for the (original) FI as well as for the FI-AA component.

There is nothing stopping you from retaining the existing currency logic.

The offers a corresponding option or "tool"

The migration tools are used to transfer the data from classic Accounting to New General LedgerAccounting and, where necessary, to enhance the general ledger with New General Ledger functions

(such as document splitting).

All the other implementations need to be scheduled in a different project, possibly in a project oftheir own.

The of complete segment reporting . Inthis context, New General Ledger Accounting only provides concerning the

. For complete zero-balance opening balances for the Segment characteristic (or other

corresponding entities), other steps (postings) are necessary.



29/210

SAP AG AC212 2-7

SAP AG 2006

Time(t)

Activation date for new GL

of the current (or future)

No single documents are transferred from phase 0. For accounts that are not managed

on an open items basis, the balance carryforward is transferred (to the migration year).

OIs (=> from G/L accounts managed on an open items basis, as well as customer andvendor OIs) are migrated individually.

Documents from phase 1 are completely posted subsequently in the migration (by meansof programs). Any document split will be (post)processed.

New General Ledger Accounting is active and uses the configured functions.

Latest activation date for validation (for

migration with document splitting)

To make the phase model easier to visualize, here is an example with concrete figures:

Recommended migration date: 01/01/200X

Activation date for New General Ledger Accounting: 05/01/200X, for example

Activation date for the validation: 01/01/200X (or even before!)

Now assume the following case:

Recommended migration date: 01/01/200X or 01/01/200X+1 depending on the documentvolume

Activation date for New General Ledger Accounting: 02/01/200X+1, for example

Activation date for the validation: 01/01/200X (or even before!)

It is possible to postprocess a document split for theaccounts managed on an open items basis of a document from phase 0 that has not yet been cleared.

If document splitting is going to be activated in phase 2, acheck should be performed on documents in phase 1 to verify that they can be used in New General

Ledger Accounting. This check should be run when the documents are entered (for the first time).

This makes it easier to subsequently post the documents during the migration. The check is

performed as part of validation (more information later in this course).



30/210

SAP AG AC212 2-8

SAP AG 2006

Migration date Activation date for new GL

With regard to thechange in open items

administration for anaccount, you shoulddefinitely consult SAPNote

With regard to thechange in open itemsadministration for anaccount, you shoulddefinitely consult SAP

Note

Migration to the New General Ledger: If data migration to theNew General Ledger is planned using a migration type which requires document splitting, you

should make sure that changes are made to open item administration in phase 1 and phase 2.

Phases 1 and 2 indicate the period between the migration date and the end of the actual migration

(migration complete indicator is set).

This means: the programs RFSEPA02 (set up open item administration after master record change)and RFSEPA03 (remove open item administration after master record change) must not be started.

This also means that you have to recreate an open items account if you need one.



31/210

SAP AG AC212 2-9

SAP AG 2006


Test the complete New GLconfiguration in a

Optional: Start the (see

later) and test migration(s)

in a test system

Optional: New GLCustomizing

(PROD);

Complete New GLCustomizing

Start the and testmigrations (with the most

recent data possible) in a

using the MigrationCockpits, includingactivating the New GeneralLedger

Work through theactivation phase in the

Migration Cockpit in the including

Since the New GL should already be configured by the end of phase 0, you must allow yourselfsufficient lead time to set up and test the New General Ledger.

According to the Business Blueprint, document splitting is to be used in the New GeneralLedger, so you can still complete the configuration at the start of phase 1.

The optional activities in phase 0 are useful as they enable you to consider the issues involved in themigration at an early stage.



32/210

SAP AG AC212 2-10

SAP AG 2006


Test the New GL configuration in a

Complete New GL Customizing (PROD);

Start the (seelater) and work throughthe set-up phase, of the document splitsee slide notes.

Test migration(s) with theMigration Cockpit in a see slide notes.

Testmigration(s) with theMigration Cockpit in a

with the MigrationCockpit, includingactivating the new GL

Work through theactivation phase in theMigration Cockpit in the including

In case you are stillunsure how to assign your company codes to one or more migration plans in phase 0, you should

work with a kind of dummy migration plan. This can result in relatively complex follow-on

activities in phase 1 if the dummy assignments prove to be incorrect, however. For this reason, you

should already have a clear understanding of the assignments by the end of phase 0.

In SAP ERP 2005, you should activate for document splitting on themigration date, with validation level error message, .

can uncover errors that may then alleviate problems in phase 1.Example: An open item that has not been cleared at the time of the test migration and was not

originally entered in conformity with New GL standards is cleared at the end of phase 0. This means

that it no longer appears as a problem document in productive migration in phase 1.On the other hand, test migrations in phase 0 help you develop an understanding of the kind of

problems that may occur, and enable you to recognize the importance of "clean" New GL

Customizing for data migration.

Since the New GL should already be configured by the end of phase 0, you must allow yourselfsufficient lead time to set up and test the New General Ledger.



33/210

SAP AG AC212 2-11

SAP AG 2006

after data migration, You cannot activate theNew General Ledger for individual company codes alone.



34/210

SAP AG AC212 2-12

SAP AG 2006



35/210

SAP AG AC212 3-1

SAP AG 2006

Unit 01: New GL An Overview of the Main Functions Unit 02: The Subproject Basics











36/210

SAP AG AC212 3-2

SAP AG 2006



37/210

SAP AG AC212 3-3

SAP AG 2006



38/210

SAP AG AC212 3-4

SAP AG 2006

to SAP ERP and

[totals table

]

Members of the project team

(e. g.

) about the functions of the

Precise

of

own

From the initial

(Business Blueprint), the extent towhich the New General Ledger can and will be used in the future

in a test client/system

Begin the

(see also next slide)

with SAP

of

without already having activated New General Ledger Accounting

SAP master data object maintenance keyword:

of figures in the classic accounting world

Year-end closing activities and

Work with and in the

If required: BAdI programming

) in a test system

Evaluation of migration data and

if necessary

of the no longer required

SAP ERP:

If you upgrade (directly) to SAP ERP 2005 (ECC 6.0), you have the advantage of being able to use in the migration.

It is of course still possible to migrate data with SAP ERP 2004 (ECC 5.0).

After the technical upgrade to SAP ERP, check whether the following entries exist in yourproduction client in the table :

TCode Business Transaction Bus. Trans. Variant

FB1D 1010 0001

FB1K 1010 0001

FB1S 1010 0001FBRA 1020 0001

If this is not the case, transport the entries using a transport request from client 000 to the productionclient.



39/210

SAP AG AC212 3-5

SAP AG 2006

Import the

see SAP Note

for a from SAP e.g.:

aimed at identifying the migration scenario

using the

and system analysis

(Final) Continue to work productively in parallel in classic accounting

of , a scenario-based , to thecustomer

Customer downloads the corresponding add-ons

) in a test system with the latest production data

for test validation

Carry out the (customer)(with [technical] weekend support by SAP, if necessary)

the migrated data and postprocess it if necessary

the and work productively

the

Components of the New GL Migration Service

English terms that are frequently used for the SAP Migration Service to the New General Ledgerand its components:

Service name: SAP General Ledger Migration

Scenario validation and system analysis session

Test validation session

Service sessions are comparable with SAP GoingLive Checks: These are several sessions atvarious times within a service.

You can get the Migration Cockpit (immediately) after contracting. The service session to

validate the scenario does not have to take place beforehand. In other words, the sequence of thenamed service scenarios is not "carved in stone".



40/210

SAP AG AC212 3-6

SAP AG 2006

support for the project by the customer e.g.: How quickly can test systems be set up? How long do transports take? How many people are assigned to the project number of project team members?

And above all: The

in matters relating to the

.

the experience(

and

) and the quality of the consultant.

thefamiliarity of the consultant with the customer's system andtheprocessesthat take place there.

the complexity of thecustomer's system landscape(applications used).

thenumber of migration objects to be processed keyword

.

(and of course) the : The most important question is:

the ability to keep to project planning deadlines: Postponing "going live" by one, two or more monthsresults in the need for additional testing activities.

There is to the question of (including the subproject).

You can find out about the actual length of projects in unit 10. You will see that it is not possible tomake any general assumptions regarding this ...



41/210

SAP AG AC212 3-7

SAP AG 2006

general questions about migration that cannot be assigned to a more specificcomponent

termination of migration programs

problems with applications or consultant requests

general questions about the New GL Migration Service (incl. service orders)

delivery questions about service sessions

questions about the Migration Cockpit

questions about the DMIS add-on

questions about providing the license key

technical problems in connection with the delivery of service sessions

requests for remote consultation (subject to fee) as part of the migration

For sample questions, see notes page.

For sample questions, see notes page.

FI-GL-MIG:

We would like to migrate to New General Ledger Accounting. How should we proceed?

The following termination occurred in the test client when we tried to transfer the OIs fromphase 0:

FI-GL-MIG-BO:

How can I get hold of the SAP migration tools?

Where can I find more information about New GL Migration Back Office?

I would subsequently like to implement document splitting are migration tools already

available for this?

Where can I find the migration handbook?

FI-GL-MIG-TL:

What are the technical prerequisites for using the Migration Cockpit?

What is the current SP status of the DMIS add-on?

We want to test the migration, but get a dialog box asking for the license key what shouldwe do?



42/210

SAP AG AC212 3-8

SAP AG 2006

on the under

You can, of course, the of the

=> Portal menu option In the navigation tree, choose

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

In the General Ledger (=> see path above) you will find other informative documentsabout the New General Ledger in general, as well as some SAP Tutorials about this topic.



43/210

SAP AG AC212 3-9

SAP AG 2006



44/210

SAP AG AC212 3-10



45/210

SAP AG AC212 4-1

SAP AG 2006

Unit 01: New G/L An Overview of the Main Functions Unit 02: The Subproject Basics

Unit 03: How Might a New G/L Project Proceed?

Unit 05: Configuring the New General Ledger (with regard to Migration Scenario 2)






Unit 11 Appendix 3: New G/L Migration and Industries



46/210

SAP AG AC212 4-2

SAP AG 2006



47/210

SAP AG AC212 4-3

SAP AG 2006



48/210

SAP AG AC212 4-4

SAP AG 2006

Identify the migration scenario to be used

(remote) (telephone)

Test and validate the previously identified scenario directly on the customersystem

(the customer performs the migration)

Predetermined migration process by means of a preconfigured process tree

Status management

Extensive log connection

(remote) (telephone)

Check and validate the test migration on a customer test systemkeyword: Quality assurance

5. (One-off) (technical support)

The support cover problems that arise due to incomplete New G/LCustomizing settings (e.g. document splitting)

Detailed information about the new terminology listed above:

: SAP service for migrating data from the classic G/Lto the new general ledger

(SV): Service event for checkingwhether the migration package ordered by the customer matches the required business scenario.

To do this, SAP extracts the required information from the customer system and evaluates the

data in one of its own systems.

New G/L Migration Cockpit: User interface (UI) in which the customer performs the migration,comprising the and the

Process monitor in which you can see the status and the results of themigration.

Similar to an IMG, the Process Tree maps all the steps to be worked through. Theseare dependent on the package and are thus put together on a scenario basis. The customer therefore

receives tailor-made guidance through the migration process.

(TV): Service event in which technical validation checks can becarried out in the migrated data.



49/210

SAP AG AC212 4-5

SAP AG 2006

Although SAP its customers use the new G/L, the is to use it.

Previous that particular arerequired for safe, error-free migration to the "new world"

This guarantees that that will arise for manycustomers in the same way, .

This (only) an

.

The preparation and execution of the technical migration of the source data from classic applicationsto the new general ledger are the main components of a migration project, and have to be performed

with the utmost care. The main aim is to ensure proper accounting procedures during the migration.

To guarantee maximum security, SAP accompanies each migration project with a . This obligatory technical service is based on standard migration scenarios and includes a

scenario-specific new G/L Migration Cockpit and two service sessions to ensure the quality of the

data and the migration project.



50/210

SAP AG AC212 4-6

SAP AG 2006

E-Mail to: [email protected]

Before you start the migration project, you should already have launched the new G/Lproject. The migration is (only ever) a subproject of the new general ledger implementation project

albeit an incredibly important and complex subproject.



51/210

SAP AG AC212 4-7

SAP AG 2006

General business data

General questions about the systemlandscape

Questions about the new G/L project

Questions about the possibility of mappingparallel accounting

Questions about customer fields Questions about FI-SL Questions about the new G/L scenarios

Questions about document splitting

After you have completed the questionnaire, return it (by E-Mail) to SAP:

The questionnaire is only available in English.

From the page of the questionnaire that has been shown here, you can already see that it isimpossible to answer the questions if you do not have a certain knowledge of the options and

functions provided by the new general ledger.

Try to answer the questions as precisely as possible, as SAP uses these answers to drawconclusions about your migration scenario. Incomplete or incorrect answers prolong the process of

determining the right scenario for you unnecessarily.



52/210

SAP AG AC212 4-8

SAP AG 2006

After any remaining open items have been

resolved (by E-Mail or by phone), you discussand agree on the migration scenario you needtogether with SAP

(between you and SAP) over the migration scenario

to be used, takes place for the chosen migration scenariousing the service.

The service includes the parts presented in this unit.

The service is free of charge.

You will find information about the price in the slides that follow.


53/210

SAP AG AC212 4-9

SAP AG 2006

Based on the questionnaire alone, does SAP thinkit can identify the best possible

migration scenario?

In other words: from the customer system and transferred to SAP,where it is analyzed - the result is then compared with the chosen migration scenario.

The data analysis is performed after the Data Collector has been started and the data transferred toone of SAPs own systems by the New G/L Migration Back Office, which was set up specially for

this purpose.

The SV session not only checks the previously chosen migration scenario, it also determines theactual (technical) situation in the customer system and reveals potential obstacles that you may have

to overcome to arrive at the desired situation.

The contract is created on the basis of the desired scenario.


54/210

SAP AG AC212 4-10

SAP AG 2006

This part of the service is executed

by the (SAP) Migration Back Office for the customer You need an

, comprising:

the Basis plug-in (in the standard system since SAP ERP)

the Service Tool for Applications plug-ins ()

You are provided with the results of the SV service session and you can evaluatethem accordingly.

plug-in Open the URL in your browser and download the file to your frontend pc.

ST-A/PI is small (=> size: 2 4.5 MB) and does not overlap with production coding in any way.You can import it at any time (=> TCode ). Users should not need to log off in the process.


55/210

SAP AG AC212 4-11

SAP AG 2006

After the Scenario Validationservice session, SAP provides youwith the in the form of a.

- the productive and non-productive company codes- the fiscal year variants for the company codes- activated components (CO, EC-PCA, SL, )

- the currency types used in or assigned to thevarious ledgers

- master data checks e.g.: do P&L accounts existthat are managed on an OI basis? How many profitcenters are there?

- document and line item checks- Do postings across company codes exist- Quantity checks: Number of table entries- ...


56/210

SAP AG AC212 4-12

SAP AG 2006

The choice of scenario is examined in detail.

Important system information is already provided forthe customer at the start of the project.

The findings can be used to complete the project plan.


57/210

SAP AG AC212 4-13

SAP AG 2006

Migration of the classic general ledger (table / ledger ), the

consolidation staging ledger (table / ledger ) and the cost-of-sales ledger (table / ledger )

Note:Custom fields that are only required or posted at line item level can be migrated in thisscenario too.

Migration of the classic general ledger (table / ledger ), the

consolidation staging ledger (table / ledger ) and the cost-of-sales ledger (table / ledger )

Note:Custom fields that are only required or posted at line item level can be migrated in this

scenario too.

of the SAP General Ledger Migration service applies for each anddepends on the scenario. For more information, return the questionnaire to the E-Mail address:

[email protected].

You can find the questionnaire under: http://www.service.sap.com/glmig


58/210

SAP AG AC212 4-14

SAP AG 2006

Migration of objects from scenario 1 and additional transfer of profit centeraccounting (table / ledger ) and additional transfer of values fromspecial ledgers (table / ledger )

Comments: "Z ledgers" contain customer fields, for example, that can or should be

evaluated at totals level.

Migration of profit center accounting (only) allows the evaluation of deficitsor surpluses in the individual profit centers in this scenario (classic profit centerapproach).

- In this scenario, SAP assumes that you in the SAP system.

Migration of objects from scenario 1 and additional transfer of profit centeraccounting (table / ledger ) and additional transfer of values fromspecial ledgers (table / ledger )

Comments: "Z ledgers" contain customer fields, for example, that can or should be

evaluated at totals level.

Migration of profit center accounting (only) allows the evaluation of deficitsor surpluses in the individual profit centers in this scenario (classic profit centerapproach).

- In this scenario, SAP assumes that you in the SAP system.

of the SAP General Ledger Migration service applies for each anddepends on the scenario. For more information, return the questionnaire to the E-Mail address

[email protected].



59/210

SAP AG AC212 4-15

SAP AG 2006

The introduction of document splitting enables you to evaluate the

, or fields, as well as on thebalance sheet (in the new general ledger).

The introduction of document splitting enables you to evaluate the

, or fields, as well as on thebalance sheet (in the new general ledger).

of the SAP General Ledger Migration service applies for each anddepends on the scenario. For more information, return the questionnaire to the E-Mail address

[email protected].



60/210

SAP AG AC212 4-16

SAP AG 2006

(in the new G/L)

Migration of parallel accounting, mapped in the SAP system by the account

approach. During the migration, a switch is made from the account approach to

the ledger approach (in the new G/L).

(in the new G/L)

Migration of parallel accounting, mapped in the SAP system by the accountapproach. During the migration, a switch is made from the account approach tothe ledger approach (in the new G/L).

(in the new G/L)

Migration of parallel accounting, mapped in the SAP system by the account

approach. During the migration, a switch is made from the account approach to

the ledger approach (in the new G/L) and document splitting is introduced.

(in the new G/L)

Migration of parallel accounting, mapped in the SAP system by the accountapproach. During the migration, a switch is made from the account approach to

the ledger approach (in the new G/L) and document splitting is introduced.

The migration is tailored to the customers requirements, on the basis of one of

the five standard scenarios that has the most similarities to the customer

scenario.

The migration is tailored to the customers requirements, on the basis of one of

the five standard scenarios that has the most similarities to the customerscenario.

of the SAP General Ledger Migration service anddepends on the scenario. For more information, return the questionnaire to the E-Mail address:

[email protected].


In SAP literature you will also come across the terms service-based migration and project-based migration:

Service-based migration: Migration with a scenario that is covered by a migration package. Therequirements of the project are therefore covered by the service. The migration scenarios 1 5

are included in this.

Project-based migration: Migration with a scenario for which there is no standard migrationpackage. The requirements of the migration can therefore not be covered by the service in full. In

such cases, migration packages can be used, however, additional, project-based consultation is

required.


61/210

SAP AG AC212 4-17

SAP AG 2006

The migration tools available in the standardsystem do not necessarily support in full the implementation of a new application

in the new general ledger.

: In release you did not work with classic Profit Center Accounting(=> ), but would like to use and evaluate profit centers in the new G/L.Although this is perfectly , it requires, in addition to the actual migration activities,a lot of , as well as in most cases .

The "Profit Center Implementation" example given on the slide is not a clear, service-basedmigration. SAP cannot simply categorize such a situation as project-based migration

The customer will have to put the data in a standard scenario/standard package

(=> in the given example, on package 2 or 3) and carry out the additional activities listed.

You want to use new general ledger accounting to prepare for consolidation without havingwriting data to the table GLT3 beforehand.

You want to use the SAP object "business area" in the new G/L without having previously savedthis in the totals table of the classic general ledger (=> GLT0). Consult SAP Note 321190 in

connection with the business area object too. If you want to carry out segment reporting in the new G/L, SAP recommends you derive the

segment object from the profit center master record. If you choose to opt for a different solution

for deriving segments (=> e.g. derivation by means of a BAdI), you are responsible for the

corresponding implementation.

You do not necessarily have had to have worked with the cost-of-sales ledger(=> table GLFUNCT) in previous releases to evaluate the functional area object (for a P&L

statement based on the cost of goods sold).

You map parallel accounting using the company code solution (or FI-SL ledger solution) and

plan to use the ledger solution in the new general ledger.

You are using a number of different industry solutions and will migrate to the new generalledger.


62/210

SAP AG AC212 4-18

SAP AG 2006

This part of the Migration Service is (again) by

the (SAP) Migration Back Office

A

(by the customer) since the service session for scenario

validation, for example.

A the current are

for the , for example.

The purpose is also to test and validate a by the

customer for . It is also intended to

ensure a consistent system landscape after the migration.

The second service session takes place after one of the final migrations, and is used to validate themigrated test data. Technical plausibility checks take place in the migrated test data and application-

specific compatibility checks are made with regard to the migration scenario.

Business checks, such as the validation of a segment area structure in accordance with IFRS, mustbe covered by the customer or partner in the user test after the test migration.

The session should take place after a migration that provides valid results, but not too close to theproduction migration, to allow sufficient time to resolve any new questions that may arise.


63/210

SAP AG AC212 4-19

SAP AG 2006

RegisterwithSupport!


64/210

SAP AG AC212 4-20

SAP AG 2006

Comprises internal or externalconsultants

Works on and defines the new G/Lconcept

Configures the migration activities

Carries out the migration project

Supports the customer project

Provides scenario-based,

preconfigured migration packages

Establishes contact withconsultants in case extendedmigration functions are required

Provides technical quality checks

- Accompaniment through clearly structured (sub-)project flow - Flexibility with regard to customer

requirements

- Low project costs and minimization of risk - can assess costs and risks in advance

It is clear that with the new G/L migration project, SAP cannot, nor wishes to handle the entire newG/L project. Rather, the service is intended to provide support for the customer.

The mentioned in the slide can be an SAP consultant, an SAP partner, aconsultant from a different consulting company or an employee in the customers IT department.

The for consultants is .


65/210

SAP AG AC212 4-21

SAP AG 2006

Mgl.Poss.contract

foraddlconsultation

incl.

announcedtechn.

BOs

upport

Legend:

BO = Migration Back Office

The SAP New G/L Migration service guarantees the quality of a new general ledgermigration project and minimizes the potential risks connected with the project. As described, the

service sessions verify the approach to the project and the data migration, and therefore contribute to

ensuring data consistency after the migration.

The Migration Cockpit simplifies the handling of the migration and makes the process considerably

less complex.

Previous experience with migration projects has shown that the migration service is an importantfactor in the success of the project. You should therefore make sure that you integrate the migration

service when planning your new G/L project.


66/210

SAP AG AC212 4-22

SAP AG 2006


67/210

SAP AG AC212 5-1

SAP AG 2006



Unit 04: New G/L Migration Service and Standard Migration Scenarios








68/210

SAP AG AC212 5-2

SAP AG 2006

The system is prepared for migration at a later stage with

migration package 2.

(see also SAP Note ).


69/210

SAP AG AC212 5-3

SAP AG 2006


70/210

SAP AG AC212 5-4

SAP AG 2006

Can the new G/L be activated in the production system before and during the migration?

Can the new G/L be activated in a test system? Of course, after all, you have to test yournew G/L configurations.

Do you perform a test migration in the same test system too? , sinceyou should use an up-to-date copy of your PROD to do this.

How does the new G/L configuration get to your PROD? Usually by means of

Under no circumstances should the be transported theindicator needs its own transport request!

Does SAP have any information about the

SAP Note Check current Find out whether replacement

is possible.

Check your hardware.

Reconcile your ledgers. Carry our year-end closing with balances carried forward,close posting periods and so on.

TCode for checking whether new general ledger accounting is active:

Important new G/L standard tables:

Totals table:

Line items table:

Table with split information: FAGL_SPLINFO(check tablefor entries too)

The following programs are available for showing/hiding the old/new IMG and SAP Easy Accessmenu paths:

Show/hide new IMG

Show/hide old IMG

Show/hide new menu

Show/hide old menu

As soon as you have activated a migration plan (in your client), you canno longer reverse clearing operations in phase 1 for OIs from phase 0.


71/210

SAP AG AC212 5-5

SAP AG 2006

- In the R/3 system, you have activated the , the ,

(EC-PCA), the , the

and a , as well as CO, for external and internal accounting.- You have acquired very detailed knowledge about the functions of the new general

ledger.- The business concept for the new general ledger has been established and you have opted

for the following core elements

(field name: Place)

Activation date for RTI = migration date (1st of the FY) ispossible. but would not result in the secondary cost elements being transferred!

(see above)

If your company only uses a few of the classic applications mentioned on the slide, this makes themigration to the new G/L easier.

To gain an idea of what should not be changed, and in some cases, what must not be changedretrospectively once the new G/L has been activated (status 02/2007), consult SAP Note

:

Make sure that you consult and other publications on the subject of new G/Lmigration.

With regard to the inclusion of custom fields in the totals table for the new general ledger,


72/210

SAP AG AC212 5-6

SAP AG 2006

Since it is assumed that the field was already used in classic general ledger

accounting, no extension of the account assignment block would have hadto be made.

TCode:

Customizing path:


73/210

SAP AG AC212 5-7

SAP AG 2006

- Assign scenarios

- Define segments- Assign segments to profit

centers- Configure document splitting- Configure RTI- Define any non-leadingledger

As of Q1 2007 it is still not possible to introduce document

splitting after you have already activated the new G/L, forexample!

(e.g. by changing the way the document splittingcharacteristics are controlled)

Example of a procedure that would lead to the production system coming to a standstill: Open itemsfrom phase 1 were migratedthe indicator being set for the

object in document splitting.

This indicator is then set once the migration has actually finished.

When trying to clear the open items in the activated new G/L (=> e.g. payment run), problems arise,

since the open item does not (usually) have the profit center object and therefore cannot pass it on to

the payment document either (by way of the passive split).

If you are not sure whether you may need a characteristic (in the future), you should still

activate the relevant characteristic (by way of the assignment of the scenarios). You can give it thedefault value at first and then give it an actual value when you want to or have to report it.


74/210

SAP AG AC212 5-8

SAP AG 2006

1. Simple against cash

2. Simple against bank interim account (OI account)

3. Simple against bank interim account but now with (manual)account assignment of the bank items with , and .

4. Simple - with vendor - and a $/ exchange rate of 0.5

5. with multiple account assignment

- with vendor 30500- and a $/ exchange rate of 0.5

6. at with a , with:- Valuation method - Without valuation area- Valuation for preparation of financial statements - Vendor OI=> Regarding update of FC valuation to EC-PCA see Notes page!

A always means a document /a posting that has only one account assignment (e.g.a profit center or cost center). The term "singular" account assignment could also be used.

logically implies a document that has more than one accountassignment. In this case, the term "non-singular" account assignment could also be used.

If the valuation amount is to be transferred to EC-PCA, a default PC must be assigned to thevaluation accounts (e.g. ). You can control this in the world of classic G/L accounting usingthe transaction 3KEH, for example.


75/210

SAP AG AC212 5-9

SAP AG 2006

1000

1000

1000

1000

1000

1000

1000

FB60 / Singular vendor invoiceZ4EUR16.500,--201900025.1000

Expl:


76/210

SAP AG AC212 5-10

SAP AG 2006


77/210

SAP AG AC212 6-1

SAP AG 2006











78/210

SAP AG AC212 6-2

SAP AG 2006


79/210

SAP AG AC212 6-3

SAP AG 2006


80/210

SAP AG AC212 6-4

SAP AG 2006

You get .

In a you can see all the most important information about amigration project at once.

With you can quickly recognize the status of a project,and the (processing control) is proposed, and in partstipulated.

By incorporating, providing the option of integrating and creating, as well as comprehensive

, the Migration Cockpit can offer a great deal of supportthroughout the entire migration process.


81/210

SAP AG AC212 6-5

SAP AG 2006

Legend:DMIS =

ata

gration

erver

You with (e.g. SAP_ABA, SAP_APPL, SAP_HR, ): (standard)

The , with the latest support package status in February 2007: SP 0003;

this is to all intents the for information about installation, see SAP Note The that provides the .

DMIS Basis add-on is a component that is ontent-free which means you can import the add-onwithout worrying about any effects this may have on your operative data.

This add-on is also a technical component of other SAP products, such as the Test Data Migration

Server, for example.

If you have already installed TDMS 2005, you have to upgrade the DMIS Basis add-on. In this case,the best thing to do is to contact SAP directly.

Put simply, you can regard an add-on as a kind of luxury transport, since the add-on runs variouschecks when imported that an ordinary transport would not make. These include, for example,

checks that make it safe to import an add-on, in comparison to a transport.

An add-on is normally made available on the SAP Service Marketplace, underwww.service.sap.com.

Amongst other things, the DMIS Basis add-on contains the MBT (Migration Basis Technology),which makes the general structure of the Migration Cockpit possible.

: As already mentioned on the slide, there is an for: SAP Note .


82/210

SAP AG AC212 6-6

SAP AG 2006

Choose

between (see graphic):

The Customizing paths in an (ECC5.0) look almost identical as of with the general ledger activated. However, it was not possible to carry out migration

Customizing without . Without authorized registration as a pilot customer, the

message "migration to the new general ledger is not permitted" appeared immediately.

As of , the system requests a , as is also the case in SAP ERP 2005(see next slide).

The following functions will always be in (ECC5.0), in comparison withSAP ERP 2005 (ECC6.0), status 02/2007:

The (new)function: Documents that are posted in the classic G/L are checked forlogical consistency with the new G/L.

Incorporation of the migration programs in the Closing Cockpit (CloCo).

This is not a drawback, however, as SAP no longer supports the use of the Closing Cockpit inconnection with new G/L migration.

The , which offers a company that already maps parallel accounting with theaccount solution in the SAP system the option of from the

.

You will find more information about the missing features in SAP ERP 2004 in SAP Note 862523.


83/210

SAP AG AC212 6-7

SAP AG 2006

If you execute the ( ):

P.T.O.


84/210

SAP AG AC212 6-8

SAP AG 2006

SAP Note 812919 Status: 27.11.2006

As of February 2007, the license key will still be requested in Customizing, however, you nolonger have to enter it in the corresponding field

SAP will no longer issue a license key sincea migration plan is created from the Migration Cockpit.

Do not link migrationto the technical upgradeto ERP

Migration is a sub-

project within the newG/L project

SAP (the MigrationBack Office) supports

you with the migrationwith a binding,chargeable New G/LMigration Service

As well asSAP Note , you should read SAP Note It provides important information regarding the questions:

What are the for the migration?

What can I do to ?


85/210

SAP AG AC212 6-9

SAP AG 2006

All other immediately reference the Migration Cockpit (stillknown as the New G/L Migration Monitor here) and


86/210

SAP AG AC212 6-10

SAP AG 2006

oersion_igrationasis echnology_ew igration

The transaction calls the so-called:

You can now define various for a project . P.T.O.

:

Transaction CNV_MBT_NGLM is also a good way of testing whether or not the DMIS add-on hasbeen imported into your system. If it is missing, you cannot execute the transaction

CNV_MBT_NGLM.

The transaction is not in the SAP Easy Access menu which is why it makes sense to store it inyour user favorites.

To get detailed information about how to use the Migration Server Overview successfully, the (information) in the transaction CNV_MBT_NGLM.

The project ID must begin with a "Z" see graphic: .

The scenario that cannot be changed is(New G/L Migration) no other scenarios areneeded for new G/L migration.

A project is usually defined for each client.

You do not need to save a project actively (by pushbutton) clicking the pushbutton savesthe project to the database.

Once it has been created, a project cannot be deleted you can only deactivate the packagesappended to it.


87/210

SAP AG AC212 6-11

SAP AG 2006

in the MC, "guests" also require a special that wasdeveloped especially for new G/L migration

You can assign the role to the corresponding users in role maintenance (TCode) or in the usermaster record (TCode ).

The user profile generated by the system is .

A user with the profile can also use the Migration Cockpit, of course.


88/210

SAP AG AC212 6-12

SAP AG 2006

One or more are for a (migration) project from the client 000. The contain the information that byway of the add-on:

The system generates

Packages can only be uploaded if you have imported the Content add-on in client 000 in addition tothe DMIS Basis add-on.

If the migration add-on is not installed or imported, the dialog box shown in the upper screenshotdoes not appear.

The contents for packages 1 3 are available - status Q1/2007. In the future (Q3/2007) packages 1to 5 will be available for .

You do not explicitly need to save the packages here either. As soon as a package ID is displayed inthe Migration Server Overview, this means it has been saved to the database.

Once this has happened, a package .

SAP chose this particular functional solution for documentation reasons.

It is, however, possible to a package. Note, however! This is a : Youactivate a package again after it has been deactivated.


89/210

SAP AG AC212 6-13

SAP AG 2006

- ( ) so-called ( )

- the ( )

- You can very well with the .

Subproject 1 is not required in the new G/L environment!

Subproject 3 is not required in the newG/L environment!

The new general ledger is always introduced or activated at client level.

There can be one or more migration plans for the various company codes within a client.

TipIf you create a migration plan for each company code, it is easier to reset the individualcompany code if an error occurs later.

A different target situation can be aimed at for each migration plan.


90/210

SAP AG AC212 6-14

SAP AG 2006

for calling the Migration Cockpit is the

(=> TCode C)

Legend:

Active packageInactive package

P.T.O.


91/210

SAP AG AC212 6-15

SAP AG 2006

(can be hidden)


92/210

SAP AG AC212 6-16

SAP AG 2006

Initially, only the can call the MigrationCockpit, .

However, thecan also grant other users access and

At first, the registeredusers are

,

Nevertheless,registration does have

an advantage:Guests are notautomatically logged outwhen the activity is executed.

The registration can be reversed at any time, however: Pushbutton

Registering other users for the Migration Cockpit is also a mandatory activity in a migrationproject. This means that this activity must/can also be started from within the process tree:

Phase:

Activity: Register SAP users for migration project


93/210

SAP AG AC212 6-17

SAP AG 2006

Depending on the choice of , are generated in the MigrationCockpit

P.T.O.

It is

to

recognize inthe

.

Since

is alsoused in

,

need to be

executed.


94/210

SAP AG AC212 6-18

SAP AG 2006

(only a few)

e.g. activity Icon:

(Quite a few) e.g. activity Icon:

Including e.g. activity

It is sometimes possible to start several programs by executing an activity, e.g.activity

e.g. activity Icon:

All (three) are as follows:(See slide notes for more details)

is extensively

Sample documentation for the activity : "We [ ] recommend that you check whether there are modifications in your system[ ] that have an impact on the new general ledger or on themigration and decide whether these modifications [ ] are alsorequired for new general ledger accounting

Note that this check is independent of the technical modification clearing (using transaction SPAU)

that you did on connection with the technical upgrade to SAP ERP."

There is another with the activity : it

is one of the (relatively few) activities that does not have to be executed in order to set the status.With these activities, the can also be .

This is practical for activities that are mandatory activities but are not necessarily required in allcompanies.

These activities can be recognized in the toolbar, as the pushbutton is activatedfor them.


95/210

SAP AG AC212 6-19

SAP AG 2006

One of the phases is always the (=> defined in green).

The the to ,

the relevant (=> ) is

The are:

Setup phase

Checkup phase

Preparation phase

Migration phase

Validation phase

Activation phase

The same activity cannot be started twice at the same time (by the same or by another user). The function shown belongs in the area, which is part of the DMIS add-on.

When all the mandatory activities have been performed (see next slide) you can start the firstactivity for the next phase. The active phase changes automatically as a result.

: You can always start optional activities, regardlessof whether they are part of the active phase or another phase.


96/210

SAP AG AC212 6-20

SAP AG 2006

The is only if have been (at least once).

How can you The quickest and

safest way is to use the .

Allactivitiesin

theset-upphase

Mandatoryact

ivitiesintheset-upphase

: Since the use of the

field is optional, these activities are not

mandatory activities and thus not listed in the

.

In subsequent versions of the MC, optional activities will be labelled example:

Like the Migration Cockpit, the Extended Process Monitor provides information about:

The start date of the activity

The start time of the activity

The end date and end time of the activities as well as the runtime

It is also possible to go from here to the logs.


97/210

SAP AG AC212 6-21

SAP AG 2006

too, there are not all, by any means

A migration plan is created during a migration

A migration date is determined for the migration plan

The second activity cannot be executed before the first

In the MC, you can

for each activity whether that activity exists in

on another:Select activity => Toolbar / (=>

pushbutton)

Previous activity is displayed

The illustrated the (=> the activity ID),which does not explain the message of the dialog box intuitively the real meaning appears in the

dialog box on the right:

The activity that comes before the activity "determine migration date", namely "create migrationplan", has not been completed in the set-up phase for the migration package 90002.

You can show the technical name of the activity in the monitor with the Display Activity IDpushbutton (=> in the toolbar: Blue arrow pointing to the right).

The Activity Details pushbutton provides other details in addition to the possible previous activity:

Can the activity be run again?

Do preceding or subsequent relationships exist?

Can you restart programs that have already been executed?


98/210

SAP AG AC212 6-22

SAP AG 2006

Jump to the

How often was an activity executed?=> Possibility of jumping to individual logs

Various runtime information

Job namefor programs(that are startedin the

background)

Activities thatare not mandatoryare not connected to

status management.They can berepeated as often asyou wish.

Activity progress report(at the moment only 0 or 100) for last time activity was executed

stands for . You can also couple attachments of the file types andwith the Migration Cockpit.

Changes to the monitor are kept for (at least) one session for a specific user.


99/210

SAP AG AC212 6-23

SAP AG 2006


100/210

SAP AG AC212 6-24


101/210

SAP AG AC212 7-1

SAP AG 2006











102/210

SAP AG AC212 7-2

SAP AG 2006

(new G/L)


103/210

SAP AG AC212 7-3

SAP AG 2006


104/210

SAP AG AC212 7-4

SAP AG 2006

Test the complete new G/Lconfiguration in a

: Start the (=> seelater) and test migration(s)

in a test system : New G/L

Customizing (=>PROD) /

Migration date Activation date for new G/L

Complete new G/LCustomizing

Start the and testmigrations (with the mostrecent data possible) in a

using the MigrationCockpit, includingactivating the new generalledger

Work through the in theMigration Cockpit in the including

Note these specifications and recommendations in your project.


105/210

SAP AG AC212 7-5

SAP AG 2006

The fact that every activity does not have its own slide is , in the process tree are remember also that a lot of theactivities have been

=> Toolbar:

the

the

the

the and

the

, since this is of course the phase in

which the actual migration of the data takes place!

(and in the next)

However, it is not possible to allocate (at least) one separate slide to each activity.

This statement applies to the following phases of the process tree:

The , for example, requires no additional, explanatory slides the activities to bestarted there

Confirm that the previous fiscal year is closed

Check whether a clearing reset with posting date is (still) allowed in phase 0

Reconcile the general ledger (=> program )

Reconcile various source ledgers: TCode

Confirm that a (classic) opening balance was created

Confirm that a (classic) balance sheet for the current year was created


106/210

SAP AG AC212 7-6

SAP AG 2006

This is an optional activity whether or not you execute it your

If you have a as recommended by SAP, with the typicalcomponents , and ,you

.

With this activity, you confirm that the activities named take placein a different system and are transported to the current system.If you execute the activity a new activity (=> ) is automatically added (with status traffic light ) in the flow

structure.

If, however, you execute the (e.g. for testing or for demopurposes) , .


107/210

SAP AG AC212 7-7

SAP AG 2006

In , you You can only determine the long text the (=>e.g.)

The proposal for the long text for the migration plan comes from the long textfor the loaded package.

P.T.O.

You cannot change the long text for the migration plan / package description again within theMigration Cockpit. If you want to change the text again, you have to do this by means of the

Migration Server Overview: TCode


108/210

SAP AG AC212 7-8

SAP AG 2006

- migration without document splitting- migration with document splitting

The

is

by the system, depending on the chosen migrationscenario. It is an internal parameter that plays no other role.


109/210

SAP AG AC212 7-9

SAP AG 2006

The date from whichthe complete posting data is incorporated inthe new G/L tables.In the , the migrationdate is the start of phase 1.

You should perform the migration

the

The earliest migration date is the start of the fiscal year. All the data that was posted before this date(=> documents from phase 0) are not transferred in precise detail in the SAP standard migration

(only) the balances are carried forward. The exceptions to the rule are accounts managed on an open

items basis for documents that are still open.

If, once you have taken everything into account and finished your preparations, you find yourself inthe last quarter of a fiscal year, it is probably easier and more practical to set the migration date to

01/01 of the following year.

Whatever the case, the migration date must be the first day of a fiscal year. The last day of the fiscalyear variant must correspond to the migration date minus one day.


110/210

SAP AG AC212 7-10

SAP AG 2006

In the activity the system now only outputs a yellow traffic lightin the status bar when the migration date is 01/01. : The warning is

sufficient for you to be able to exit the , providing all the othermandatory activities have been performed!

Be aware, though, that a of , especially when the a considerable part of the year has alreadyelapsed.When you set the migration date to 01.01 of the current FY+1, this is given thestatus "green".

Current FY = Current fiscal year

Current FY+1 = Current fiscal year plus 1 year


111/210

SAP AG AC212 7-11

SAP AG 2006

If you want to, you can create a migration plan for each individual company code.

It is also , and indeed practical, to

- The company codes must have a fiscal year variant withthe same start and end date

If you have company codes for working with document splits and other company codes for workingwithout document splits, at least two migration plans