Mallikarjuna G November 16, 2010



The LSMW is an R/3-based tool that supports us when transferring data from non-SAP systems (Legacy Systems) to SAP systems once or periodically. It is a cross-platform component of the SAP system. The Main functions of the LSMW are«


Import data from a legacy system ( legacy data in spreadsheet tables and/or sequential files). Converting data from its original (legacy system) format to the target (SAP) format Importing the data using the standard interfaces of SAP (IDoc inbound processing, batch input, direct input)



invoices. vendors.Legacy System Migration Significance of Data Migration orkbenc Managing large amounts of data can be a significant challenge to most organizations. e. ‡ Data maintenance.. e.. loading legacy systems data into SAP applications during initial SAP implementation or M&A activity (mergers and acquisitions ). mass changes to SAP data for price changes and payroll changes ‡ Data integration. or transactional data (journal vouchers. e. loading vendor invoices or bank statements into SAP applications ‡ Mass data creation. etc) in SAP systems. creating new master data (materials.g. customers.).g. Some of the common data management tasks include: ‡Data migration. etc..g.. e. .g.

Legacy System Migration Principles of t e LSM orkbenc orkbenc The quality and consistence of the data imported into R/3 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.

you should better assign a fixed value or establish an optional field for data transfer.Legacy System Migration ‡ Make sure that SAP customizing is finished. In the case of a very large data volume. ‡ If only a part of your legacy system will be replaced by SAP. orkbenc tool Some of t e Important Tips. In such a case. before applying t e LSM ‡ Determine the data contained in your legacy system and which of the data will be required in the future (with respect to business operation). ‡ In which form is the legacy data available? Determine accordingly which of the LSMW functions will be applied. determine which function will be provided by the SAP system and which by the legacy system. . ‡ Decide whether it makes sense to use this tool with respect to the data volume to be transferred. ‡ ‡ In which way will the data be extracted from the non-SAP system? Note: The LSMW does not extract data. There may be required fields that do not correspond to data fields in the legacy system. ‡ Run the relevant transaction in the SAP system manually with test data from the legacy system and see which fields must be filled. batch input or IDoc techniques may cause extremely long runtimes. It may be easier to transfer very small data volumes into the SAP system manually.

depends on t e business object as well as on t e availability of standard input programs ‡ Data consistency due to standard import tec niques: Batc input Direct input BAPIs (Business Application Programming Interfaces) IDocs (Intermediate Documents) ‡ Structured way of working. ‡ Mapping is done by SAP itself. orkbenc is basically designed for a functional consultant w o do not do muc coding ‡ T e import tec nique to be used in an individual case.Legacy System Migration Features of LSM ‡LSM . . because you ave to finis every step before starting t e next step ‡ LSM is possible for only Standard transaction codes. ‡ LSM input file is always TEXT file.

BAPI's : When the Data has to be distribute whith in the R/3. The user has to format the data using predefined structures and store it in a flat file. The difference is. ALE/IDOC : When the data has to be distribute with external system non-SAP or third party package. instead of processing screens they validate fields and directly load the data into tables using standard function modules. but doesn't required an ABAP program to be written to format the BDC DATA. Yet it is a slower updation method. Direct Input: Works similar to Batch Input programs. Much faster and suits for large volume of data.Legacy System Migration Brief Description of Uploading met ods orkbenc Batch Input: Uses classical BDC approach. .

Legacy System Migration orkbenc Accelerating Data Migration: LSM Workbench Grap ical representation How LSM Workbench works One or several files Legacy dat a on PC Read data Structure relations Field mapping Read data Legacy data on appl icati on server Convert data R/3 Standard Conversion rules Converted data Batch Input processing Direct Input processing IDoc inbound processing ¥ SA P AG J ul y 1 99 9 21 .

make sure that you are working in change mode.Legacy System Migration Getting Started orkbenc Here is an example showing the way to use the conversion tool LSMW in SAP. To activate this mode. Only this mode provides all functions required for changing objects . click Change in the corresponding processing step. It starts in the start-up screen of LSMW transaction and ends with a screen on which the results of the conversion are displayed If you want to create or change objects.

Legacy System Migration Step 1 .Enter transaction LSMW orkbenc .

corresponding subprojects and objects via Edit -> Create new entry.g. for every legacy system ‡ Subproject: An ID wit a maximum of 10 c aracters t at is used as furt er structuring attribute ‡ Object: An ID wit a maximum of 10 c aracters to name t e business object . subproject. you can create a new project. If you want to transfer data from several legacy systems.Legacy System Migration Step 2 ± project. objects orkbenc At t e initial screen. you may create a project e. Alternatively you can select from an existing project ‡ Project: An ID wit a maximum of 10 c aracters to name your data transfer project.

