KX Session

Data Migration
2005-06-02
Data migration

AGENDA

1. What is Data migration?

2. Purpose of Data migration

3. Relevant data for Data migration

4. Example Messer

5. Data migration - ADM Phases

6. Data migration tools

7. Summary

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 2
What is Data Migration?

Data migration is…

…checking and reworking of existing ‚Production data‘ via…

• …transfer legacy data prior to Go Live to the new IT system

• …transfer data from SAP system(s)/NON SAP systems to other SAP system(s)

• …migrate data during upgrades in SAP systems that are already up and running

• …modificate conversion rules to meet customer needs (Business and technical viewpoints)

• …design and implement migration tests in close cooperation with the customer's
departments

• …delete old/inconsistent data (Data cleansing)

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 3
Data Migration – What for..?

The purpose of Data migration…

• Keeping the right Business data after a system change

• Reducing Data maintenance effort

• Providing leaner processes

• Reducing Data errors

• Increasing Data consistency

• …

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 4
Relevant Migration data

Data relevant for migration

• Master data for the TO BE processes

Master data – Customer master
Material Master
Customer Material Info Record
Vendor master
…

• Transactional data for the TO BE processes

Transactional data – Contracts
Orders
Price records
Bank data
…

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 5
KX Session Data Migration –
Harmonization and cleansing of doubles

Example: MESSER environment

• Data is stored in different source systems

Source systems Target system

IT: 439029088

CH: 37994847591234320 Product 1032455

FR: 10029001

Example:
Same product with
different codes

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 6
KX Session Data Migration –
Master data approach at Messer

Challenge…
• Data fields are used differently
• Relevant master data objects can be used in specific areas or for specific processes,
others can be used by every process

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 7
KX Session Data Migration –
Master data approach at Messer

Best practice

• Data migration is dedicated to one team / person

• Data migration = cross team task

• Migration concept with objects and timeline communicated to all team

members

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 8
 KX Session Data Migration –
Phases and overview

Analyze Design Build Test Deploy

RICEF • Design Data Data Conversion Data Conversion

-Reports Conversion and Migration to
-Interfaces • Data Identification
-Conversions Production
-Extensions Data Definition
-Forms
Data Mapping Data Validation
Data cleansing

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 9
 KX Session Data Migration –
Analyze phase

Analyze Design Build Test Deploy

Identify and Locate

• Identification of the required data in the new system
• Identification of the source/target system(s) for this data
• Initial estimates of the volumes - be specific e.g. 10.000 customers
• Type of data conversion

Migration object Migration Source system Target system Type of data

YES/NO conversion

A Material Master YES SAP R/2 SAP R/3 Automated

B Material evaluation NO - - -
C Material stock NO - - -
D Purchase requisitions YES SAP R/2 SAP R/3 Automated
… … … …

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 10
 KX Session Data Migration –
Data volumina example

Analyze Design Build Test Deploy

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 11
 KX Session Data Migration -
Analyze and design phase

Analyze Design Build Test Deploy

Analyze and Design phase

• Define source structure : structure of data in the source file.
• Define target structure : structure of SAP that receives data
• Field mapping: Mapping between the source and target structure with
conversions, if any
• Specify file: location of the source file
Migration object Migration Source system Target system Type of data
YES/NO conversion

A Material Master YES SAP R/2 SAP R/3 Automated

A1 Material number 8999 40008582
A1.1 Base unit of measure L15 KG
A1.2 Material type Bulk Bulk
A.1.3 Material text Thermo Oil Thermo Oil
… … … … …

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 12
 KX Session Data Migration –
Build & Test & Deploy overview

Analyze Design Build Test Deploy

Build
• Transform the data as required - This includes creating non-existent data from scratch, and also altering
the legacy data to make it fit into SAP.
• Data cleansing (for example: get the customer phone number field to contain customer phone numbers,
get the stock counts right)
• Build and unit test the data conversion routines

