Legacy System Migration Workbench

Accelerating Data Migration: LSM
Workbench
ACE
Legacy System Migration

Workbench
Workbench
ACE
What is
LSMW?
Workbench
ACE
 What is data migration? / Subject of LSM
 Data transfer
 source: non-SAP systems (“legacy systems”)
 target: SAP R/3
 Initial data transfer from non-SAP systems to SAP R/3

 Move data from legacy system to SAP R/3
 Switch off legacy system
 Periodic data transfer (Interfacing)

 Exchange data between R/3 and other systems
 Position of data migration

 Requires customized R/3 System (customizing must be finalized)
Workbench
ACE
 Relevance of data migration?

 Accounts for 15% - 20% of the total SAP R/3 implementation costs
 Smaller implementation projects: up to 40%
 Why is data migration so expensive?

 In many cases
 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
Workbench
ACE
Data migration in 3 steps
start 1. step 2. step 3. step target
data
data fieldmapping
preparatory data import on R/3
in and
steps data
legacy rules base
system
checklist LSMW
Workbench
ACE
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 R/3.
 LSMW uses standard R/3 interfaces.
Workbench
ACE
Requirements
for the use of
LSMW
Workbench
ACE
 Organizational
 Customizing of the R/3 applications must be finished
 Know how in LSMW (1-2 days)
 Knowledge of the source data (Which fields means what?)
 Knowledge of the R/3 application (Which fields means what?)
 technical know how
 R/3 basis (batch input processing, IDoc processing)
 ABAP
 System requirements
 for LSMW 1.6 (July 1999): R/3 release 4.0x, 4.5x or 4.6x
 for LSMW 1.0 (Sept. 1998): R/3 release 3.0F or 3.1x
Workbench
ACE
How does
LSMW
work?
Workbench
ACE
Data Migration
Datenmigration
Workbench
ACE
Define source structures
D Vendor master
A
T
A
M Bank data
I
G
R Contact person
A
T
I
O
N
A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...

Workbench
ACE
Define source fields
Vendor master
D L1 L2 L3 L4 L5 L6 L7 ...
A
T
E
A
M B1 B2 B3 ... Bank data
M
I
I
G
G Contact person
R A1 A2 A3 A4 ...
R
A
A
T
T
I
I
O
O
N
N
A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...

Workbench
ACE
Vendor master Define structure relationships
L1 L2 L3 L4 L5 L6 L7 ...
B1 B2 B3 ... Bank data

D
A
T Contact person
A1 A2 A3 A4 ...
A
M
I
G
R
A
T
I
O
N
A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...
...
Workbench
ACE
Vendor master Fieldmapping and conversion rules
L1 L2 L3 L4 L5 L6 L7 ...
D
A B1 B2 B3 ... Bank data
T
E
A
N Contact person
M A1 A2 A3 A4 ...
M
I
I
G
G
R
1:1 translati
R
A
Move
A
T
In
T
d
I
ivi
I
d
O
ua
O
on
lc
N
od
i ng
Fixed value/
constant
A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...
...
Workbench
ACE
 Most common conversion rules predefined
 Initial value D  DE
A  AT
 Constant F  FR
 Assign (“MOVE”)
 Fixed value
 1:1 translation
 Translation via intervals
 User-defined routines 001...100  10
101...200  20
 Prefix 201...300  30
 Suffix
 Concatenate
 Individual ABAP coding
Workbench
ACE
 Central conversion rules (reusable rules)
 Assure consistent data conversion in different data objects
Material master
Sales order
Material number
Purchase requisition
Purchase order
Workbench
ACE
Further steps
 read source data
D
A  data conversion
T
A
 run import
M
I
G
R
A
T
I
O
N
Workbench
ACE
One or several
How LSM Workbench works files
Legacy data
on PC
Read data Read data
Legacy data
Structure on application
relations server
Convert data
Field mapping
R/3 Standard
Batch Input
Conversion rules processing
Converted Direct Input

data processing
IDoc inbound
processing
Workbench
ACE
 What kind of data can be read?
 Data from spreadsheet-based applications
 MS Excel, MS Access, etc.
 Data from host systems on R/3 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”
H Customer #1 (header rec.)
Identifying P Contact person #1
string P Contact person #2
(H=header ... ...
P=position)
Workbench
ACE
 Which data can be migrated via LSMW?
 ==> all data where an interface exists
 Standard Batch Input, Standard Direct Input
 precondition: application program
 entries in tables SXDA* (DX-Workbench)
 Batch Input Recording
 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
