Legacy System Migration Workbench (LSMW) is an ECC6 tool that supports one-time and periodic transfer of data from non-SAP systems (legacy systems) to ECC6. This easy-to-use tool supports the conversion of data from the non-SAP system that can then be imported into the ECC6 System using batch input, call transaction, direct input, BAPIs, or IDocs.
LSMW provides a recording function, which you can use to generate a data migration object from a create or change transaction. In the HCM scenario of loading Organizational Management data the creation of a one-time load is the relevant option. The recording function is to record object creation. A spreadsheet is used to provide the new object data. Periodic or scheduled repeating transfers are not possible in this scenario.
Loading data into the Personnel Administration and Organization Management databases from spreadsheets coupled with a recording is a straightforward way to work. The PNPCE and PCH logical databases have a simple ‘Flat’ structure and spreadsheets are a familiar tool for use in data management. Because these types of load are so commonly used, the LSMW application contains model entries in the form of Projects, Subprojects and Objects. We will review the process to create OM objects.
For more details on LSMW with other data transfer scenarios please see Course BC320 - Data Transfer.
At its highest level the process of using LSMW with a spreadsheet and a recording is as follows:
- Configure the system to allow external object ID entry
- Create an external file storing the data to upload
- Create a structure to read the data into the Read file
- Read in the data
- Create a mapping of fields and instructions for any conversion of the data
- Convert the data and store in the Convert file
- Select the method of data transfer, in our case, a batch file
- Run the batch file and replicate the entry of the data as if using the recorded transaction
Data loaded in this way is still validated in the same manner as it would be via the transaction you recorded.
System preparation: External Object ID range
Creating new OM objects from a spreadsheet includes supplying the new object ID numbers as a column of data in the spreadsheet. This represents External numbering and requires the range of ID numbers you wish to use to be configured as allowed for external entry in the relevant customizing table. The ID numbers being uploaded must be un-used in the target system or they will be rejected.
LSMW Project Structure
As of SAP NetWeaver Application Server Release 6.20, the LSMW is integrated in the SAP system. It is accessed via transaction LSMW. Work is organized into Projects, Subprojects and Objects. When working with OM objects we will have separate LSMW objects for object 1000 and for object 1001 which will be loaded in that order.
LSM Projects Subprojects and Objects
LSMW Process Steps
When we create an object in a project and subproject, a default sequence of process steps is displayed for that object. Our job is to create the setup for each step.