Presentation on

Data Migration of
Non-SAP Systems to R/3

1
 Introduction

• This introduction is intended to allow a quick entry into

the work with the Legacy System Migration Workbench
Version 1.6 ("LSM Workbench").

2
LSM Workbench: What is it?
• The LSM Workbench is an R/3-based tool that supports you
when transferring data from non-SAP systems ("Legacy
Systems") to R/3 once or periodically.
• The tool supports conversion of data of the old system in a
convenient way. The data can then be imported into the R/3
system via batch input, direct input, BAPIs or IDocs.

3
Schematic Flow of Data Migration with
the LSM Workbench

4
The main advantages of the
LSM Workbench:

• Part of R/3 and thus independent of individual platforms

• A variety of technical possibilities of data conversion
•Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case
depends on the business object.

5
Main functions

The LSM Workbench is a tool that supports data transfer

from non-SAP systems to R/3. The main functions of the
LSM Workbench are:

• Import data (legacy data in spreadsheet tables and/or

sequential files)
• Convert data (from source format to target format)
• Import data (into the database of the R/3 application)

6
Initial Transaction
• To start working with the LSM Workbench, use transaction LSMW

7
Project, Subproject and Object

• Project : An ID with a maximum of 10 characters to

name your data transfer project. If you want to transfer data
from several legacy systems, you may create a project e.g.
for every legacy system.
• Subproject : An ID with a maximum of 10 characters that is
used as further structuring attribute.
• Object : An ID with a maximum of 10 characters to
name the business object.

8
Example for a Project Structure

9
LSM Workbench: The Main Steps of
Data Migration

10
Maintain Object Attributes

• In this step, object type and import technique are

selected.

11
12
Maintain Source Structures

In this step you define the structures of the object with name,
description and the hierarchical relationships

13
14
Maintain Source Fields

In this section, fields are created and maintained for the

structures defined in the preceding step.

15
16
Create Individual Source Fields
Make sure that you are in change mode and the cursor
is positioned on a source structure or an existing source field.
Clicking on Create field displays the following popup:

17
Maintain Structural Relationships

The structural relationships define the relationships between

source and target structures.
The possible target structures are defined during the
selection of the object type and the import technique.

18
19
Maintain Field Mapping and
Conversion Rules
In this step, you assign source fields to target fields
and define how the field contents will be converted.
All fields of all target structures, which you selected in
the previous step, will be displayed. For each target
field the following information is displayed:
Field description
Assigned source fields (if any)
Rule type (fixed value, translation etc.)
Coding.

20
21
Specify Files

In this step you describe all files to be used in the

following steps:
Your old data on the PC and/or R/3 server
The file for read data
The file for the converted data

22
23
24
 Assign Files

In this step, you assign defined files to the source

structures:

25
 Read Data

Proceeding:
If you want to process all data belonging to an object,
click on Execute. The process is started.
If you want to migrate a part of the data only, you can limit
the number of data to be migrated in field "General
selection parameters". Make your selection in field
"Transaction number" from "... to ...". Multiple selection is
possible

26
27
 Display Read Data

In this step, you can display all or a part of the

read data in table form. Clicking on a line displays
all information for this line in a clear way. The
same happens when you click on Field contents.

28
 Display Read Data

In this step, you can display all or a part of the

read data in table form. Clicking on a line displays
all information for this line in a clear way. The
same happens when you click on Field contents.

29
Convert Data

If you do not make any data selection, confirm the

process by clicking on Execute. Otherwise, make your
selection in field "Transaction number" from "...to...".
Here, multiple selection of transaction numbers is
possible as well.

30
Display Converted Data

In this step, you can display all or a part of the

converted data in table form. Clicking on a
line displays all information for this line in a
clear way. The same happens when you click
on Field contents.

31
Import Data with Batch Input

Generate Batch Input Session

In this step, the standard batch input program belonging to
the object is directly called. The name of the file with the converted data
is already proposed.
The batch input sessions to be generated are named after
the LSMW object

Run Batch Input Session

The program goes to R/3 standard transaction SM35. However, only

the batch input sessions for the selected object are displayed.

32
Import Data with Direct Input

Start Direct Input Session

Depending on the object type, either the

standard direct input program belonging to
the object is called or you can select a direct
input program or a direct input transaction.

33
 Recordings

If neither a standard batch input program nor a standard

direct input program is available for a data object, you can
create a new object using the recording function of the LSM
Workbench.

However, also in cases where a standard program is

available, it may make sense to use the recording function in
order to reduce the number of target fields.

34
Perform a transaction „trial run“: Caution: This is no
simulation mode! Your input is posted in the system!
Postprocess recording: Assign field names, field texts and
default values
Save recording: This generates the above structure in the
Data Repository.

35
36
Enter Recording name, Description & owner

Enter Transaction code

Now you can execute the selected transaction. Here you should input
values in all the fields you intend to fill with the values from you old data
later.

37
After the recording has finished, you can process it. You can delete or add fields

38
After you saved, the status line displays the following
message: "Data saved successfully". The recording is now
available among the attributes for the object.

39
40
41
Questions

42
Thank you

43