13 Steps to simple LSMW using Record Method
The LSMW 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 legacy system in a convenient way. The data
can then be imported into the R/3 system via Batch input, direct input, BAPIs or IDocs.
LSM Workbench provides a recording function that allows to generate a
"Data migration object" in an entry or change transaction, Through LSMW, we can
upload Master Data and Transaction Data.
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.
• Generation of the conversion program on the basis of defined rules
• Clear interactive process guide
• Interface for data in spread sheet format
• Creation of data migration objects on the basis of recorded transactions
• Charge-free for SAP customers and SAP partners
Here you have to first Define Project, Sub Project, and Object. It is mainly for grouping
objects. One can have multiple subprojects and Objects in a Project.
Execute the transaction and you will get navigated to the second screen: LSMW Work
Bench. Here one can choose the required steps by pressing the ‘User Menu’ button.
Do you want to Master SAP MM? Then enrol in "SAP MM Training" This course will
help you to master SAP MM
The following 13 steps are sufficient for the Support person for the LSMW update.
Step 1: Maintain Object Attributes
Define the method of upload. i.e. batch recording, direct update, BAPI, etc. Go inside
this step and choose the radio button for the options. This document explains only the
transaction recording method.
One can toggle between the Display or change option using the standard button. Select
the object type and Import method as ‘Batch Input Recording’. Once you have selected
this click on the overview button so that you can go to the recoding overview
Example of a recording
After recording default those fields that you want to update /use in the batch update.
Step 2: Maintain Source Structures
Give any name, which can be easily identifying the input data structure. (It is equivalent
to defining an internal table in an ABAP program). Can define multiple structures also (if
required).
Step 3: Maintain Source Fields
Define all those fields that you are giving in the input file here. The order should match
the order of fields in the file. Otherwise, it will get updated into the wrong fields. (Most of
the errors might be in this step)
Step 4: Maintain Structure Relations
Define the source and destination structure relationships.
SAP MM Tutorial
Step 5: Maintain Field Mapping and Conversion Rules.
You have to define the mapping rules.., eg. Customer = customer. Or if any default value
has to be passed, or some fixed value is given like that ( company code can be a default
value if processing for a particular company code.
After making all the mappings and initialization you can even do a syntax check to see
your mappings are correct or not
Step 6: Specify Files
You have to specify the input file location in this step.
Step 7: Assign Files
Assign the physical file path to the structure
Step 8: Read Data
Reading the file to the source structure
Step 9: Display Read Data
This is a very useful step where we can review the field values that got read.
Step 10: Convert Data
Converting the source structure data to the destination by applying the conversion rules
that have mentioned in step 4 and step 5.
Step 11: Display Converted Data
Also useful for checking the values converted.
Step 12: Create Batch Input Session
This will create a BI session in SM35.
Step 13: Run Batch Input Session
This step will call SM35. One can run the session in SM35. You can run in the
foreground, Error mode, or background. Preferably run in Foreground for testing some
few records…once confirmed the update then run in the background.
How to transport the LSMW project from Test to Production system;
The LSMW projects can be transported between systems via the export /import method.
You can export the entire project as a text file and that can be imported to another
system.
In MSS no changes are allowed, so before importing to MSS, give the MSS file path in
MST and then do an export.
