LSMW:Upload Master Data Using Batch Input Recording Part 1
Introduction
The Legacy System Migration Workbench (LSMW) is a instrument to transmit data from legacy systems into an R/3 System. LSMW supports a step-by-step process; if one step is executed and saved then next step automatically follows. Apart from formation of project/ subproject/ object and recording, there are 14 basic steps included in LSMW. This article explains clearly about each and every step.
Example, I am showing how to upload Personnel Data for an employee i.e. Infotype 0002 .
Creating Project/ Subproject and Object:
Go to LSMW
Give the name of the Project, Subproject and Object as desired
Recording:
In menu bar, Goto—->Recordings
Now, Select ‘Recordings’ and create —->Give recording name and description
Go to Transaction ‘PA30’
In Master data maintain screen, give Personnel No, infotype and subtype (if any), and click on create
Select The fields in whioch you want to input the data.
Save the Entry . The following screen will appear.
Now, click on Default All and save and press back
We are clicking ‘Default all’ button, so that all the fields which we touched during recording are included
Save and back to main Screen.
Processing basic steps in LSMW:
LSMW need to be configured 14 basic steps. Below you will find detailed step-by step procedure.
Click On execute
Step 1: Maintain Object Attributes
Select this radio button and click on execute
Now, click on Display/ Change icon Here, we are telling system that what kind recording should take into consideration while performing upload.
Select ‘Batch Input Recording’ and give name as shown below (Recording Name)
Save and Back.
Step 2: Maintain Source Structures
Source structures are helpful in building hierarchical relationships. While uploading the data system always checks highest level structure first before going for subordinate structure.
Select source structure and create
First click on Change button and then click on create button.
Save and Back.
Step 3: Maintain Source Fields
Here we assign all the fields which need to upload to source structure.
Click on Object Overview—->select table
Click on Object Overview—->select table
Click on change and then select the source field and then Table.
Copy the fields and length in excel sheet (for temporary)
Note: exclude TABNAME and TCODE which are not required to maintain separately, system will take these from recording we made.
Save and back.
Step 4: Maintain Structure Relations
Here we check whether structure relations between legacy and R/3 established or not.
In this step there is no need to change, just save and come back.
Save and Back.
Step 5: Display Field Mapping and Conversion
Here we establish the relationship between legacy and R/3 based on object fields.
In menu bar, go to ExtrasàAuto Field Mapping
After Execute go to Extra and then Auto Field Mapping.
Now accept proposal for all the fields which need to upload
Step 6: Maintain Fixed Values, Translations, User-Defined Routines
No need to maintain this step, unless and until if there exist any user defined routines, which helpful for reusable.
Step 7: Specify Files
In this step, you specify the location of the legacy file.
Note: Generally we receive legacy file in excel format, so save this file as Text
Now, double click on ‘Legacy Data – On the PC (Front End)
Dear Jazib Tairq,
Very helpful document. Thanks for sharing. Please continue sharing such a productive material.
Regards
Muhammad Umar
Very helpful document keep sharing such material.
Thanks
Thanks
good document and keep presenting your words and thoughts in such a good documents. well done.
Best Regards,
Suhaib Bin Aziz
Thank you for the review; Good stuff on LSMW!
Best.
Thanks Antoine
Good Job Jazib. Keep it up.
Thanks Zeeshan
good work done bachaa
Thanks Miss
Dear Jazib Tariq,
Nice and helpful document of LSMW.
Santosh Shivane
Thanks Santosh 🙂
Dear Jazib Tariq,
Appreciated your efforts for making this useful document.
Did you observe that LSMW did not delimit infotypes while uploading mass data? 😕
If so, is there a method to make LSMW to delimit infotypes while uploading data for infotype changes?
Regards,
TG
Nice one.... thanks
Dear Jazib,
Nice Documents.
Thanks and Regards,
Arpit
Thanks TG, Venkatesh and Arpit 🙂
Hi Tariq,
Your document is very good and useful.
Could u please share the document for BDC
Regards,
Neha.
Dear Jazib Tariq,
This manual is really helpful to me. Greatly appreciate your effort creating such a detailed documentation.
Many thanks!
Regards,
Nguyen Anh Khoa
Thanks Khoa
nice document
Thanks Surya
Good walkthrough. Some of the screenshots are a bit blurry though. For those of you who want a crisper copy, follow this link : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e04f8fc8-2ef3-2d10-dc8d-eb6fd0711157?QuickLink=index&overridelayout=true&49873160545562
Dear Triq, thanks for this details about LSMW.
My Pleasure Rajeev
Good Document. Can we upload the record for a change of position or organizational unit through T code pp01 or pp02 or pm01
Iam can able to see the change but not able to see the change in the organizational assignment infotype
😥
Just want to comment and say this is great. Thanks for posting it!
nice
Thanks Priya, Joseph, Andy
Hi Jazib Tariq,
Thanks a lot for the document. Its very helpful. Please can you share the file format for this with sample data. It will really help me in my practise.
Thanks again.
Regards,
Vandana
Hi Vandana,
You can use Excel as well as text file.
File format depends on your fields selection.