IBM Global Services SAP Legacy System Migration Workbench| 7.12.02 March-2005 © 2005 IBM Corporation SAP Legacy System Migration Workbench
Nov 11, 2014
IBM Global Services
SAP Legacy System Migration Workbench| 7.12.02
March-2005 © 2005 IBM Corporation
SAP Legacy System Migration Workbench
IBM Global Services
© 2005 IBM Corporation2 March-2005SAP Legacy System Migration Workbench| 7.12.02
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.
IBM Global Services
© 2005 IBM Corporation3 March-2005SAP Legacy System Migration Workbench| 7.12.02
Several data migration methods are there to transfer legacy data into SAP
Data Migration In SAP Projects
IBM Global Services
© 2005 IBM Corporation4 March-2005SAP Legacy System Migration Workbench| 7.12.02
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%
IBM Global Services
© 2005 IBM Corporation5 March-2005SAP Legacy System Migration Workbench| 7.12.02
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)
IBM Global Services
© 2005 IBM Corporation6 March-2005SAP Legacy System Migration Workbench| 7.12.02
What is LSMW?
IBM Global Services
© 2005 IBM Corporation7 March-2005SAP Legacy System Migration Workbench| 7.12.02
LSM Workbench
New tool from SAP to aid in data conversions.
Can be used for Direct Input, Batch Recordings, BAPIs, and IDOC in-bound processing.
Greatly reduces the amount of development time needed to create conversion programs.
IBM Global Services
© 2005 IBM Corporation8 March-2005SAP Legacy System Migration Workbench| 7.12.02
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. A project can have any number of subprojects assigned to it.
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
IBM Global Services
© 2005 IBM Corporation9 March-2005SAP Legacy System Migration Workbench| 7.12.02
An Example Scenario
Data migration in a company with several plants.
Total migration of data will be under a particular project.
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.
IBM Global Services
© 2005 IBM Corporation10 March-2005SAP Legacy System Migration Workbench| 7.12.02
How LSM Workbench works
One or several files
R/3 S
tand
ard
Convert data
Batch Input processing
Legacy dataon PC
Legacy dataon PC
Read data
Converted data
Converted data
Data that has been
read
Data that has been
read Legacy data on application
server
Legacy data on application
server
IDoc inboundprocessing
Direct Input processing
Structure relations
Field assignments
Conversion rules
Structure relations
Field assignments
Conversion rules
SAP Application Server
IBM Global Services
© 2005 IBM Corporation11 March-2005SAP Legacy System Migration Workbench| 7.12.02
Steps to create new LSMW object
Launch the tool by running transaction LSMW from SAP.
IBM Global Services
© 2005 IBM Corporation12 March-2005SAP Legacy System Migration Workbench| 7.12.02
Execute each of the design steps sequentially
Main Design Steps
IBM Global Services
© 2005 IBM Corporation13 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Object Attributes
Configure basic attributes for the data upload
IBM Global Services
© 2005 IBM Corporation14 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Object Attributes (Contd.)
IBM Global Services
© 2005 IBM Corporation15 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Source Structures
Build Source Structure Hierarchy with all Fields of the Legacy System
IBM Global Services
© 2005 IBM Corporation16 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Source Fields
Create source fields in each of the source structures in the hierarchy
IBM Global Services
© 2005 IBM Corporation17 March-2005SAP Legacy System Migration Workbench| 7.12.02
Uploading Multiple Structures using a Single Data File
Insert Record Type Identifier (STYPE) as the First Field in each of the Source Structures
IBM Global Services
© 2005 IBM Corporation18 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Structure Relation
Create Relationships between the Source and the Target Structures
IBM Global Services
© 2005 IBM Corporation19 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Field Mapping and Conversion Rules
Assign Source/Legacy Fields of each structure to R/3 Fields. This can be done individually for each R/3 field of the Target Structure. For Time consuming and Complex Structures, we may use Automatic Field Mapping facility using option Extras -> Auto-Field Mapping
IBM Global Services
© 2005 IBM Corporation20 March-2005SAP Legacy System Migration Workbench| 7.12.02
Specify Conversion Rule
Use predefined conversion rules or create your own conversion rule in the ABAP editor.
IBM Global Services
© 2005 IBM Corporation21 March-2005SAP Legacy System Migration Workbench| 7.12.02
Create Global Data / Form Routines
Create Global Data Definitions and Subroutines, if needed, for Custom Conversion Rules – use the option Extras -> Display Variant for this purpose.
IBM Global Services
© 2005 IBM Corporation22 March-2005SAP Legacy System Migration Workbench| 7.12.02
Maintain Fixed Values, Translations, User Defined Routines
Create Re-usable Form Routines and use them in the Conversion rules during Field Mappings
IBM Global Services
© 2005 IBM Corporation23 March-2005SAP Legacy System Migration Workbench| 7.12.02
Reusable Translation is very useful for defining conversion rules for a field
Reusable Translation
IBM Global Services
© 2005 IBM Corporation24 March-2005SAP Legacy System Migration Workbench| 7.12.02
Specify Files
File containing Legacy Data can reside either in user PC or in the Application Server.
For Background Processing, the input file must be located on the Application server (Either Logical or Physical File). Use transaction FILE to create logical file.
File names for Read Data and Convert Data are defaulted by SAP and are respectively.
<Project>_<Subproject>_<Object>.lsmw.read and.
<Project>_<Subproject>_<Object>.lsmw.conv.
IBM Global Services
© 2005 IBM Corporation25 March-2005SAP Legacy System Migration Workbench| 7.12.02
File Properties
Input File Properties determine File Contents, Delimiter used, File Structure, File Type and Code page
IBM Global Services
© 2005 IBM Corporation26 March-2005SAP Legacy System Migration Workbench| 7.12.02
Assign Files
Map the Source Structures to the Data Files
IBM Global Services
© 2005 IBM Corporation27 March-2005SAP Legacy System Migration Workbench| 7.12.02
Execution of LSMW program
Execution Steps
IBM Global Services
© 2005 IBM Corporation28 March-2005SAP Legacy System Migration Workbench| 7.12.02
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 (*.read).
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 (*.conv).
Execute the corresponding Batch Input or Direct Input program for uploading the Converted data into SAP.
IBM Global Services
© 2005 IBM Corporation29 March-2005SAP Legacy System Migration Workbench| 7.12.02
Customizing Design Steps
Design Steps can be customized using the option Extras -> Personal Menu
IBM Global Services
© 2005 IBM Corporation30 March-2005SAP Legacy System Migration Workbench| 7.12.02
LSMW Recoding
In LSMW recording can be used to upload legacy data into SAP
IBM Global Services
© 2005 IBM Corporation31 March-2005SAP Legacy System Migration Workbench| 7.12.02
Periodic Data Transfer
Periodic Data Transfer can be used if the Data Transfer Type specified under Object Attributes is ‘Periodic’.
Use SAP standard program /SAPDMC/SAP_LSMW_INTERFACE for Transferring Data Periodically.
The Input Data File for Periodic Data Transfer should reside on the Application Server.
IBM Global Services
© 2005 IBM Corporation32 March-2005SAP Legacy System Migration Workbench| 7.12.02
LSMW using IDOCs
Use option Settings -> IDOC Inbound Processing to configure File Port, Partner Type and Partner Number.
IBM Global Services
© 2005 IBM Corporation33 March-2005SAP Legacy System Migration Workbench| 7.12.02
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.
A set of Business Object Methods(BAPIs) are also provided by SAP for certain Objects .
IBM Global Services
© 2005 IBM Corporation34 March-2005SAP Legacy System Migration Workbench| 7.12.02
What data can be transferred by LSM Workbench ?
Examples of Master Data
Customer
Vendors
Bill of Materials
GL Accounts
Human Resource
Examples of Transaction Data
Condition Records
Sales Orders
Purchase Orders
Purchase Requisitions
Purchasing Info Records
Financial Documents
Good Movements
IBM Global Services
© 2005 IBM Corporation35 March-2005SAP Legacy System Migration Workbench| 7.12.02
Export/Import and Transporting LSMW Project
LSMW Projects can be downloaded to a file and that project can also be imported from the file.
IBM Global Services
© 2005 IBM Corporation36 March-2005SAP Legacy System Migration Workbench| 7.12.02
Limitations of LSM Workbench
Cannot be used to extract data from Legacy Systems
Cannot be used for outbound interfaces
Not 100% flexible
IBM Global Services
© 2005 IBM Corporation37 March-2005SAP Legacy System Migration Workbench| 7.12.02
Demonstration
Use of Legacy System Migration Workbench (LSMW) tool with an example.
IBM Global Services
© 2005 IBM Corporation38 March-2005SAP Legacy System Migration Workbench| 7.12.02
Practice
Use of Legacy System Migration Workbench (LSMW) tool with an example.
IBM Global Services
© 2005 IBM Corporation39 March-2005SAP Legacy System Migration Workbench| 7.12.02
Summary
LSMW can be used to migrate legacy data into SAP by Direct Input, Batch Recordings, BAPIs, and IDOC in-bound processing.
Basic steps of LSMW are selection of data import method, creation of source structure and fields, data mapping, file assignment, data read and conversion and finally data upload.
Custom ABAP code can be written in data mapping section to perform validation, data selection and to fulfill other customized requirements.
LSMW cannot be used for outbound interfaces.
IBM Global Services
© 2005 IBM Corporation40 March-2005SAP Legacy System Migration Workbench| 7.12.02
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 ?