Você está na página 1de 18

Introduction to

Migration New General


Ledger
SAP AG

Reasons for the Migration

Classic General Ledger Accounting New General Ledger Accounting


in SAP R/3 Enterprise in SAP ERP

Currently: SAP ERP:


Dispersed Over Diff. Areas One Single Environment
Classic GL Ledger CoGS New General Ledger
Legal Ledger Accounting supports
Requirements
Legal requirements
Management and segment reporting
Profit Center Ledger
Management and Extensibility for industries
Segment Reporting Extensibility for customers
Balance sheet for any dimension
Special Purpose Ledger
Multidimensional, Parallel set of books
customer-specific Fast close
Reduction of TCO
Industry-specific ledgers
Balance sheet for grant, fund, International Accounting Standards
title … Compliance & transparency

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

1
Point to Remember:

The migration is always a


project in its own right!

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Introduction to Migration

Initial Situation and Target Scenario

Process and Technical Implementation

2
Migration Is a Project

Migration does not only involve the technical transfer of data; it


can also involve changes to business processes.
Migration is always performed in the form of a project, entailing project phases,
milestones, tests, and so forth

Fundamental prerequisite for the migration:


Successful upgrade of the SAP system to SAP ERP

The migration does not entail:


Implementation of parallel accounting
Implementation of segment reporting
Changeover of the leading valuation if parallel valuation already used
Consideration of scenarios with the company code approach (not supported by
SAP in future, project solution)
Simultaneous changeover of the leading depreciation area
in FI-AA (->SLO)
Change to chart of accounts or conversion of chart of accounts (->SLO)
Currency changeovers (such as introduction of new currencies -> SLO)

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Phase Model for the Migration

Principles of Migration
The migration date is always the first day of a fiscal year (current or future fiscal year)
Year-end closing of the old fiscal year must be complete before New General Ledger
Accounting is activated

Migration Date Activation Date


Old Fiscal Year New Fiscal Year

Classic GL Accounting Classic GL Accounting New GL Acctg


Phase 0 Phase 1 Phase 2

Technical upgrade to ERP Year-end closing for the Creation of document splitting
Creating blueprint for New old fiscal year information for items of old
General Ledger Accounting Making Customizing fiscal year that are open on the
Planning the migration settings in New General migration date
Making Customizing settings in Ledger Accounting Transfer of documents from
New General Ledger Making Customizing phase 1 to new tables:
Accounting settings for the migration FAGLFLEXA / FAGLFLEXT
Analysis of all business Activating document Transfer of balance
processes if document splitting validation (only relevant if carryforward for new fiscal
is to be used document splitting is used) year to FAGLFLEXT
Making Customizing settings
for document splitting

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

3
SAP General Ledger Migration

To achieve a high degree of safety in the migration


projects, SAP decided to accompany each migration
project with the SAP General Ledger Migration service
obligatory service for each migration project
once the service is ordered, the migration programs will be provided for
download
service offered at fixed price

With this service SAP provides scenario-based migration


funcionality combined with service sessions to check data
consistency

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Content of SAP General Ledger Migration service

Scenario-based new General Ledger Migration Cockpit


Step-by-step guidance through the migration via process tree and monitor
Status administration with logs

Remote service sessions


Service session to assure right migration approach
Service session including technical validation and plausibility checks in
migrated test data

Back office support


24h/day technical development support at production weekend
Development support for test migrations during working hours

Complete migration service offered at fixed price

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

4
SAP General Ledger Migration – Process and Overview

New-G/L customer project (assistence of [SAP-]consultants possible)

Subproject migration (assistence of [SAP-]consultants possible)


‚Customer
request

announced techn. BO support


produktiv migration incl.
Contract for additional
consulting possible
Feedback-Session

Feedback-Session
Service session 2
Feedback-Session

migration service

service session 1
Questionaire

Contract for

migration test
by customer
New G/L

Scenario validation test validation

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Introduction to Migration

Initial Situation and Target Scenario

Process and Technical Implementation

5
Analysis of the Initial Situation I

Is classic Profit Center Accounting in use?

Is Cost of Sales Accounting in use?

How is Special Purpose Ledger used?


