DOWNLOAD PDF : https://icedrive.net/dashboard/#/cloud/Zm9sZGVyLTIwMzI2MjQ1NA

Legacy System Migration Workbench

Use

The Legacy System Migration Workbench (LSMW) is a tool that supports data migration from legacy systems (non-SAP systems) to SAP systems. It is a cross-platform component of the SAP system.
Implementation Considerations
Do not use the LSMW before the SAP system has been installed and application customizing has been completed.

Integration

The LSMW is a cross-application component (CA) of the SAP system.
The tool has interfaces with the Data Transfer Center and with batch input and direct input processing as well as standard interfaces BAPI and IDoc.
The Legacy System Migration Workbench is called using transaction LSMW.
Features
Instead of individual tables or field contents, the tool migrates user-defined datasets (known as objects), which are combined according to business criteria. In addition to using standard import techniques, you can also generate user-specific objects. For more information, see Recordings.
The LSMW comprises the following main functions:
1. Read data (legacy data in spreadsheet tables and/or sequential files). You can use any combination of PC and server files.
2. Convert data (from the source into the target format).
3. Import data (to the database used by the SAP application).
The following additional functions are available:
• Import techniques: Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods.
• Global Functions: You can call certain functions from an ABAP code location of your choice, and so influence the procedure used to migrate your data.
• Editor Function: The source code for a target field can be checked. You can insert source fields, global variables, and global functions as well as use the Pretty Printer.
• Action Log: All the actions associated with an object are stored in an action log.
• The field assignments for all parts of a project can be downloaded/uploaded in one step.
• Unassigned Source Fields: Neglected data can be displayed.
• Source Fields: You can create source fields by copying them from other sources.
Copy.
• Processing Times: The ABAP code can be added to at different times.
• Authorizations: The LSM Workbench is independent from the client. Access to the LSMW is controlled by authorizations. The assignment of these authorizations is basically independent from the client. The Display, Execute, Change, and Administration functions can be controlled by assigning authorizations.
• Documentation: User-specific documentation can be stored at different levels and formatted into an overall documentation by pressing the appropriate button.
Constraints
Restrictions The LSMW supports a one-time transfer of data (initial data load) and also offers a restricted support of permanent interfaces. Thus, a periodic transfer of data is possible. The LSMW, however, does not include any functions for monitoring of permanent interfaces. The tool does not support any data export interfaces (outbound interfaces).
More Information
More information about data conversion with the LSMW:
• Conceptional Preprocessing
• Authorizations
• Exporting a Project
• Importing a Project
• Migration of Data with LSMW
• Troubleshooting

https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-US/4d/afeb6ad8f66d57e10000000a42189e/frameset.htm
Introduction
The Legacy System Migration Workbench (LSMW) is a instrument to transmit data from legacy systems into an SAP 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 Organization and Staffing (Human Resources ) > PPOME – Change

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 PP01 – General

In Maintain object screen, you can proceed as follow:

Object

Create

Enter an abbreviation and name for the organizational unit.

Specify a validity period for the organizational unit.

Save the Entry .

Exit

The following screen will appear.

Now, click on Default All

We are clicking ‘Default all’ button, so that all the fields which we touched during recording are included

and save

and press back

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 change

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 SAP 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 SAP based on object fields.
In menu bar, go to Maintain Field Mapping and Conversion Rules

After Execute go to Extra and then Auto Field Mapping.

Now accept proposal for all the fields which need to upload

RULE

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)

Convert the data on Notepad.

Here Double Click on Legacy Data and give the Path,

Save and Back

Step 8: Assign Files
Here, we just check whether file is assigned to source structure or not.

Save and Back

Step 9: Read Data
Here our legacy data is read

BACK

Step 10: Display Read Data
Here, we can display all for part of the data by giving line numbers

Step 11: Convert Data
Here, whatever data has been read will convert to SAP standards

Step 12: Display Converted Data
Here, converted data can be viewed for cross check

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

BACKGROUND

DISPLAY ERRORS ONLY

Now legacy data will we upload to Master data in SAP system
To check Go to PPOME

Updated Successfully.