Legacy System Migration Next Step : Execute orkbenc Once the project and subproject along with the object are determined we execute to find the list of steps to be performed for data transfer .

Legacy System Migration Process Steps orkbenc ‡ The number of process steps is dynamic and shall depend on factors like input method ‡ By clicking the µUser menu¶ button one can select ± deselect the Process steps ‡ To proceed through the processing steps one needs to start from the first one and execute each of them ‡ A step can be skipped by selecting the next available processing steps¶ radio button .

Legacy System Migration Step 1: Maintain object attributes Choose if the data transfer is once or periodic orkbenc C oose met od for input of data.               . In t e met od to input data from a BAPI. one needs to select t e Business Object and t e corresponding met od.

Legacy System Migration Step 2: Maintain Source Structures orkbenc Give a name and a description to the source structure (Nothing but giving an Internal table name & description) Source Structure .

T e easiest way is to click on ¶Table Maintenance· icon to enter Fieldname. you need to list w at fields are present in t e source structure. Type and Lengt for eac field .Legacy System Migration Step 3: Maintain Source Fields orkbenc In t is step.

.Legacy System Migration Step 4: Maintain Structure Relations orkbenc Execute a step to ¶Maintain Structure Relations·. t e relations ip is defaulted automatically. t ere is only one Source and Target Structure. (See below Figure ) Since.

t en click on ¶Source Field· and select t e field. Ot erwise click on Rule Select t e Radio Button ¶Constant· and provide t e Constant value . Like as ¶0004·. Eg. .Legacy System Migration orkbenc Step 5: Maintain field mapping and conversion rules Select t e Field (if t e field is coming from Internal table.

In t is step. w ic can be used across conversion tasks. user-defined routines. You can also maintain re-usable translations and user-defined routines. In t is case. Step 7: Specify Files. we define ow t e layout of t e input file is.Legacy System Migration orkbenc Step 6: Maintain fixed values. translations. It is present on my PC (local drive) as C:\XD02. T e input file is a [Tab] delimited wit t e first row as field names. (Note: Just Execute->Click on c ange mode ->Save -> come back) . t at step is not required.txt.

LSM reads t e data from t e source file (from your PC·s local drive).Legacy System Migration Step 8: Assign File orkbenc Execute step ¶Assign Files· and t e system automatically defaults t e filename to t e source structure (Note: Just Execute->Execute->back -> back) Step 9: Read Data In t is step. You ave t e option to read only selected rows and convert data values to Internal format. (Note: Just Execute->Execute->Back ->Back) Step 10: Display Read Data T is step is optional. you can review t e field contents for t e rows of data read (Note: Just Execute->Execute->Back ) . If required.

You can confirm t is by viewing t e customer master records (XD03) .Legacy System Migration Step 11: Convert Data orkbenc T is is t e step t at actually converts t e source data (in source format) to a target format. Based on t e conversion rules defined. Once you ave successfully executed t e batc input session. you can create a batc session to process updates (Note: Just Execute->Execute-) Step 14: Run batch input session You can execute t e BDC session by Run Batc input session. Executing a batc input session is a standard SM35 transaction for managing BDC sessions. t e customer master records are updated in t e system. (Note: Just Execute->Execute->back -> back) Step 12: Display Converted Data Again t is is an optional step to view ow t e source data is converted to internal SAP (Note: Just Execute->Execute->Back ) Step 13: Create batch input session Once t e source data is converted in an internal format. source fields are mapped to target fields.

End _ of_ Processing. Global Data Begin _ of _ Processing. 3. End _ of_ Transaction. orkbenc .Legacy System Migration Events in LSMW 1. 4. 2. Begin _ of _ Transaction. 5.

w ic is triggered after completion of Eac and Every record in t e Flat file. End _ Of_ Transaction End_ of _ transaction is an Event. w ic is triggered at Eac record of Flat file. w ic we need to implement t e logic. w ic is triggered after completion of Entire flat file processing. Begin _ Of_ Processing Begin _ of _ processing is an Event. End _ Of_ Processing End_ of _ processing is an Event.Legacy System Migration Global Data orkbenc Global Data is used to Declare t e variables. Begin _ Of_ Transaction Begin _ of _ transaction is an Event. . w ic is triggered at t e time of Processing of an Entire Flat File. work area and Internal tables.

Legacy System Migration Begin _ of _ Processing Begin _ of _ Transaction orkbenc 123 321 456 654 789 987 741 ATP CHI ATP AMP ATP KUR HYD End _ of _ Transaction End _ of _ Processing X54321 X54322 X54323 X54324 X54321 X54322 X54323 MALLIK MK VENKAT VK Shiksha SS PRAVEEN PV SAILEELA SL MADHURI MD ANUSHA AR .


Sign up to vote on this title
UsefulNot useful