Advertisement

The LSMW ( Legacy System Migration Workbench ) is an R/3-based tool that supports us when transferring data from non-SAP systems (Legacy Systems) to SAP systems once or periodically. The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the SAP system via batch input, direct input, BAPIs or IDocs. Furthermore, the LSM Workbench provides a recording function that allows generating a “data migration object” in an entry or changing transaction.

Significance of Data Migration

Data migration comes in the end of SAP implementation. At this time, the SAP system is normally installed and application customizing is finished (in the best case). An examination of SAP implementation projects by SAP Consulting has shown that data migration is about 20% of the total implementation expenses. This portion may rise up to 40% in smaller implementation projects. A significant reduction of the expenses for data migration results in a corresponding significant reduction of the total project budget and the project runtime. The first experiences with the LSM Workbench in SAP implementation projects are very promising: Both the expenses and the costs of data migration could be reduced significantly.

Basic Principles of the LSM Workbench

The LSM Workbench was developed on the basis of the following principles:

  • Most of the functions should reside in the SAP system. No collection of individual programs on different platforms.
  • The quality and consistence of the data imported into the SAP system should be more important than speed and performance of data migration.
  • Existing knowledge and coding should be used.
  • The developed “mapping” and rules should be reusable and thus be used repeatedly in projects.

On this basis, a concept was developed that is represented in the following chart:

SAP LSMW FLow Data Introduction to LSMW

SAP LSMW Flow Data

Advantages of the SAP LSMW

The main advantages of the LSM Workbench:

  • Part of the SAP system and thus independent of individual platforms
  • A variety of technical possibilities of data conversion
  • Data consistency due to standard import techniques
  • Batch input
  • Direct input
  • BAPIs (Business Application Programming Interfaces)
  • IDocs (Intermediate Documents)
  • The import technique to be used in an individual case depends on the business object
  • Generation of the conversion program on the basis of defined rules
  • Clear interactive process guide
  • Interface for data in spreadsheet format
  • Creation of data migration objects on the basis of recorded transactions
  • Charge-free for SAP customers and SAP partners

Preconditions

The LSM Workbench is a tool that supports data transfer from non-SAP systems to SAP systems. The main functions of the LSM Workbench are:

  1. Import data (legacy data in spreadsheet tables and/or sequential files)
  2. Convert data (from source format to target format)
  3. Import data (into the database of the SAP application)

Before we can apply the LSM Workbench, we absolutely need a data migration concept. The following items should be considered in particular:

  • Make sure that SAP customizing is finished.
  • Determine the data contained in our legacy system and which of the data will be required in the future (with respect to business operation).
  • Decide whether it makes sense to use this tool with respect to the data volume to be transferred. It may be easier to transfer very small data volumes into the SAP system manually. In the case of a very large data volume, batch input or IDoc techniques may cause extremely long runtimes. A rough landmark for estimating the required time: 10 000 records per hour where this value may vary considerably depending on the hardware available.
  • Identify the transaction(s) in the SAP system via which we want to import the data into our SAP system. It may be relevant whether we need the data for statistical analysis or for further processing in the system.
  • Run the relevant transaction in the SAP system manually with test data from the legacy system and see which fields must be filled. There may be required fields that do not correspond to data fields in the legacy system. In such a case, we should better assign a fixed value or establish an optional field for data transfer.
  • Map the fields in advance in written form: Assign the source fields to the target fields.
  • Determine the form in which non-SAP data will be transferred into the SAP system (e.g. via “Move” or according to a rule).
  • If applicable, define the translation rules.
  • In which way will the data be extracted from the non-SAP system?
  • In which form is the legacy data available? Determine accordingly which of the LSMW functions will be applied.
  • If only a part of our legacy system will be replaced by SAP, determine which function will be provided by the SAP system and which by the legacy system. If applicable, set up a concept of data flows and interface architecture.

Above are the quick introductions about migration tool of Non-SAP Systems to SAP-Systems, known as SAP LSMW. Next post I will try to explain Step-by-Step Guide using LSMW

Tags: * * * *

Filed under: General

Like this post? Subscribe to my RSS feed and get loads more!