– Which are used?
– In operational system or in consolidation environment?
– Online update or by rollup?
– Document splitting already used in FI-SL?

Are other SAP ERP systems or SAP business suite


modules implemented? (such as HCM)
How are interfaces to external systems used?
– Adjustments to interfaces necessary?
How is Consolidation used?
– How is the data transferred?

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Analysis of the Initial Situation II

How are G/L accounts on an open item basis managed?


– Relevant if you want to accompany the migration with the introduction of
document splitting. Number of documents to be split?

How many documents are in the migration period (phase 1)?


– These documents must be "migrated" (and may first need to be processed,
enhanced with additional account assignments)

How many company codes and cross-company-code


clearings exist?
Are different fiscal year variants in use?
Are additional currencies in special purpose ledgers in use?
Is parallel valuation in use?
– Special feature: Migration from account approach to ledger approach

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

6
Scenarios Supported by SAP General Ledger Migration
service (1)
Scenario 1: Merge of FI ledger
Merging of classic G/L ledger, consolidation preparation ledger and
cost-of-sales ledger

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


Scenario 1 and additional merging of Profit Center Accounting and
Special Ledger

Scenario 3: Scenario 2 + Document split (e.g. for profit


center, segment or business area reporting)
Document split allows balance sheet on additional dimensions such as
profit center, segments

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Scenarios Supported by SAP General Ledger Migration


service (2)

Scenario 4: Scenario 2 + Change from account approach to


ledger solution for parallel accounting
Switch from parallel accounting by parallel accounts to parallel ledger

Scenario 5: Scenario 3 + Change from account approach to


ledger solution for parallel accounting
See descriptions of scenarios 2,3,4

Any scenarios that differ from the above standard


scenarios are migrated project-by-project based on the
scenario that comes nearest to the customer’s scenario.
The change from an existing parallel accounting solution to a new
parallel accounting solution will be based on scenario 4 or 5 whereas
the introduction of a parallel accounting solution (or keeping the
account approach) will be based on scenario 1, 2 or 3. Additional
consulting might be required.

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

7
What is the target scenario?

The business model and its portrayal in New General Ledger


Accounting must first be defined before the migration.

The possibility to seperate the different steps should be


checked (for example: change from account to ledger
solution, documente split, etc.), to reduce the complexity of
the migration project.

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Introduction to Migration

Initial Situation and Target Scenario

Process and Technical Implementation

8
Migration Without Document Splitting –
Building Balances in New General Ledger Accounting
Initial situation Target scenario
Balances from classic General Balances in New General
Ledger Accounting (GLT0) / Ledger Accounting
PCA / FI-SL… FAGLFLEXT
Balance sheet accounts /
1. accts not managed on OI basis/
no reconciliation accounts
CoCode 1000 CoCode 1000
Balance Carryforward
CF 150 CF 150
Per 1 100
Per 2 200

2. Documents from phase 1


Subsequent build of
Per 1 CoCode 1000 100
Per 2 CoCode 1000 200 FAGLFLEXA and FAGLFLEXT

Retained
3. earnings accounts
CoCode 1000 CoCode 1000
Balance carryforward
CF 500 CF 500

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Migration Without Document Splitting – Transfer of Open Items

New General Ledger Accounting/


Open items < migration date Build FAGLFLEXT
Receivables /
and FAGLFLEXA for
payables
new fiscal year

1. Transfer of cumulated FAGLFLEXT


balance carryforward Reconciliation account
CoCode 1000 CoCode 2000
OI CoCode 1000
CF 100 CF 200
OI CoCode 2000 Additional build of
FAGLFLEXA and FAGLFLEXT 100 Per 1
for old fiscal years 200 Per 2

2. Documents from phase 1


Subsequent build of
Per 1 CoCode 1000 100
FAGLFLEXA and FAGLFLEXT
Per 2 CoCode 2000 200

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

9
Migration With Document Splitting –
Building Balances in New General Ledger Accounting
Initial situation Target scenario
Balances from classic General Balances in New General
Ledger Accounting (GLT0) / Ledger Accounting
PCA / FI-SL… FAGLFLEXT
Balance sheet accounts /
accts not managed on OI basis/
1. no reconciliation accounts CoCode 1000
CoCode 1000/Seg 1 Segment 1 Segment 2
Balance carryforward
CF 150 CF 150
Per 1 100 Per 1 200

