Hi,
LSMW means Legacy System Migration Workbench which is transaction code itself too.
This is the tool used to upload the Data to SAP system from Legacy.
During implementation, all the data, with same transaction similar field to be maintained then this tool will be used.
Example: A company having 5000 materials, so creating 5000 times material master is very labories and manually maintaing the field values leads to Human error. Instead of this do recording once in LSMW, maintain all the steps wrt that create excel file maintain data in that, save it in tab delimated formate and upload it. This u can do it in foreground/backgrond. Like this it is very much required very offenly. Every consultant irrespective of his module he should have knowledge in LSMW.
IN PP Module LSMW is used to upload master datas
1) Material master
2) BOM
3) Routing.
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
T code is also same LSMW.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Legacy System Migration Workbench
Purpose
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.
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 details, 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:
u2022 Import techniques: Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods.
u2022 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.
u2022 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.
u2022 Action log: All the actions associated with an object are stored in an action log.
u2022 The field assignments for all parts of a project can be downloaded/uploaded in one step.
u2022 Unassigned source fields: Neglected data can be displayed.
u2022 Source fields: You can create source fields by copying them from other sources.
u2022 Processing times: The ABAP code can be added to at different times.
u2022 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.
u2022 Documentation: User-specific documentation can be stored at different levels and formatted into an overall documentation by pressing the appropriate button.
Constraints
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).
Pls refer below
www.erpgenie.com/saptech/lsmw.htm
For Material Master: Use Recording menthod
BOM create : use std Object method
Production Version :Use Record method (Mass maintenance)
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
Execute.
3. Maintain object attributes.
Execute
select Batch Input recording
goto->Recording overview
create
recording name.
enter transaction code.
start recording
do recording as per ur choice.
save + back.
enter recording name in lsmw screen.
save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
Here you have to enter the name of internal table.
display change
create
save + back
3. MAINTAIN SOURCE FIELDS.
display change
select structure
source_fields->copy fields.
a dialogue window will come .
select -> from data file
apply source fields
enter No. of fields
length of fields
attach file
save + back
4. MAINTAIN STRUCTURE RELATIONS
display change
save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
display change
click on source field, select exact field from structue and enter
repeat these steps for all fields.
save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
execute
save + back
7. SPECIFY FILES.
display change
click on legacy data
attah flat file
give description
select tabulatore
enter
save + back
8. ASSIGN FILE
execute
display change
save + back
9. IMPORT DATA.
execute
display change
save + back
10. DISPLAY IMPORTED DATA
enter ok, it willl show records only.
back
11. CONVERT DATA
execute
display change
save + back
12. DISPLAY CONVERTED DATA
execute
display change
save + back
13. CREATE BATCH INPUT SESSION
tick keep batch input folder
F8
back
14. RUN BATCH INPUT SESSION.
sm35 will come
Object name will be shown here
select object & process
Hope it will helps,
Regards,
Imran
Edited by: imran shek on Jan 15, 2009 12:52 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.