LSMW for OM Objects (org. unit, positions, jobs)
I want share some knowledge regarding how to upload the OM Objects like jobs, positions & Org. units through LSMW with batch input recording.
I know everyone is well versed with this LSMW, just consider it as a quick reference and step-wise document for who doing for the first time LSMW for OM Objects.
We have to create all the OM Objects External Number range before uploading the objects through LSMW. Because system will not consider for Internal number ranges while recordings.
Creating Project / Subproject and Object:
Go to Tcode- LSMW
Click on Create button and give the name of the Project, Subproject and Object as desired
*Give Project names as SMALL otherwise while assigning upload file at step 7 Specify files, error will come. System path is not allowed more than 45 words (this is standard by the system)
Recording: Sample recording of Objects
- In menu bar, Goto Recordings
Now click on Create Recording and give the Recording name and description
System will ask for Transaction code, give PP02
Maintain the fields that are mandatory, to create object types
Save the Record and click the button Back
Now system will show the recording results in the screen Create Recording
Click the Button Default All to default the system for Technical fields which are entered while recording
Save the screen and go back our Recording was completed
Once again go back to the LSMW screen and Execute the Project
Now, we have to do step by step LSMW (14 steps)
Step 1: Maintain Object Attributes
Select this radio button and click on executeà (Do same for other steps)
Now, click on Display/ Change icon (do this for every step, because by default it will be display mode)
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
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à
- Enter details as shown belowà
Save and go 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à
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.
Make excel sheet as shown:
- Now select ‘Maintain Source Fields’ button and execute
- Click on ‘table maintenance
Paste from the excel sheet which we maintained.
* we can take either C or D for the Date format accordingly upload data has to be maintained
Save and go 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.
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
Note: Make sure that you select your recording before auto field mapping
Click on accept proposal for all the fields which want to upload
After auto field mapping complete, save and back.
Step 6: Maintain Fixed Values, Translations, User-Defined Routines
No need of this step-6
Step 7: Specify Files
In this step, you specify the location of the legacy file. The file in tabular form with first row field names
Now, double click on ‘Legacy Data – On the PC (Front End)
Save and go back
Example of Excel file to upload in the .TXT form
Step 8: Assign Files
Here, we just check whether file is assigned to source structure or not.
Save and go back
Step 9: Read Data
Here our legacy data is read
Execute Now, next screen shows how many number of records have been read
Step 10: Display Read Data
Here, we can display all for part of the data by giving line numbers
Check, whether data has been correctly fit into fields
Step 11: Convert Data
Here, whatever data has been read will convert to SAP standards.
Click on Execute button, it shows how many records have been converted. It should be same as data which have been read in step 9.
Step 12: Display Converted Data
Here, converted data can be viewed for cross check.
Data from the legacy file is fitting to correct fields, so we configured all prior steps without any mistake.
Note: If data is not fitting correctly, then we need to cross check Step3 and Step5.
Step 13: Create Batch Input Session
In this step, we create session for batch input
Make sure you check box for ‘Keep batch input folder’ is active
Step 14: Run Batch Input Session
Here we run the batch input session which we created in step 13.
Select Session and execute process
Here we can choose options, how upload should be done
It is recommendable that, first 3 to 4 records upload foreground to make sure data is uploading correct, for rest of records select ‘Display errors only.
Now legacy data will we upload to Master data of employees in SAP system.
Testing: whether objects are created or not
Table V_T527X (Org. units)
Table T528B (Positions)
Table T513 (Jobs)
For relationship LSMW:
Objects Relationships and Report RHINTE10
Thanks and Best Regards,