2. Documents from phase 1


Transfer posting for
Subsequent build of balance carryfwrd
Per 1 Segment 1 100
FAGLFLEXA and FAGLFLEXT using TA FBCB,
Per 1 Segment 2 200
where necessary

Retained
3.
earnings accounts
CoCode 1000/Seg1 CoCode 1000/Seg1
Balance carryforward
CF 500 CF 500

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Migration with Document Splitting –


Enrichment of "Old" Open Items with Account Assignments

Select items that were open on the migration date, that is


Items that are currently still open, or
Items with a clearing date falling after the migration date

Customers
Vendors
G/L Accounts

Create Work Enrich Update Splitting info


BAdI
list table

Build
FAGLFLEXA
Balance
FAGLFLEXT
carryforward

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

10
Migration With Document Splitting – Transfer of Open Items

New General Ledger Accounting/


Open items < migration date Build FAGLFLEXT
Receivables /
and FAGLFLEXA for
payables
new fiscal year

Transfer of cumulated FAGLFLEXT


1. For each dimension by
balance carryforward Reconciliation account
reading the splitting Segment 1 Segment 2
OP 100 Segment 1 information
CF 100 CF 200
OP 200 Segment 2
FAGLFLEXA built 100 Per 1
additionally for old fiscal 200 Per 2
years

2. Documents from phase 1


Subsequent build of
Per 1 100 Segment 1
FAGLFLEXA and FAGLFLEXT
Per 2 200 Segment 2
including processing of document splitting

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Technical Procedure for Performing the Migration

Determination of the migration objects ("old" OIs and documents from phase 1)

Transfer of balance carryforward (accounts not managed on an open item basis)

If applicable, reposting of balance carryforward values (accounts not managed on


an open item basis)

Preparation of documents from phase 0 (enhancing open items with document


splitting information)

Transfer of "old" open items (customer/vendor accounts, G/L accounts) and


simultaneous build of balance carryforward for relevant reconciliation accounts

Preparation for documents from phase 1 (supplementary account assignment,


such as Segment or Profit Center)

Transfer of documents from phase 1 into tables of New General Ledger


Accounting

Reconciliation of the data

Activation of New General Ledger Accounting

Completion of the migration

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

11
Overview of a Possible Migration Process

Start of the migration project


Analysis of the initial situation and definition of the target business scenario
Upgrade to SAP ERP
Customizing New General Ledger Accounting for the target scenario
Testing the target scenario in an appropriate test environment

Customizing of migration
(Iterative) migration test-run in the test system:
Creation and analysis of a migration log
Adjustments to Customizing new run etc…
Then transport of migration settings to production system
Alongside the migration test-run: closing the old fiscal year
Migration in the production system (performed once) after final closing of the
previous fiscal year
Activation of New General Ledger Accounting
End of the migration project

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Additional Activities –
Documents to Be Posted Subsequently with Document Splitting

Analysis of document splitting information


G/L account assignment
Check document types
Check assignment of business transactions

Alternative Customizing
Document splitting method for migration
Document-specific business transaction assignment
Document-specific item category assignment
Alternative clearing relationship
Edit account assignment information
Specify document splitting relationship

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

12
Document Validation –
Only When Document Splitting Is Used

Phase 1 in production system

Check on the current posting data against rules


for document splitting
- Log
- Online warning message + log
- Error message

Adjustments possible for special processes


- Business transaction / transaction / batch input

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Evaluation of Migration

Evaluation of the migration status


- Statistics, error overview, object lists

Log of balance origin

Ledger comparison

Display of document splitting information


(Ledger-independent)

Log of migration-specific adjustments to


document splitting

Simulation of document splitting

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

13
Completion of Migration

activity in Migration Cockpit


"Complete Migration Plan"
After the migrated data has been successfully
reconciled and checked

Effects
The migration programs for this migration plan can
no longer be executed.
The manual reposting of balance carryforward
(FBCB) can no longer be performed.

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Special Features in the Migration I