Workbench
ACE
What does
LSMW
look like?
Workbench
ACE
Define project,
subproject
and object
Workbench
ACE
Select
migration step
Workbench
ACE
Maintain
attributes
Workbench
ACE
Enter
structures of
legacy system
in R/3
Workbench
ACE
Define
conversion
rules and
field
mapping
Workbench
ACE
Generated
conversion
program
Workbench
ACE
Interface for
data on PC
Workbench
ACE
Overview of
migration
object
Workbench
ACE
Overview of
migration
object
Workbench
ACE
Migration
customizing:
translation table
Workbench
ACE
recording
Workbench
ACE
Transport of Mapping and Conversion Rules
Purpose
Mapping and conversion rules that have
been used in a R/3 system should be used in
another R/3 system.
Procedure
Use the export and import function of LSMW
Or: create a change request to use the standard transport
system of R/3
LSM- LSM-
Version Version Condition
1.6
1.6
Both R/3 systems have the same LSMW-version
(to transport rules from version 1.0 to 1.6 you must either convert the rules to 1.6 format
before the export or import to version 1.0 and then do the upgrade of the rules)
Workbench
ACE
Periodic Transfer of Data
(/SAPDMC/SAP_LSMW_INTERFACE)
LSMW:
additional to be
program scheduled Job
Read data (only files on the

application server can be used)
Data conversion
Data import
Workbench
ACE
 What LSMW can do
 organize the data migration project
 project, subproject, object
 document the 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 (p.e. batch-input, IDoc)
 define source
 structure of the source data (segments, fields, file attributes etc)
 define relations
 between source and target (SAP R/3) on record level and on field level
 define rules
 transfer of field contents
Workbench
ACE
 read data (technical conversion)
 convert data (conversion of values)
 import data
 with a standard import technique
 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 R/3 application
Workbench
ACE
 transport the data migration object
 via download and upload
 via R/3 transport system
 What LSMW cannot do

 extract data from the legacy system
 “outbound”: transfer data from SAP R/3 into another system
Workbench
ACE
 Advantages and strengths at a glance:
 Part of R/3 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 R/3 Customizing before processing the import
 Free of charge for SAP’s customers and partners
Workbench
ACE
 Advantages and strengths at a glance:
 Migrated data in R/3 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
Workbench
ACE
 Examples of positive feedback:
 “... Just wanted to let you know us here at ... We are very
pleased with the LSM product. We are using it for most of our
conversions and have found it to be of tremendous help and
quality. ...”
 “The LSM Workbench saved the day. Without it, we would

never have been finished on time.”
 “...in our opinion, the major benefit is LSM’s flexibility, which

allows us to respond very quickly to changing requirements...”
Workbench
ACE
 Examples of positive feedback:
 “...within two and a half hours, we managed to generate our

own migration object for the material master transfer, and
successfully migrate the material masters from the EXCEL
sheet. It was a complete success! ...”
 “...the transfer of master data on June 12, and of the open items
on June 19, 1998, meant that we could go live the same day.”
 “...I used the LSMW to transfer customers and creditors, and I

was really impressed by how fast and flexible it was!
Fantastic! ...”
Information Workbench
ACE
Support
Training
LSMW
Workbench
ACE
 Information
 Main information medium: SAPNet
 www.service.sap.com.de/LSMW
 Download of
 software (LSMW16.CAR) and further material
 installation guide
 quick guide (“HowToGuide”)
 contact
 e-mail: lsm@sap.com
 Support
 Online-Service-System: component XX-LSM
Workbench
ACE
 Training
 upon request
 part of the data migration training BC420 in release 4.6
 self-study via examples in SAPNET
Workbench
ACE
Beyon
d
LSMW
Workbench
ACE
 New DX-Workbench (Release 4.6)
 Organize your data migration projects
 Generate test data
 Use LSMW (or third-party tool) as mapping engine
 Fast data load via BAPIs
 Handle import errors (restart etc.)

Workbench
ACE
 Release 4.6
 New-DX Workbench and LSMW
 Release 5.0
 Unified solution for all

data migration issues
Workbench
ACE
Legacy System Migration

Workbench
lsm@sap.com

Legacy System Migration Workbench

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Legacy System Migration Workbench

Uploaded by

Copyright:

Available Formats

Accelerating Data Migration: LSM

Legacy System Migration

 Initial data transfer from non-SAP systems to SAP R/3

 Periodic data transfer (Interfacing)

 Position of data migration

 Relevance of data migration?

 Why is data migration so expensive?

Data migration in 3 steps

start 1. step 2. step 3. step target

 LSMW is a tool based on R/3.

for the use of

A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...

A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...

B1 B2 B3 ... Bank data

A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...

A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ...

Converted Direct Input

Transport of Mapping and Conversion Rules

Read data (only files on the

 What LSMW cannot do

 “The LSM Workbench saved the day. Without it, we would

 “...in our opinion, the major benefit is LSM’s flexibility, which

 “...within two and a half hours, we managed to generate our

 “...I used the LSMW to transfer customers and creditors, and I

 Organize your data migration projects

 Generate test data

 Use LSMW (or third-party tool) as mapping engine

 Fast data load via BAPIs

 Handle import errors (restart etc.)

 New-DX Workbench and LSMW

 Unified solution for all

Legacy System Migration

You might also like