ERP Implementation
BCO5651 Session 9
SAP Data Migration
Dr. George Vossos
Updated: 1 February 2021
Lecture Goals
Introduction to SAP Data Migration
Introduction to Data Conversion / ETL
Introduction to SAP LSMW
Group Workshop (simulated role-play)
Updated: 1 February 2021
Data Migration 101
◆
◆
◆
Data migration is required when
◆
◆
as is the case when business mergers or acquisitions happen and the company ends up with two systems for the same
function.
Data Migration is the process of transferring data between one application system to another,
database type to another, or storage type.
Relevance of data migration?
◆
◆
◆
new systems are implemented, existing systems are upgraded or integrated with one another
Accounts for 15% - 20% of the total SAP implementation costs
Smaller implementation projects: up to 40%
Why is data migration so expensive?
◆
◆
◆
◆
you need to develop conversion programs (which can not be used later on)
you need to deal with lots of technical details and different technologies
data volume depends on the project volume
the effort for programming does not depend on the data volume
Peoplesoft to SAP Training Data – Case Study
◆
•
•
•
•
•
City of Tacoma
City used PeopleSoft application
before SAP
PeopleSoft has 8 years of training
records (Approx – 1 million records)
◆
1.
2.
SAP Training & Event module has
been partially implemented
PeopleSoft training records were not
migrated to SAP during the
implementation
3.
Which Tool
An inside-out approach: The data
import tool lives inside SAP and is
used to bring outside data into SAP
as LSMW, BDC and etc.
An outside-in approach: The tools
living outside SAP are used to bring
outside data into SAP.
TX Shuttle chosen
Training coordinators have to log-in
to SAP as well as PeopleSoft to
provide training history records
4
Peoplesoft to SAP Training Data – Case Study
◆
•
•
•
•
•
Challenges
Data Structure: PeopleSoft data
structure is different from SAP viz. data
element and data type
Data Translation: Courses in
PeopleSoft have been mapped as
Business Event Type in SAP
◆
1.
2.
3.
Data Consolidation: Data clean-up, i.e.
removal of duplicate courses
Data Overlap: Some courses exist both
in PeopleSoft and SAP application.
PeopleSoft classes migrated as SAP
training classes
Historical Data: Unique PeopleSoft
classes have been migrated to SAP
under “PeopleSoft Business Event
group”
4.
5.
Learnings
Data migration should be completed
before go-live of any module of SAP
Data standardization should be in
place before data migration
Identification of the data migration
tool at early stage of the data
conversion process reduces the
preparation work
Data load should be during the offpeak hours
Eight years of PeopleSoft training
records uploaded into SAP in less
than 2 weeks – without relying on
programming staff.
5
System Consolidation – Creates Data Migration
Market challenges
Strategic implications
• Continuous pressure to
maximize efficiency of
operations
• Expanding corporate networks
• Requirement to realize
increasing globality of
corporate activities
• Need to effectively adapt
business structures and
processes to new market
requirements
• Major strategic reorganization
measures
(e.g. M&A, centralization)
• Frequent business process
changes
Impact on technology
Global Operations - Creates Data Migration
Global Inter-company Networks
Headquarter
Customer
Supplier
OEM
EDI
EDI
EDI
EDI
EDI
EDI
Distributor
EDI
Basic
Materials
Subcontractors
Mergers, Acquisitions and Reorganizations
Corporate Networks
Subsidiary 1
Headquarter
Subsidiary 2
Everyone
operates its own
systems
Subsidiary 6
Subsidiary 3
Subsidiary 4
Subsidiary 5
Changing Bus Environment – Create Data Migration
Impact on IT landscapes and systems
• Challenge to integrate multitude of systems
and leverage synergies
-> Fast and sound integration required
• High alteration rate of requirements at IT
structures and processes
-> Alignment of IT systems to new business
processes necessary
• Decentralized, heterogeneous and regionally
disperse systems
-> Inefficient number of IT systems in operation
Need to
simplify and
streamline IT
architectures
and
processes
Why System Consolidation?
◆
◆
◆
◆
◆
Cost reduction
◆ Maintenance and upgrade costs
◆ Hardware costs
◆ Support costs (headcount)
M & A activity
Globalized reporting requirements
◆ Cross regional cost and revenue reporting
Infrastructure enhancements
Enabling other software coversions
Techniques for system consolidation
◆
Options for consolidating SAP R/3 systems include
◆
◆
Greenfield Startup – Build new system from scratch
Configuration Build – New system with existing configuration transferred by transports
◆
Master Data Build – New system with transported configuration and master data build
by LSMW or BDC
◆
Limited Transactional Data Build – Master Build with limited transactional data by BDC,
LSMW or custom ABAP
◆
Complete Historical Build – Complete merge of multiple systems and all transacational
data
Comparison of Consolidation Options
200
0
GF
◆
10
CB
25
MDB
65
LTB
Amount of data to be transferred / Complexity of consolidation
CHB
Greenfield Startup / Configuration Build / Master Data Build
◆



