Common Template Accounting
Migration Strategy
What is Migration?
Premises - Migration
migration of DATA - not HW, not processes (HW may be necessary to
transport data to D’dorf, i.e. using tapes, CD, DVD, because of WAN
bandwidth)
reach requirements for data migration from:
legal point of view 2
central and local business point of view
project point of view (roll-out plan, cost, …)
use right tools for right data
define standards for mapping and conversions
integrate data archiving in migration process
Migration – Dimensions
Scope Time Frame
3
Migration
Resources
Responsibility Tools
Organization
Migration – Scope
Minimize the volume of the data (from data type point of view)
Objectives Setup the right methods
Minimize volume Aggregate / summarize / harmonize migrated data
Migrate only active data (e.g. AP/AR master records) – Cleaning before Mig.
Methods for Mapping 4
Organizational Units Mapping between old system and new created values in CTA
and Master Data Doesn’t have to be 1:1 (e.g. CC = CC&PC, CC&BA = CC&PC)
Takeover
Copy data from old system without some big changes.
Harmonization
Unification of data with other companies
Is followed by mapping
New
Mainly for data didn’t used in old system
Migration – Scope
Minimize the volume of the data
Objectives Setup the right methods
Methods for Balances
Transaction Data Mainly used for GL accounts values without OI management. Posting
with contra technical account.
Items
5
Mainly used for GL accounts with OI and AP/AR sub-ledgers. Posting
with contra technical account.
Documents
Not recommended method because of different posting logic, structures
(problematic mapping). Posting with original logic/accounts.
Run on CTA
Special cases (e.g. payment runs, depreciation runs, ...)
New
Mainly for data didn’t used in old system
Migration – Scope – Data Types – Examples
FI, CO, AM, PS MM, IM, PS, PM, RE, SD
Company Code, Company, Business Area, Chart
of Accounts, Chart of Depreciation, GL / AP / AR Plant, Purchasing Organization, Purchasing Group,
Organizational Group, Asset Class, Document Type, Depreciation Warehouse, Business Unit, Sales Organization,
Area, Controlling Areas, Cost Element Category, Distribution Channel, Sales Group, Purchasing
Units
Cost Center / Group, Profit Center / Group, WBS Document Type, ...
Element, ...
GL Account, Vendor, Customer, Payment Term /
Method, Dunning Area / Procedure, Order Type, Product Category, Material Type,
Correspondence Type, Cash Journal, CJ Business Material Group, Industry Sector, Investment
Transaction, General Bank Data, House Bank, Program, Vendors / Customers Logistic Segment, 6
Master Data IBAN, Depreciation Key, AM Transaction Type, Project Type, Profile, Investment Program Type,
Asset, Asset sub-number, Asset super-number, Business Partner, RE Usage Type, RE Contract
Evaluation Group, Cost Element, Internal Order, Type, RE Contract Condition, RE Flow Type, RE
Consolidation Transaction Type, Partner Number, Service Charge Settlement Type, RE Area Type, ...
Functional Area, Tax Code, ...
GL Balance, GL Open Item, AP Open Item, AP
Balance, AR, Open Item, AR Balance, Bank Order, Order Request, Sales Order, Material,
Values Statement, Cash Journal Document, Asset Value, Contract, ...
CO Document, SL Document, ...
Others ... ...
Migration – Scope – Overview – Modules
Old Systems CTA
Old Systems
One system / One client
map
copy
Organizational Units new
map
copy
Master Data new
IM, PS, MM, RE, PM, SD IM, PS, MM, RE, PM, SD
balances
items, docs
Values run, new
new
IM, PS, MM
map
copy
Organizational Units new
map
copy
Master Data new
FI, CO balances
items, docs
FI, CO
Values run, new
Migration – Time Frame
Minimize the volume of the data and history (from time point of view)
Objectives Harmonize as much as possible Migration with Legal and Audit needs
Harmonize Migration with CTA rollout plan and also with parallel projects
Minimize volume How Old Data
(depend on business and legal requirements)
We will migrate maximum 1 fiscal year history (before take-over) of GL
accounts balances on summary level by: year, months, company codes,
8
profit centers, cost centers, functional areas, ...
The Open items (GL, AP, AR, AM) open on take-over day will be
migrated.
Fixed Assets values will be migrated also with values on end of previous
fiscal year. Values from beginning of FY until the take-over date will be
migrated individually (balances, items, re-run, ...)
Actual CO data will be mainly migrated via FI migration. Plan data will be
migration according to reporting and business needs analyzed during
rollout.
Migration – Time Frame
Minimize the volume of the data and history (from time point of view)
Objectives Harmonize as much as possible Migration with Legal and Audit needs
Harmonize Migration with CTA rollout plan and also with parallel projects
Harmonize migration Takeover Point
with Legal and Audit options: start of FY, half of FY, any start of month, any date
needs from time (depend on legal and business requirements)
point of view We recommend to plan Take-over date in beginning of the Fiscal Year.
9
In case of Take-over date beginning of quarters it has influence to
migration methods and volume but is still feasible. In this case we also
have to migrate data from beginning of actual Fiscal Year.
Must be coordinated with Roll-out Strategy.
Harmonize migration Rollout Plan
with CTA rollout and Selection of Take over point must be coordinated with Rollout plan and
parallel projects with Other projects running parallel with CTA project.
Migration – Resources, Responsibility, Organization
Have available resources
Have transparent responsibility
Objectives Have clear organization
Transparency
Resources Migration is task for certain implementation team supported by DSO/MGI and
Responsibility by local resources in the company/country where implementation is realized.
Organization Implementation team is responsible for Migration
DSO/MGI are responsible to organize resources for each implementation
10
depending volume, difficulty, ...
C&D defining rules for migration related to Data objects – Implementation
teams must follow rules or ask for change request
In case of migration with scenario 2B (other than FI/CO modules) support by
company or sales division resources is more heavy
Transparency follow and document rules and methods of migration
testing of migration
involve audit (internal and external) to approval of migration
Migration – Realization
One system / One client
to do: to do:
CTA Overview / Coordination
CTA Realization Sales Division / Companies Realization
CTA SD
IM
IM PS 11
FI MM
PS
CO RE
MM
PM
SD
Data Structure
rules for objects & migration rules
business scope CTA optional 2B
Migration – Tools
Proper and appropriate tools
Objectives Minimize time and cost of migration
Proper and SAP standard migration programs – if available and suitable for an object
appropriate tools LSMW – if available and suitable for an object (mainly for transactions)
ABAP – for all the rest
SLO – will not be used for “rollout” migration – but possibly in future in case 12
of CTA internal migration (change of structures, numbers, ...)
Minimize time and predefine methods of migration for all migrated objects (in Object list)
cost of migration prepare template ABAP programs for migration (will be modified for each
implemented company according local needs)
prepare conversion/mapping tables for objects
prepare conversion tools out of SAP – Excel, dB, ...
Migration – Tools – Data Archiving in Migration Process
I. Business requirements There is not plan to migrate Archive Files from
source environments target CT environment source environment
It is expected to keep source environment for
FI/CO Archive FI/CO Archive
2001 some time after production available for reporting
2002
time
2004
2003 (freeze of the source system)
2005
2006 2006 2006 take over point
2007 2007 2007 (e.g. 1.1.2007)
2008 2008
2009 2009
2010 2010
III. CT system after going live
source environments target CT environment 13
FI/CO Archive FI/CO Archive
2001
2002
time
II. Legal requirements 2004 ? 2003
2004
DART
2005 2005
2006 2006 2006 2006 take over point
source environments target CT environment 2007 2007 2007 (e.g. 1.1.2007)
2008 2008
2009 2009
FI/CO Archive 2010 2010
?
2001
2002
time
2003
DART DART
2004 2004
2005 2005
2006 2006 take over point
2007 (e.g. 1.1.2007)
original data without conversion
conversion
original data after conversion
move of old archive
new data after going-live
archiving
Migration Scope – Summary / Directions
Proposal for discussion
Scope include all objects “in scope” of FI/CO and harmonization of non FI/CO objects by scenario 2B.
Scope Dimension
Detail descriptions for migrated objects are part of Data Structure Object/IMG List.
Methods selection will be part of Migration Concept. We will mainly used ABAP and LSMW for
Methods/Tools
migration. The SLO services will not be used during rollout migration but possibly in future for example
Selection for “migration” of vendors together with Common Template Purchasing project.
We will migrate maximum 1 fiscal year history (before take-over) of GL accounts balances on summary
level by: year, months, company codes, profit centers, cost centers, functional areas, ...
The Open items (GL, AP, AR, AM) open on take-over day will be migrated.
14
Fixed Assets values will be migrated also with actual values on the take-over date.
Actual CO data will be mainly migrated via FI migration. Plan data will be migration according to
reporting and business needs analysed during rollout.
It is recommended to plan Take-over date in beginning of the Fiscal Year.
Time Dimensions
In case of Take-over date beginning of quarters it has influence to migration methods and volume but is
still feasible. In this case we also have to migrate data from beginning of actual Fiscal Year.
Must be co-ordinated with Roll-out Strategy.
1 year historical data are expected to be enough for business needs.
The older data needed for legal requirement will be in first phase after take-over kept in original
systems. Later we will use DART tool to move data from original systems to CTA system for limited
reporting requirements (must be more analysed).
[CLIENT LOGO]
16