Migration to multiple ledgers


Open items are not migrated for specific ledgers, that is to say, the
balance carryforward from open items is always updated for all ledgers
In the case of non-calendar fiscal years (for one company code),
multiple migration plans have to be used (bundling of company codes
for which the same fiscal year is defined)
- Execution of the migration plan with the earliest migration date first
Depending on the tables currently used (GLT0, GLFUNCT, GLPCT), they
can in future be combined in a single ledger
- Not mandatory to have multiple ledgers
Migration with introduction of the segment
Supplementary account assignment of FI documents (phase 1)
– Scenarios in the standard delivery
A) Profit Center Accounting already used Derive segment from profit
center
B) Profit center not yet used Set derivation of profit center either from CO
account assignment or by program
– Activate segment derivation

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

14
Special Features in the Migration II

Migration when Profit Center Accounting is active


SAP recommends depicting Profit Center Accounting within New General Ledger
Accounting
If classic Profit Center Accounting is used, see SAP Note 826357

Migration with customer fields


Estimation of the expected number of totals records if a customer field is
included in FAGLFLEXT (see also SAP Note 1045430)
Customer field does not necessarily have to be coupled with customer totals
tables (see also SAP Note 820495)
Enrichment of open items and documents (phase 1) for customer field
Build balance carryforward and period balances using customer field
If financial reporting uses this field, a zero balance must exist for each entry in
each document
What is not migrated?
Statistical noted items in general, down payment requests, payment requests
Reference documents (recurring entry original documents, sample documents)
Parked documents

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Special Features in the Migration III

Reposting of balance carryforward (transaction FBCB)


Repostings only possible in phase 1 (that is, before the activation date for New
General Ledger Accounting)
The transfer of balance carryforward needs to have been completed
No postings to OI-managed accounts or reconciliation accounts (correct target
balances are built cumulatively from the enriched open items)
Amounts must be specified explicitly in all currencies (no automatic translation
into local currency)
Update of FAGLFLEXT and GLT0 Ledger comparison produces a match!
If FBCB documents exist, it is not possible to reset the migration (RESTORE_
ALL)

Migration and archiving


Open items always remain in the system
Documents from phase 1 must not be archived
Totals records (also from previous years if applicable) must be available
– Totals records may also be transferred from previous years by means of rollup

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

15
Integration Aspects

Asset Accounting (FI-AA)


Depreciation area 01 must be assigned to the leading ledger
Where necessary, conversion of depreciation areas in FI-AA using SLO (not part
of migration to New General Ledger Accounting)
Previous year must be closed in Asset Accounting
Depreciation area conception (delta areas) and corresponding assignment to
ledgers in General Ledger Accounting

Treasury and Risk Management (CFM)


Valuation area 001 must be assigned to the leading ledger
Valuation area conception and corresponding assignment to ledgers in New
General Ledger Accounting
– Control via accounting principle

Real-time integration with Controlling


Definition of the time of the conversion from the reconciliation ledger approach to
real-time integration
– Independently of the time of the migration, that is to say, the conversion can also occur
beforehand

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

Restrictions Affecting SAP ERP 2004

SAP Note 862523


The scenario for the transition from parallel accounts to parallel ledgers
is not supported in SAP ERP 2004.
The functions for validating document splitting are not available in SAP
ERP 2004.

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

16
Training courses about New G/L and Migration to New G/L

New general ledger and migration to new general ledger is


covered in greater depth in the following SAP training
courses:
AC210: New General Ledger Accounting in SAP ERP (4 days)
AC212: Migration to New General Ledger Accounting (3 Tage)

Both training courses are strongly recomended as


prerequisit for the implementaion and migration

Please refer to the SAP Education Service to find out when


these courses are being held in your region. You also find
this information at www.service.sap.com/trainingcatalog

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

So, please remember:

The migration is always a


project in its own right!

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

17
Copyright 2007 SAP AG. All 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
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, 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, System i, System i5, System p,
System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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 are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product specifications may vary.

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

SAP AG 2006, Introduction to Migration / Solution Management of Financials / ‹#›

18

Você também pode gostar