IBM Global Services

SAP Legacy System Migration Workbench

SAP Legacy System Migration Workbench| 7.12.02

March-2005

© 2005 IBM Corporation

IBM Global Services

Objectives
 The participants will be able to:
 Describe the different data import technique of LSMW.  Create the source structures and fields to read input file data.  Map source structures with target structures using conversion rules.

 Read and convert input file records into SAP.
 Upload the legacy data into SAP using LSMW.

2

SAP Legacy System Migration Workbench| 7.12.02

March-2005

© 2005 IBM Corporation

IBM Global Services

Data Migration In SAP Projects
Several data migration methods are there to transfer legacy data into SAP

3

SAP Legacy System Migration Workbench| 7.12.02

March-2005

© 2005 IBM Corporation

IBM Global Services

Importance of data migration
 What is data migration?
 Initial data transfer
 Implement SAP R/3  Move data from legacy system to Sap R/3  Switch off legacy system

 Periodic data transfer (interfacing)
 Exchange data between R/3 and other systems

 Why is data migration important?
 Accounts for 15% - 20% of the total SAP R/3 implementation costs.  Smaller implementation projects: up to 40%

4

SAP Legacy System Migration Workbench| 7.12.02

March-2005

© 2005 IBM Corporation

12.IBM Global Services Data migration  Why is data migration so expensive?  In many cases  Need to develop conversion Programs  Need to deal with lots of technical details and different technologies  What does SAP offer now?  LSMW (Legacy System Migration Workbench) 5 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

12.IBM Global Services What is LSMW? 6 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

BAPIs.  Greatly reduces the amount of development time needed to create conversion programs.12. Batch Recordings. and IDOC in-bound processing.IBM Global Services LSM Workbench  New tool from SAP to aid in data conversions.02 March-2005 © 2005 IBM Corporation . 7 SAP Legacy System Migration Workbench| 7.  Can be used for Direct Input.

02 March-2005 © 2005 IBM Corporation .  Object is assigned to a Sub project  Structure Relationships are Field mappings between the Source and the Target Structures within an Object  Field Assignments use Place Holders and Conversion Rules that define how the Field contents are to be converted 8 SAP Legacy System Migration Workbench| 7. A project can have any number of subprojects assigned to it.IBM Global Services Key building blocks for LSMW conversion program  Project serves as an organizational unit used to combine Mapping and Field assignments  Sub Project is an organizational unit subordinated to the project.12.

12.  Total migration of data will be under a particular project.IBM Global Services An Example Scenario  Data migration in a company with several plants.  Data migration for the individual plants within it can be classified as several sub projects under the said project.  An object assigned to a certain sub project can be for customer master upload or material master upload or FI documents upload etc.02 March-2005 © 2005 IBM Corporation . 9 SAP Legacy System Migration Workbench| 7.

IBM Global Services How LSM Workbench works One or several files Legacy data on PC Structure relations Data that has been read Read data Legacy data on application server Field assignments Convert data R/3 Standard Batch Input processing Converted data Direct Input processing IDoc inbound processing March-2005 Conversion rules SAP Application Server 10 SAP Legacy System Migration Workbench| 7.02 © 2005 IBM Corporation .12.

12.IBM Global Services Steps to create new LSMW object  Launch the tool by running transaction LSMW from SAP.02 March-2005 © 2005 IBM Corporation . 11 SAP Legacy System Migration Workbench| 7.

12.02 March-2005 © 2005 IBM Corporation .IBM Global Services Main Design Steps  Execute each of the design steps sequentially 12 SAP Legacy System Migration Workbench| 7.

12.IBM Global Services Maintain Object Attributes  Configure basic attributes for the data upload 13 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

12.IBM Global Services Maintain Object Attributes (Contd.) 14 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

02 March-2005 © 2005 IBM Corporation .IBM Global Services Maintain Source Structures  Build Source Structure Hierarchy with all Fields of the Legacy System 15 SAP Legacy System Migration Workbench| 7.12.

12.IBM Global Services Maintain Source Fields  Create source fields in each of the source structures in the hierarchy 16 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

IBM Global Services Uploading Multiple Structures using a Single Data File  Insert Record Type Identifier (STYPE) as the First Field in each of the Source Structures 17 SAP Legacy System Migration Workbench| 7.12.02 March-2005 © 2005 IBM Corporation .

02 March-2005 © 2005 IBM Corporation .12.IBM Global Services Maintain Structure Relation  Create Relationships between the Source and the Target Structures 18 SAP Legacy System Migration Workbench| 7.

12.IBM Global Services Maintain Field Mapping and Conversion Rules  Assign Source/Legacy Fields of each structure to R/3 Fields. we may use Automatic Field Mapping facility using option Extras -> Auto-Field Mapping 19 SAP Legacy System Migration Workbench| 7. This can be done individually for each R/3 field of the Target Structure. For Time consuming and Complex Structures.02 March-2005 © 2005 IBM Corporation .

02 March-2005 © 2005 IBM Corporation . 20 SAP Legacy System Migration Workbench| 7.IBM Global Services Specify Conversion Rule  Use predefined conversion rules or create your own conversion rule in the ABAP editor.12.

12. if needed.02 March-2005 © 2005 IBM Corporation . 21 SAP Legacy System Migration Workbench| 7.IBM Global Services Create Global Data / Form Routines  Create Global Data Definitions and Subroutines. for Custom Conversion Rules – use the option Extras -> Display Variant for this purpose.

