LSMW – Step by Step

LSMW – Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.

Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]

Advantages of LSMW:
• Most of the functions are within R/3, hence platform independence.

• Quality and data consistency due to standard import techniques.

• Data mapping and conversion rules are reusable across projects.

• A variety of technical possibilities of data conversion.

• Generation of the conversion program on the basis of defined rules

• Interface for data in spreadsheet format.

• Creation of data migration objects on the basis of recorded transactions.

• Charge-free for SAP customers and partners.

Working With LSMW:
Use TCODE LSMW

Objects of LSMW:
•Project   – ID with max of 10 char to Name the data transfer project.

• Subproject   – Used as further structuring attribute.

• Object   – ID with max of 10 Characters, to name the Business object .

• Project can have multiple sub projects and subprojects can have multiple objects.
• Project documentation displays any documentation maintained for individual pop ups and processing steps

User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.

Object type and import techniques:
• Standard Batch / Direct input.

• Batch Input Recording

o If no standard programs available

o To reduce number of target fields.

o Only for fixed screen sequence.

• BAPI

• IDOC

o Settings and preparations needed for each project

Preparations for IDOC inbound processing:
• Choose settings -> IDOC inbound processing in LSMW

• Set up File port for file transfer, create port using WE21.

• Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.

• Setup partner type (SAP recommended ‘US’) using WE44.

• Maintain partner number using WE20.

• Activate IDOC inbound processing.

• Verify workflow customizing.

Steps in creating LSMW Project:
• Maintain attributes – choose the import method.

• Maintain source structure/s with or without hierarchical relations. (Header, Detail)

• Maintain source fields for the source structures. Possible field types – C,N,X, date, amount and packed filed with decimal places.

• Fields can be maintained individually or in table form or copy from other sources using upload from a text file

• Maintain relationship between source and target structures.

• Maintain Field mapping and conversion rules

• For each Target field the following information is displayed:

o Field description

o Assigned source fields (if any)

o Rule type (fixed value, translation etc.)

o Coding.

o Some fields are preset by the system & are marked with Default setting.

• Maintain Fixed values, translations, user defined routines – Here reusable rules can be processed like assigning fixed values, translation definition etc.

• Specify Files

o Legacy data location on PC / application server

o File for read data ( extension .lsm.read)

o File for converted data (extension .lsm.conv)

• Assign Files – to defined source structures

• Read data – Can process all the data or part of data by specifying from / to transaction numbers.

• Display read data – To verify the input data being read

• Convert Data – Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.

• Display converted data – To verify the converted data

Import Data – Based on the object type selected
• Standard Batch input or Recording

o Generate Batch input session

o Run Batch input session

• Standard Direct input session

o Direct input program or direct input transaction is called

BAPI / IDOC Technique:
• IDOC creation

o Information packages from the converted data are stored on R/3 Database.

o system assigns a number to every IDOC.

o The file of converted data is deleted.

• IDOC processing

o IDOCS created are posted to the corresponding application program.

o Application program checks data and posts in the application database.

Finally Transport LSMW Projects:
• R/3 Transport system

o Extras ->Create change request

o Change request can be exported/imported using CTS

• Export Project

o Select / Deselect part / entire project & export to another R/3 system

• Import Project

o Exported mapping / rules can be imported through PC file

o Existing Project data gets overwritten

o Prevent overwriting by using

‘Import under different name
’

• Presetting for Inbound IDOC processing not transportable.