LSMW To Upload HCM Personnel Data Step by Step
LSMW To Upload HCM Personnel Data Step by Step
1. Step 1: Maintain Object Attributes. Select this radio button and click on execute. ...
2. Step 2: Maintain Source Structures. ...
3. Step 3: Maintain Source Fields. ...
4. Step 4: Maintain Structure Relations. ...
5. Step 5: Display Field Mapping and Conversion. ...
6. Step 6: Maintain Fixed Values, Translations, User-Defined Routines. ...
7. Step 7: Specify Files.
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 .
Go to LSMW
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.
We are clicking ‘Default all’ button, so that all the fields which we touched during
recording are included
Save and back to main Screen.
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
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.
Source structures are helpful in building hierarchical relationships. While uploading the data system
always checks highest level structure first before going for subordinate structure.
Here we assign all the fields which need to upload to source structure.
Click on change and then select the source field and then Table.
Note: exclude TABNAME and TCODE which are not required to maintain separately,
system will take these from recording we made.
Save and back.
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.
Here we establish the relationship between legacy and R/3 based on object fields.
No need to maintain this step, unless and until if there exist any user defined routines, which helpful
for reusable.
Note: Generally we receive legacy file in excel format, so save this file as Text