Professional Documents
Culture Documents
This document contains step by step instructions to use LSMW to update Vendor Master
Records. This demonstration covers 2 different techniques to build LSMW program:
Batch Recording
Standar Batch / Direct Input
Demo Example 1: LSMW to Update Vendor Master Records with Batch Recording
Access to Legacy System Migration Workbench by using t-code LSMW.
LSMW helps to organize data conversion activity by grouping the activities into Project,
Subproject and Object structure. Create a Project called Z_LSMW_DEMO01 and a Subproject
as Z_MM and Object as Vendor_Master.
Execute the Object created within the Project/ Subproject and you will see the step by step
guideline provided by LSMW.
Click create and enter the Recording name as ZVENDOR, the description as Vendor Master
Update, and the transaction code as XK02.
Transaction code XK02 will be called. Enter the key vendor information (vendor number,
company code, and Purchasing Organization) and choose the respective area that you would
like to update.
Make changes to fields required (in this demo: Prev. acct. no, Incoterm 1, incoterm 2, minimum
order value).
Once the transaction is completed, system will records the flow of screens and fields and saves
them as target fields. Note that the fields are populated with default values. The values you
entered when you recorded the transaction are set by default.
Note that if you have more fields in the recording than needed, you can remove them by clicking
icon.
Double-click on the field RF02K-LIFNR and enter the name as LIFNR and the description as
Vendor and remove the default value. Repeat the same steps for other target fields.
Go back to the initial screen and save the object attributes after assigning the new recording
ZVENDOR created.
icon to
Tips: The source structure fields can be created with reference to Object Overview which can be
found from the LSMW initial screen.
Similarly, assign Source Field rules to the remaining fields and save the field mapping.
Alternatively, you can use constant rule icon to default certain target field to certain value.
Example, if you would like to default Company Code to AU01, point your cursor to BUKRS, click
on
and input company code as AU01. You may leave this column in your upload
template blank and system will upload the data with default company code value as AU01.
1
3
Demo Example 2: LSMW to Update Vendor Master Records with Standard Batch / Direct
Input
As an alternative to using Transaction Recording, you could also use a standard SAP object to
update Vendor Master Records. Business Object 0040 is already pre-defined in the system
with standard Batch Input Interface Program RFBIKR00.
Create a Project called Z_LSMW_DEMO01 and a Subproject as Z_MM and Object as
Z_VENDOR2.
Step 1: Maintain Object attributes
In this example, you will be updating the vendor master records with the help of pre-defined
Batch Input Interface Program RFBIKR00. Choose radio button Standard Batch/Direct Input.
Enter Object 0040 for Vendor Master records and default method 0001 and click on Save.
Similarly, assign Source Field rules to the remaining fields and save the field mapping.
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used
across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we specify the file path of the upload template. The upload template file is a Tab
delimited with the first row as header fields saved in your local PC.
Try removing all path definitions and use only the filename.
1
3
After executing the Batch Input Session, you can view the summary of upload activity. You will
see what the total records are read as well as total records that have been created/uploaded
successfully.
Click on Transactions tab to see the index of record which has failed to update and click on
Screen tab to see the details of screen input.