1 / 48

Legacy System Migration Workbench

Legacy System Migration Workbench. lsm@sap.com. What is. LSMW?. What is data migration ? / Subject of LSM Data transfer source: non-SAP systems (“legacy systems”) target: SAP System Initial data transfer from non-SAP systems to an SAP System

aric
Télécharger la présentation

Legacy System Migration Workbench

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Legacy System Migration Workbench lsm@sap.com

  2. What is LSMW?

  3. What is data migration? / Subject of LSM • Data transfer • source: non-SAP systems (“legacy systems”) • target: SAP System • Initial data transfer from non-SAP systems to an SAP System • Move data from legacy system to an SAP System • Switch off legacy system • Periodic data transfer (Interfacing) • Exchange data between an SAP System and other systems • Position of data migration • Requires customized SAP System (customizing must be finalized)

  4. Relevance of data migration? • Accounts for15% - 20% of the total SAP implementation costs • Smaller implementation projects: up to 40% • Why is data migrationso expensive? • In many cases • you need to develop conversion programs (which can not be used later on) • you need to deal with lots of technical details and different technologies • data volume depends on the project volume • the effort for programming does not depend on the data volume

  5. Data migration in 3 steps start 1. step 2. step 3. step target preparatory steps data on SAP data base data in legacy system fieldmapping and rules data import checklist LSMW

  6. What is LSMW (Legacy System Migration Workbench) ? • LSMW is a tool based on R/3. • LSMW supports periodic and single data transfer from a non-SAP system to an SAP System. • LSMW uses standard SAP interfaces.

  7. Requirements for the use of LSMW

  8. Organisational • Customizing of the SAP applications must be finished • Know how in LSMW (1-2 days) • Knowledge of the source data (Which fields means what?) • Knowledge of the SAP application (Which fields means what?) • technical know how • R/3 basis (batch input processing, IDoc processing) • ABAP • System requirements • For LSMW 3.0 (???): R/3 release 6.10 • For LSMW 1.7 (Sept. 2000): R/3 release 4.0x, 4.5x or 4.6x • For LSMW 1.0 (Sept. 1998): R/3 release 3.0F or 3.1x

  9. How does LSMW work?

  10. Legacy System R/3 Datenmigration Data Migration

  11. Define source structures Legacy System Vendor master DATA MIGRATION Bank data Contact person A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ... R/3

  12. Define source fields Legacy System Vendor master L1 L2 L3 L4 L5 L6 L7 ... DATEMIGRATION DATA MIGRATION B1 B2 B3 ... Bank data Contact person A1 A2 A3 A4 ... A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ... R/3

  13. Define structure relationships Legacy System Vendor master L1 L2 L3 L4 L5 L6 L7 ... B1 B2 B3 ... Bank data DATA MIGRATION Contact person A1 A2 A3 A4 ... A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ... R/3 ...

  14. Fieldmapping and conversion rules Legacy System Vendor master L1 L2 L3 L4 L5 L6 L7 ... DATA MIGRATION DATENMIGRATION B1 B2 B3 ... Bank data Contact person A1 A2 A3 A4 ... Move 1:1 translation Individual coding Fixed value/ constant A1 A2 A3 A4 A5 A6 A7 ... B1 B2 B3 ... C1 C2 C3 C4 ... R/3 ...

  15. Most common conversion rules predefined • Initial value • Constant • Assign (“MOVE”) • Fixed value • 1:1 translation • Translation via intervals • User-defined routines • Prefix • Suffix • Concatenate • Individual ABAP coding • D  DE • A  AT • F  FR Reusable • 001...100  10 • 101...200  20 • 201...300  30

  16. Central conversion rules (reusable rules) • Assure consistent data conversion in different data objects Material master Sales order Material number Purchase requisition Purchase order

  17. Legacy System DATA MIGRATION R/3 Further steps • read source data • data conversion • run import

  18. Legacy dataon PC Legacy data on application server How LSM Workbench works Structure relations Field mapping Conversion rules Read data Read data Convert data Batch Input processing Converted data Direct Input processing IDoc inboundprocessing One or several files SAP Standard

  19. H Customer #1 (header rec.) P Contact person #1 P Contact person #2 ... ... • What kind of data can be read? • Data from spreadsheet-based applications • MS Excel, MS Access, etc. • Data from host systems on SAP application servers • Fixed record length, end of record indicator or hexadecimal length field at the beginning • With and without separator • Code page conversion • “Hierarchical” data with “identifying field values” Identifyingstring(H=headerP=position)

  20. Which data can be migrated via LSMW? • ==> all data where an interface exists • Standard Batch Input, Standard Direct Input • precondition: application program • entries in tables SXDA* (DX-Workbench) • Batch Input Recording • Recording a transaction • Flat target structure (no header-position constellations with variable amount of positions) • Methods for Business Objects („BAPIs“) • All BAPIs for which an ALE-IDoc interface has been generated(by SAP development) • IDocs • All

  21. What does LSMW look like?

  22. Define project, subproject and object

  23. Select migration step

  24. Maintain attributes

  25. Enter structures of legacy system in the SAP System

  26. Define conversion rules and field mapping

  27. Generated conversion program

  28. Interface for data on PC

  29. Overview of migration object

  30. Overview of migration object

  31. Migration customizing: translation table

  32. recording

  33. Purpose Mapping and conversion rules that have been used in an SAP system should be used in another SAP system. Procedure Use the export and import function of LSMW Or: create a change request to use the standard transport system of SAP Condition Both SAP systems have the same LSMW-version (to transport rules from version 1.0 to 1.6 you must either convert the rules to 1.6 format before the export or import to version 1.0 and then do the upgrade of the rules) LSM- Version 1.6 LSM- Version 1.6 Transport of Mapping and Conversion Rules

  34. Job LSMW:additionalprogram to bescheduled Read data (only files on the application server can be used) Data conversion Data import Periodic Transfer of Data (/SAPDMC/SAP_LSMW_INTERFACE)

  35. What LSMW can do • organize the data migration project • project, subproject, object • document the data migration project • define data conversion per object • select target • business object (p.e. customer master, material master) • method (p.e. create, change) • import technique (p.e. batch-input, IDoc) • define source • structure of the source data (segments, fields, file attributes etc) • define relations • between source and target (SAP system) on record level and on field level • define rules • transfer of field contents

  36. What LSMW can do • read data (technical conversion) • convert data (conversion of values) • import data • with a standard import technique • batch-input • direct input • method for a business-object (“BAPI”) • IDoc technique • this means: • LSMW does not write data into the databases of the applications • precondition for the use of LSMW is the availability of a data transfer interface in the SAP application

  37. What LSMW can do • transport the data migration object • via download and upload • via SAP transport system • What LSMW cannot do • extract data from the legacy system • “outbound”: transfer data from SAP into another system

  38. Advantages and strengths at a glance: • Part of SAP and therefore platform-independent • Wide range of data conversion techniques (fixed values, translation, ABAP coding, etc.) • Migration customizing: no literals in rules • Conversion program generated from conversion rules • User guidance: data migration in 14~20 steps • Interface for data in spreadsheet format • Check against SAP Customizing before processing the import • Free of charge for SAP’s customers and partners

  39. Advantages and strengths at a glance: • Migrated data in SAP is consistent • user friendly • only basis ABAP knowledge necessary • in most cases only few programming has to be done • supports data transfer for the most important master and transaction data

  40. Examples of positive feedback: • “... Just wanted to let you know us here at ... We are very pleased with the LSM product. We are using it for most of our conversions and have found it to be of tremendous help and quality. ...” • “The LSM Workbench saved the day. Without it, we would never have been finished on time.” • “...in our opinion, the major benefit is LSM’s flexibility, which allows us to respond very quickly to changing requirements...”

  41. Examples of positive feedback: • “...within two and a half hours, we managed to generate our own migration object for the material master transfer, and successfully migrate the material masters from the EXCEL sheet. It was a complete success! ...” • “...the transfer of master data on June 12, and of the open items on June 19, 1998, meant that we could go live the same day.” • “...I used the LSMW to transfer customers and creditors, and I was really impressed by how fast and flexible it was! Fantastic! ...”

  42. Information Support Training LSMW

  43. Information • Main information medium: SAPNet • www.service.sap.com.de/LSMW • Download of • software (LSMW17.CAR) and further material • installation guide • quick guide (“HowToGuide”) • contact • e-mail: lsm@sap.com • Support • Online-Service-System: component XX-LSM

  44. Training • upon request • part of the data migration training BC420 in release 4.6 • self-study via examples in SAPNET

  45. Beyond LSMW

  46. New DX-Workbench (Release 4.6) • Organize your data migration projects • Generate test data • Use LSMW (or third-party tool) as mapping engine • Fast data load via BAPIs • Handle import errors (restart etc.)

  47. Release 4.6 • New-DX Workbench and LSMW • Release 5.0 • Unified solution for alldata migration issues

  48. Legacy System Migration Workbench lsm@sap.com

More Related