Advantages
Not constrained by historical
data and business process
Easily implemented
◆


Generally no tools or external
consulting required

Disadvantages
Must retain old systems for long
periods of time
Costly dual hardware and
possibly upgrades of historical
data systems
No comparative reporting from
prior years
13
Limited Transactional Data Build
◆


Advantages
Overcomes some of the historical
data requirements not present in
Greenfield / Master Data /
Configuration builds
Still requires significantly less
resources than complete system
consolidation
◆




Disadvantages
Still must retain and maintain the
old systems
More costly to implement than
Greenfield / Configuration / Master
Data builds
Requires more resources
Lack of repeatable tools to
support such a consolidation
14
Complete Historical Data Build
◆



Advantages
No need to retain or maintain old
systems or hardware
All historical data is available in
the consolidated systems
◆


Disadvantages
Project timeline is typically longer
than other approaches
Cannot be performed by in-house
resources
Supported by SAP after
consolidation
15
System - Client Merge
System A
STEP 3
Client
001
Data migration
System B
Client
001
STEP 1
System B
STEP 2
Client 001
System C
Client
002
System X
Client 001
Client 002
Standard function
Conversion function
Client copy or MWB toolset
Client merge
Conversion Services
◆
◆
Conversion Service consists of both
◆
◆
Service Delivery:Executing conversion by specialists
Benefits of Conversion Services
◆
◆
◆
◆
Conversion Package:Predefined rule sets, programs and tables for technical
database conversion
◆
Alternative to individual, time consuming solutions
Flexible
Reduces costs
Saves time
Conversion using Conversion Services ...
◆
◆
◆
◆
Change the data directly in the database
Affects all of the client‘s dataset
Is executed without duplication of existing data
(old data records no longer available)
Is executed without reference to business transactions
(No logical check during conversion, no change documents)
Data Conversion: 3 Easy Steps
Data migration in 3 steps
start
data
in
legacy
system
1. step
preparatory
steps
checklist
2. step
3. step
fieldmapping
and
rules
LSMW
data import
target
data
on
SAP
data
base
Fieldmapping and conversion rules
Vendor master
L
1
L2
L3 L4
D
A
T
E
A
N
M
M
I
I
G
G
R
R
A
A
T
T
I
I
O
O
N
N
L5
L6
B1
B2
L7
B3
Fieldmapping and conversion rules
...
Bank
data
...
A1
A2
A3
B2
B3
...
A4
Contact person
...
Fixed value/
constant
A1
A2
A3 A4
A5
A6
A7
...
B1
...
C1
C2
C3
C4
...
◆
Rules
Most common conversion rules predefined
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
Initial value
Constant
Assign (“MOVE”)
Fixed value
D  DE
A  AT
F  FR
1:1 translation
Translation via intervals
User-defined routines
Prefix
Suffix
Concatenate
Individual ABAP coding
001...100  10
101...200  20
201...300  30
LSMW
◆
◆
◆
◆
What is LSMW (Legacy System Migration Workbench) ?
LSMW is a tool based on R/3.
LSMW supports periodic and single data transfer from a non-SAP system to an
SAP System.
LSMW uses standard SAP interfaces.
LSMW – Some Details
◆
Organisational
◆
◆
◆
◆
◆
◆
Customizing of the SAP applications must be finished
Know how in LSMW (1-2 days)
Knowledge of the source data (Which fields means what?)
Knowledge of the SAP application (Which fields means what?)
Technical know how
◆
◆
R/3 basis (batch input processing, IDoc processing)
ABAP
System requirements
◆
◆
◆
◆
◆
For LSMW 4.0 R/3 release WAS 6.20
For LSMW 3.0 (???): R/3 release WAS 6.10
For LSMW 1.8.0 (Sept. 2000):R/3 release 4.6x
For LSMW 1.7.2 (Sept. 2000):R/3 release 4.0x, 4.5x
For LSMW 1.0 (Sept. 1998):
R/3 release 3.0F or 3.1x
LSMW
How LSM Workbench works
Structure
relations
Field
mapping
Read data
Legacy data
on PC
Legacy data
on application
server
Convert data
Batch Input
processing
Converted
data
Direct Input
processing
IDoc inbound
processing
SAP Standard
Conversion
rules
Read data
One or several
files
LSMW
◆
What kind of data can be read?
◆
◆
◆
◆
◆
◆
Data from spreadsheet-based applications
◆
MS Excel, MS Access, etc.
Data from host systems on SAP application servers
Fixed record length, end of record indicator or hexadecimal length field at the
beginning
With and without separator
Code page conversion
“Hierarchical” data with “identifying field values”
Identifying
string
(H=header
P=position)
H
P
P
...
Customer #1 (header rec.)
Contact person #1
Contact person #2
...
LSMW
◆
◆
Which data can be migrated via LSMW?
==> all data where an interface exists
◆
◆
Standard Batch Input, Standard Direct Input
◆
◆
◆
entries in tables SXDA* (DX-Workbench)
Batch Input Recording
◆
◆
◆
precondition: application program
Recording a transaction
Flat target structure (no header-position constellations with variable amount of
positions)
Methods for Business Objects („BAPIs“)
◆
All BAPIs for which an ALE-IDoc interface has been generated
(by SAP development)
IDocs
◆
All
LSMW Steps
Define project,
subproject and
object
LSMW Steps
Select
migration step
LSMW Steps
Maintain
attributes
LSMW Steps
Enter
structures of
legacy system
in the SAP
System
LSMW Steps
Define
conversion
rules and
field
mapping
LSMW Steps
Generated
conversion
program
LSMW Steps
Interface for
data on PC
LSMW Steps
Overview of
migration
object
LSMW Steps
Migration
customizing:
translation table
LSMW Summary
◆
◆
◆
◆
What LSMW can do
organize the data migration project
◆
project, subproject, object
document data migration project
define data conversion per object
◆
select target
◆
◆
◆
◆
◆
business object (p.e. customer
master, material master)
method(p.e. create, change)
import technique
input, IDoc)
(p.e. batch-
◆
◆
◆
◆
define relations
◆
define rules
◆
structure of the source data
(segments, fields, file attributes etc)
transfer of field contents
read data (technical conversion)
convert data (conversion of values)
import data
◆
with a standard import technique
◆
◆
define source
◆
between source and target (SAP
system) on record level and on field
level
◆
◆
batch-input,direct input
method for a business-object (“BAPI”)
IDoc technique
this means:
◆
LSMW does not write data into the
databases of the applications
◆
precondition for the use of LSMW is the
availability of a data transfer interface
in the SAP application
35
LSMW Advantages
◆
Advantages and strengths at a glance:
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
Part of SAP and therefore platform-independent
Wide range of data conversion techniques (fixed values, translation, ABAP coding, etc.)
Migration customizing: no literals in rules
Conversion program generated from conversion rules
User guidance: data migration in 14~20 steps
Interface for data in spreadsheet format
Check against SAP Customizing before processing the import
Free of charge for SAP’s customers and partners
Migrated data in SAP is consistent
user friendly
only basis ABAP knowledge necessary
in most cases only few programming has to be done
supports data transfer for the most important master and transaction data
SAP HANA Security - Documentation: SAP HANA
Roles Explained
•
References
•
https://www.youtube.com/watch?v=ah7AspicX8o
•
Assessment 3c PFCG Tute