02 March-2005 © 2005 IBM Corporation .12. User Defined Routines  Create Re-usable Form Routines and use them in the Conversion rules during Field Mappings 22 SAP Legacy System Migration Workbench| 7.IBM Global Services Maintain Fixed Values. Translations.

12.IBM Global Services Reusable Translation  Reusable Translation is very useful for defining conversion rules for a field 23 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

 <Project>_<Subproject>_<Object>.IBM Global Services Specify Files  File containing Legacy Data can reside either in user PC or in the Application Server.lsmw.  <Project>_<Subproject>_<Object>.12. the input file must be located on the Application server (Either Logical or Physical File).read and. Use transaction FILE to create logical file.conv.02 March-2005 © 2005 IBM Corporation .  File names for Read Data and Convert Data are defaulted by SAP and are respectively. 24 SAP Legacy System Migration Workbench| 7.  For Background Processing.lsmw.

File Type and Code page 25 SAP Legacy System Migration Workbench| 7. File Structure. Delimiter used.02 March-2005 © 2005 IBM Corporation .12.IBM Global Services File Properties  Input File Properties determine File Contents.

02 March-2005 © 2005 IBM Corporation .12.IBM Global Services Assign Files  Map the Source Structures to the Data Files 26 SAP Legacy System Migration Workbench| 7.

12.IBM Global Services Execution of LSMW program Execution Steps 27 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

conv).read).02 March-2005 © 2005 IBM Corporation .IBM Global Services Uploading Legacy File Data  Use Read Data to execute the SAP generated Read Program /1CADMC/SAP_LSMW_READ_<8 digit identifier> to get the Legacy data from the Input File to an intermediate File (*.  Use Convert Data to execute SAP generated Conversion Program /1CADMC/SAP_LSMW_CONV_<8 digit identifier> to map the Data Read in the previous step to the Target R/3 fields using the Predefined Conversion Rules into another intermediate File (*. 28 SAP Legacy System Migration Workbench| 7.12.  Execute the corresponding Batch Input or Direct Input program for uploading the Converted data into SAP.

12.IBM Global Services Customizing Design Steps  Design Steps can be customized using the option Extras -> Personal Menu 29 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

IBM Global Services LSMW Recoding  In LSMW recording can be used to upload legacy data into SAP 30 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .12.

02 March-2005 © 2005 IBM Corporation .  The Input Data File for Periodic Data Transfer should reside on the Application Server.12.  Use SAP standard program /SAPDMC/SAP_LSMW_INTERFACE for Transferring Data Periodically. 31 SAP Legacy System Migration Workbench| 7.IBM Global Services Periodic Data Transfer  Periodic Data Transfer can be used if the Data Transfer Type specified under Object Attributes is ‘Periodic’.

32 SAP Legacy System Migration Workbench| 7. Partner Type and Partner Number.02 March-2005 © 2005 IBM Corporation .12.IBM Global Services LSMW using IDOCs  Use option Settings -> IDOC Inbound Processing to configure File Port.

12.  A set of Business Object Methods(BAPIs) are also provided by SAP for certain Objects .IBM Global Services What data can be transferred by LSM Workbench ?  SAP provides Standard Batch Input/ Direct Input Programs for a set of Objects  For any other uploads Batch Input Recordings can be created based on the required Transaction. 33 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

12.02 March-2005 © 2005 IBM Corporation .IBM Global Services What data can be transferred by LSM Workbench ?  Examples of Master Data  Examples of Transaction Data  Customer  Vendors  Bill of Materials  GL Accounts  Condition Records  Sales Orders  Purchase Orders  Purchase Requisitions  Human Resource  Purchasing Info Records  Financial Documents  Good Movements 34 SAP Legacy System Migration Workbench| 7.

02 March-2005 © 2005 IBM Corporation . 35 SAP Legacy System Migration Workbench| 7.IBM Global Services Export/Import and Transporting LSMW Project  LSMW Projects can be downloaded to a file and that project can also be imported from the file.12.

IBM Global Services Limitations of LSM Workbench  Cannot be used to extract data from Legacy Systems  Cannot be used for outbound interfaces  Not 100% flexible 36 SAP Legacy System Migration Workbench| 7.12.02 March-2005 © 2005 IBM Corporation .

37 SAP Legacy System Migration Workbench| 7.IBM Global Services Demonstration  Use of Legacy System Migration Workbench (LSMW) tool with an example.12.02 March-2005 © 2005 IBM Corporation .

IBM Global Services Practice  Use of Legacy System Migration Workbench (LSMW) tool with an example.12. 38 SAP Legacy System Migration Workbench| 7.02 March-2005 © 2005 IBM Corporation .

12.IBM Global Services Summary  LSMW can be used to migrate legacy data into SAP by Direct Input. data mapping.  Basic steps of LSMW are selection of data import method.  LSMW cannot be used for outbound interfaces.  Custom ABAP code can be written in data mapping section to perform validation. data selection and to fulfill other customized requirements. BAPIs. data read and conversion and finally data upload. Batch Recordings.02 March-2005 © 2005 IBM Corporation . and IDOC in-bound processing. file assignment. creation of source structure and fields. 39 SAP Legacy System Migration Workbench| 7.

02 March-2005 © 2005 IBM Corporation .12.IBM Global Services Questions  What are the key building blocks for a LSMW conversion program ?  What data can be transferred by LSM Workbench ?  What are the limitations of LSMW ? 40 SAP Legacy System Migration Workbench| 7.

Sign up to vote on this title
UsefulNot useful