LSMW

Accelerating Data Migration: LSM Workbench
Legacy System Migration

Workbench
lsm@sap.com
 SAP AG January 2002 1

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

 Move data from legacy system to an SAP System
 Switch off legacy system
 Periodic data transfer (Interfacing)

 Exchange data between an SAP System and other systems
 Position of data migration

 Requires customized SAP System (customizing must be
finalized)

 Relevance of data migration?

 Accounts for 15% - 20% of the total SAP 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

Data migration in 3 steps
start 1. step 2. step 3. step target
data
data fieldmapping
preparatory data import on
in and
steps SAP
legacy rules data
system
base
checklist 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.

Requirements
for the use of
LSMW
 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 3.0 (Nov. 2002): R/3 release 6.10
 For LSMW 1.7 (Sept. 2000): R/3 release 4.0x, 4.5x or 4.6x
 For LSMW 1.0 (Sept. 1998): R/3 release 3.0F or 3.1x

How does
LSMW
work?

Data Migration
Datenmigration

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 ...

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 ...

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 ...
...
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 ...
...
 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

 Central conversion rules (reusable rules)

 Assure consistent data conversion in different data objects
Material master
Sales order
Material number
Purchase requisition
Purchase order

Further steps
 read source data
D
A  data conversion
T
A
 run import
M
I
G
R
A
T
I
O
N

One or several
How LSM Workbench works files
Legacy data
on PC
Read data Read data
Structure Legacy data
relations on application
server
Field mapping Convert data
SAP Standard
Batch Input
Conversion processing
rules
Converted Direct Input
data processing
IDoc inbound
processing

 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”
H Customer #1 (header rec.)
Identifying P Contact person #1
string P Contact person #2
(H=header ... ...
P=position)

 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

What does
LSMW
look like?

Define project,
subproject
and object

Select
migration step
Maintain
attributes

Enter
structures of
legacy system
in the SAP
System

Define
conversion
rules and
field
mapping

Generated
conversion
program

Interface for
data on PC

Overview of
migration
object

Overview of
migration
object

Migration
customizing:
translation table

recording

Transport of Mapping and Conversion Rules
Purpose
Mapping and conversion rules that have
been used in an SAP system should be used in
another SAP system.
Procedure
Use the export and import function of LSMW
Or: create a change request to use the standard transport
system of SAP
LSM- LSM-
Version
3.0
Version
3.0
Condition
Both SAP systems have the same LSMW-version

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

 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 system) on record level and on field
level
 define rules
 transfer of field contents


 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 SAP application


 transport the data migration object
 via download and upload
 via SAP transport system
 What LSMW cannot do

 extract data from the legacy system
 “outbound”: transfer data from SAP into another system

 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

 Advantages and strengths at a glance:

 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

 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...”

 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
Support
Training
 SAP AG January 2002 42 LSMW

 Information
 Main information medium: SAPNet
 www.service.sap.com.de/LSMW
 Download of
 software (LSMW30.CAR) and further material
 installation guide
 quick guide (“HowToGuide”)
 contact
 e-mail: lsm@sap.com
 Support
 Online-Service-System: component XX-LSM

 Training
 upon request
 part of the data migration training BC420 in release 4.6
 self-study via examples in SAPNET

Beyon
d
LSMW

 DX-Workbench
 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.)

Legacy System Migration

Workbench
lsm@sap.com

LSMW

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LSMW

Hochgeladen von

Copyright:

Verfügbare Formate

Accelerating Data Migration: LSM Workbench

Legacy System Migration

 SAP AG January 2002 1

 What is data migration? / Subject of LSM

 Initial data transfer from non-SAP systems to an SAP System

 Periodic data transfer (Interfacing)

 Position of data migration

 SAP AG January 2002 3

 Relevance of data migration?

 Why is data migration so expensive?

 SAP AG January 2002 4

Data migration in 3 steps

start 1. step 2. step 3. step target

 SAP AG January 2002 5

What is LSMW (Legacy System Migration Workbench) ?

 LSMW is a tool based on R/3.

 SAP AG January 2002 6

for the use of

 SAP AG January 2002 8

 SAP AG January 2002 9

 SAP AG January 2002 10

Define source structures

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

 SAP AG January 2002 11

Define source fields

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

 SAP AG January 2002 12

Vendor master Define structure relationships

B1 B2 B3 ... Bank data

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

Vendor master Fieldmapping and conversion rules

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

 Most common conversion rules predefined

 SAP AG January 2002 15

 Central conversion rules (reusable rules)

 SAP AG January 2002 16

 SAP AG January 2002 17

Field mapping Convert data

 SAP AG January 2002 18

 What kind of data can be read?

 SAP AG January 2002 19

 Which data can be migrated via LSMW?

 SAP AG January 2002 20

 SAP AG January 2002 21

 SAP AG January 2002 22

 SAP AG January 2002 24

 SAP AG January 2002 25

 SAP AG January 2002 26

 SAP AG January 2002 27

 SAP AG January 2002 28

 SAP AG January 2002 29

 SAP AG January 2002 30

 SAP AG January 2002 31

 SAP AG January 2002 32

Transport of Mapping and Conversion Rules

 SAP AG January 2002 33

Periodic Transfer of Data

Read data (only files on the

 SAP AG January 2002 34

 What LSMW can do

 SAP AG January 2002 35

 What LSMW can do

 SAP AG January 2002 36