Generally, we use LSMW to upload the master data or transaction data, when we want to use LSMW to upload the configurational Item in mass then it’s always a challenge, as for recording we require Transaction code and programs (for some configurational nodes which is not available).

Some projects have requirement to create many activity areas depending upon the different activity (like storing the product to different temperature), for such scenarios we need to activity different Physical activity area. Its then become difficult to create this physical activity area in mass manually and this is where LSMW helps to create these entries in bulk.

Creating a Legacy System Migration Workbench (LSMW) project in an SAP Extended Warehouse Management (EWM) system involves several steps. LSMW is a tool that supports data migration from non-SAP systems (“legacy systems”) to SAP systems. Below are the general steps to create and execute an LSMW project in SAP EWM:

In S4HANA 2021 and above its easy to create LSMW for configurational item also using recording as S4HANA provide the transaction code information for each configurational node.

Physical Inventory Area

If we want to upload the physical activity area in mass in system using LSMW then we can identify the Tcode using below path:

The highlighted one is the code we can use for recording.

LSMW to create physical inventory activity area to upload the configuration in masses.

Then follow the normal procedure to create the Projects information.

Accessing LSMW:
- Log in to your SAP EWM system.
- Use transaction code LSMW to access the Legacy System Migration Workbench.
Create a New Project:
- In the initial screen of LSMW, click on “Create” to create a new project.
- Enter the project name, subproject name, and object name. These names should be meaningful and describe the migration process.

PROGRAM – /LIME/SAPLPI_CUST

Define Object Attributes:

In this step, you define the object attributes. Choose “Batch Input Recording” if you want to record the transaction or “Direct Input” if you are loading data directly into SAP tables.
If you choose “Batch Input Recording,” create a new recording by specifying the transaction code (e.g., /SCWM/ADHU for handling units in EWM).

For recording use transaction code

Maintain Source Structures:

Define the structure of the source file. For example, if you are importing data from a CSV file, define the structure of this file here.

Maintain Source Fields:

Specify the fields in your source structure. This involves defining the mapping between the source file and the SAP system.

Step 4 Assign relationship

Maintain Structure Relations:

Map the source structures to the target structures in SAP. This step establishes the relationship between the source data and the target data.

Auto Mapping of fields

Maintain Field Mapping and Conversion Rules:

Map the source fields to the target fields. This step involves detailed field mapping and defining any necessary conversion rules. Conversion rules are used to transform the source data to fit the target data requirements.