Test
• Build up your tests so that by the end of Realisation you are in effect testing the entire data conversion
routine

Deploy
• If all the testing has been successfully completed, you have a minor miracle on your hands and you can
face the go-live with confidence

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 13
 KX Session Data Migration –
Build and test phase example

Analyze Design Build Test Deploy

Build and test phase

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 14
 KX Session Data Migration –
Deploy phase

Analyze Design Build Test Deploy

Deploy phase (loading into Production system)

• Data Migration automated

from a Legacy System: LSMW
via Flat File: LSMW / CATT
from SAP to SAP system: ALE / EDI

• Data Migration manual

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 15
 KX Session Data Migration –
LSMW

Analyze Design Build Test Deploy

LSMW = Legacy System Migration Workbench

• Basic Principles:
Business objects instead of individual tables or field contents are migrated
Conversion rules can be customized to meet the customer requirements

• SAP Transaction code ‚LSMW‘

• Data consistency due to standard import techniques

Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)

• Creation of data migration objects on the basis of recorded transactions

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 16
 KX Session Data Migration –
LSMW

Analyze Design Build Test Deploy

• Import Data - Transaction code ‘LSMW’

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 17
 KX Session Data Migration –
ALE

Analyze Design Build Test Deploy

ALE (Application link enabling)

• The ALE supports the development of applications across different SAP systems

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 18
 KX Session Data Migration –
ALE

Analyze Design Build Test Deploy

Sending system Receiving system

Application IDoc Application

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 19
 KX Session Data Migration –
ALE

Analyze Design Build Test Deploy

ALE – example Material distribution – Transaction BD10

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 23
 KX Session Data Migration –
Data Transportation

Analyze Design Build Test Deploy

Transport routes

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 25
 KX Session Data Migration –
Data Transportation

Analyze Design Build Test Deploy

Transport-Management System – Transaction STMS

Provides framework for transporting
Importing data

Transport organizer – Transaction SE01

Creation / releasing / documentation change requests

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 26
 KX Session Data Migration –
CATT

Analyze Design Build Test Deploy

CATT = Computer Aided Test Tool

• The CATT records your keystrokes while performing the actual transaction

• Identification of the fields that need to be changed in that view

• Export the data to a spreadsheet to populate with the data required

• Data is uploaded and executed (no additional manual input necessary)

• Transaction ‚SCAT‘ (transaction runs without user interaction)

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 29
 KX Session Data Migration –
CATT

Analyze Design Build Test Deploy

CATT - example
• Enabling CATT = SCC4

• Run CATT script = SCAT

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 30
KX Session Data Migration

Function CATT / LSMW ALE/EDI Manual input

Batch Input
Mass Data Load
Material/Customer/
Vendor master /
Condition records
Small amounts of
data
Programs

Automatic update of
master data
Large databases
across several SAP
Systems
Transactional data

Non-SAP to SAP

SAP to SAP

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 31
KX Session Data Migration

Function CATT / LSMW ALE/EDI Manual input

Batch Input
Mass Data Load ++ ++ ++ -
Material/Customer/
Vendor master /
Condition records…
Small amounts of - - ++ +
data
Programs - - ++ n/a

Automatic update of + + + n/a

master data
Large databases - - ++ n/a
across several SAP
Systems
Transactional data ++ ++ ++ +

Non-SAP to SAP - ++ - -

SAP to SAP ++ ++ ++ +

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 32
KX Session Data Migration –
Summary

Significance of Data Migration

• Data migration comes in the end of the SAP implementation. At this time,
the SAP system is normally installed and application customizing is
finished (in the best case).

• An examination of SAP implementation projects has shown that data

migration is about 20% of the total implementation expenses. This
portion may rise up to 40% in smaller implementation projects.

• A significant reduction of the expenses for data migration results in a

corresponding significant reduction of the total project budget and the
project runtime.

Strictly confidental – for project-internal use only

SAP Harmonization project – Version 1.0 – Page No. 33