LSWM

LSMW

Objective: • Overview of LSMW • Core Functions of LSMW • Main advantage of LSMW • Example for transaction MM01

LSMW
What is LSMW ? The Legacy system migration workbench ( LSMW ) is an R/3based tool that supports single or periodic data transfer from your non-SAP system to R/3. It is a component of the R/3 System and, therefore, is independent from the platform. The data is loaded via the standard interfaces of the applications.This will include all checks that are run for online transactions. Invalid data will be rejected. R/3 release 3.0F , 3.1x : version 1.0 of LSMW R/3 release 4.0x , 4.5x , 4.6x : version 1.6 and 1.7 of LSMW

direct input ) . batch input .LSMW Core Functions of LSMW • Importing legacy data from PC spreadsheet tables or sequential files. • Importing the data using standard interfaces of R\3 ( IDOC inbound processing . • Converting data from its original ( legacy system ) format to the target (R\3) format.

LSMW Which data can be migrated using LSMW ? • By means of standard transfer programs: a wide range of master data (e.g G/L accounts .g financial documents . vendor master . customer master . sales order ) • By means of recording of transactions: further data objects (if the transaction can be run in batch input mode) . material master) and transaction data (e.

LSMW Accelerating Data Migration: LSM Workbench How LSM Workbench works Read data Legacy data on appl icati on server One or several files Legacy dat a on PC Read data Structure relations Field mapping Conversion rules Converted data Convert data R/3 Standard Batch Input processing Direct Input processing IDoc inbound processing © SAP AG July 1999 21 .

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

LSMW Batch input Direct input BAPIs (Business Application Programming Interfaces) IDocs (Intermediate Documents) • Generation of the conversion program on the basis of defined rules • Clear interactive process guide • Interface for data in spreadsheet format • Creation of data migration objects on the basis of recorded transactions • Charge-free for SAP customers and SAP partners .

Process Flow: . it is recommended to perform some conceptual tasks.LSMW Prior to using LSMW.

LSMW The following should be taken into account: • Make sure that the R/3 Customizing has been completed. . • Analyze the data that exists in your legacy system (LS) and which of it (from a business point of view) will be required in the future as well.

• Process the respective transaction in R/3 manually using test data of the legacy system and note which fields must be filled.LSMW • Identify the transaction(s) in the R/3 System that you want to use to transfer the data to this system. Maybe there are required fields that do not correspond to a data field in the legacy system. assigning a fixed value or constant or setting up a field as an optional field perhaps is useful for the data transfer. . In this case.

LSMW • Carry out mapping on paper. . You can do this by using the object overview after you defined the object. • Determine the conversion rule according to which the field contents of the source fields are to be converted into R/3 fields. that is. allocate the source fields and R/3 fields to each other.

LSMW • Define the way in which the data is to be extracted from the non-SAP system. .) • Which format does the legacy data have? Decide which standard import technique you want to use. or if you should define an extra "object class” by means of recording. (Note: The LSMW does not extract any data itself.

LSMW • In case only a part of your legacy system is to be replaced with the R/3 System. . you have to determine the functions that are to be covered by the R/3 System and those to be covered by the legacy system. If necessary.a concept of the data flows and interface architecture has to be created.

even before the procedure for Migration of  Legacy System Data Using LSMW is described.LSMW Objects of LSMW Some objects that are of special significance for data migration with the LSMW are explained at the beginning of the documentation. • Project • Sub project • Object • Structure relationships • Field assignments .

the project serves as an organizational unit used to combine mapping and field assignments. . Use In the LSMW.Project Definition All the data of an application system that is to be transferred to the SAP R/3 System.

Project Structure The project consists of: • Sub project • Business object (object) • Structure relationships • Field assignments Integration A project can have any number of sub projects assigned to it. .

. Integration A sub project can have any number of objects. Example Data migration in a company with several plants in which data is organized in different ways. the complete migration of data would be the project.Sub Project Definition An organizational unit subordinated to the project. In this case. The sub projects would comprise the data in the individual plants.

which is used to transfer the data of a project to the SAP R/3 System.Object Definition An object is a unit combined from the business point of view. Structure An object consists of the following elements: • Tables involved in the project and in the SAP R/3 System • Structure(s) for transfer of data • Relationship between data at the table and field level • Field assignments for conversion of data .

material master. or financial documents are objects. .Object Integration An object is assigned to a sub project. customer master. For example.

Structure Relationships Definition Structure relationships are mappings between structured trees. the structures of the data to be migrated (referred to as "source structures" ) have to be created within the hierarchy in a way that they can be allocated to the structures in the R/3 System (referred to as "target structures" ). Use The mappings between the trees have to make sense. . This means.

Use The field assignments use placeholders and conversion rules in order to ensure both flexibility and consistency of data. . you assign values to the placeholders and select the processing types for the conversion rules. In migration customizing.Field Assignments Definition A collection of rules that define how the field contents are to be converted during data migration from the legacy system to the SAP R/3 System.

. there are the data elements. or by means of fixed values. there is the domain. which is defined by the field type. and value tables. • At the second level.Field Assignments Structure The field assignments are distinguished by the different levels of reference: • At the highest level. field length. which are defined by the domain as well as by language-dependent texts.

The placeholders and conversion rules defined by the field assignments are either linked to the target field directly or through the domain. there are the fields.Field Assignments • At the lowest level. which are defined by field names and data elements. The field-related rules refer to them. .

.Getting started.Example Example for Batch Upload : Material master data transfer using LSMW for transaction mm01.

.Transaction LSMW Enter the Name for the project. subproject and object and press create button.

maintain the field properties. Then go to LSMW. Once you are through with the recording. This needs to be done for all the fields for which you made an entry during recording. by double clicking on the 3rd column of any field. (ctrl + F2) in this case its going to be mm01. you have to record the transaction. press ctrl + f8 for the corresponding project Double click .Example .LSMW As soon as you have create the project.

. by pressing ctrl + F3 for all the fields that you made an entry during recording. create the field. Go back and by default No.3 Radio option must have been selected.2 Radio option and Press F8 and in the next screen you have to mention the source structure by clicking create button and then save it.Example .3 Radio option “Maintain source field”.LSMW When you are done with maintaining the Object attributes( you have to mention the name of the recording in Batch Input Recording ). Select No. if not select No. In the source field screen. now the next step is to maintain source attributes.

specify the file name and then save it. “Maintain Field Mapping and conversion rules” and press ctrl F8. execute it and enter the value for no. execute it.9 “Read Data”.of transaction(say 1-999999). Then Select No:10 “Display read data” to check whether value from . Go back and select No: 7 Radio option “Specify files” . . Go back and select No:8 radio option “Assign files” and press CTRL F8 .LSMW Go back and select No. then go to No.5.Example . press CTRL F8 .txt file is properly assigned to the corresponding fields in the structure. Click Assign Source Field for each field in a structure and map it to the Project structure. then create entry for Legacy Data.

LSMW Follow the previous procedure for Step 10-12. .Example . Create the Batch Input Session and Run the Batch input session.

Summary • The Legacy System Migration Workbench (LSMW) is a tool that supports data migration from non-SAP systems to the SAP R/3 System. • The LSMW supports a one-time transfer of data (initial data load) and also offers a restricted support of permanent interfaces. The LSMW. a periodic transfer of data is possible. does not include any functions for monitoring of permanent interfaces. however. It is a component of the R/3 System. . Thus. The tool does not support any data export interfaces (outbound interfaces).