LSM Workbench

7/28/2019 LSM Workbench

1/17

Description:

LSMW- The tool supports conversion of data of the legacy system in a convenient way.The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.

In this wiki we will use the LSMW to Update Customer Master Records with TransactionRecording.

The LSM Workbench is an R/3-based tool that supports you when transferring data fromnon-SAP systems ("Legacy Systems") to R/3 once or periodically. The tool supportsconversion of data of the legacy system in a convenient way. The data can then beimported into the R/3 system via batch input, direct input, BAPIs or IDocs.

Furthermore, the LSM Workbench provides a recording function that allows generating adatamigration object in an entry or changing transaction.

Significance of Data Migration

Data migration comes in the end of R/3 implementation. At this time, the R/3 system isnormally installed and application customizing is finished (in the best case).

An examination of R/3 implementation projects by SAP Consulting has shown that datamigration is about 20% of the total implementation expenses. This portion may rise up to40% in smaller implementation projects.

A significant reduction of the expenses for data migration results in a correspondingsignificant reduction of the total project budget and the project runtime.

The first experiences with the LSM Workbench in R/3 implementation projects are very promising: Both the expenses and the costs of data migration could be reducedsignificantly.

The L SM Workbench was developed on the basis of the following principles:

*Most of the functions should reside in R/3. No collection of individual programs ondifferent platforms.

*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.


2/17

The main advantages of the LSM Workbench :

- Part of R/3 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 R/3.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 R/3 application)

Authorizations

Authorization level Profile Function

Disply B_LSMW_SHOW The user can display all projects and their work steps. He/she cannot switch to change mode.


3/17

Execute B_LSMW_EXEC The user can display data, and read, convert andimport data.

Change B_LSMW_CHG The user has "Execute" authorization, and canchange and copy objects.

All B_LSMW_ALLThe user can use all functions made available bythe tool.

The profiles listed above are not included in the profiles of the standard R/3 system.Therefore you have to add the required profiles to your user master record.

Step-by-Step Gui de for using L SM W

Project, Subproject and Object

On the initial screen, you can create a new project, corresponding subprojects and objectsvia Edit -->Create new entry .

~ Project : An ID with a maximum of 10 characters to name your data transfer project. If you want to transfer data from several legacy systems, you may create a project e.g. for every legacy system.

~ Subproject: An ID with a maximum of 10 characters that is used as further structuringattributes.

~ Object: An ID with a maximum of 10 characters to name the business object.

The main screen of LSMW provides wizard-like step-by-step tasks, as shown in theFigure below. To complete your data conversion, you need to execute these steps insequence. Once a step is executed, the cursor is automatically positioned to the next step.


4/17

Note that these steps may look different depending upon your Personal menu settings.You could make step numbers visible by 'Numbers on' icon or hidden by 'Numbers off'icon. You can execute a step by double-clicking on the row. Toggle icon 'Double-click=Display' or 'Double-click=Edit', makes the step in 'display' mode or 'change' mode.

Step 1: Maintain Object attributes

In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click onthe recording overview icon to record the R/3 transaction. Enter the Recording name asXD02_REC, the description as Customer Master Updates Recording, and the transactioncode as XD02.


5/17


6/17

The system calls the transaction code XD02 and prompts you to complete the ChangeCustomer transaction, as shown in Figure below. Enter the key customer information (Ientered customer number 1000, sales organization 1000, distribution channel 01, anddivision 00) and choose 'Sales' view within 'Sales area data'. Make changes to these threefields (I entered, sales office 1010, sales group 110, and customer group 01) and save thetransaction.

Once the transaction is completed, R/3 records the flow of screens and fields and saves


7/17

the information, as shown in Figure.

Note that the fields are populated with default values. The values you entered when yourecorded the transaction are set by default.

Note that if you have more fields in the recording than needed, you can remove them byclicking 'Remove Screen field' icon.

Observe that the transaction-recording process stores field names in a technical format.By pressing the F1 key on individual screen fields and then pressing the F9 key, thesystem displays technical names. You then can replace the technical names withdescriptive names. Double-click on the field RF02D-KUNNR and enter the name asKUNNR and the description as Customer Account Number and remove the default value.(See Figure)


8/17

Similarly, double-click on all other fields with default values and make appropriatechanges. Once you have made changes, the recording overview screen looks like what

you see in Figure


9/17

Save your changes. When you go back to the initial screen, you will see that the initialscreen steps have changed. Since you want to import data via the BDC method, theDirect Input and IDoc-related steps are hidden, as they are not relevant.

Step 2. Maintain Source Structures

Give a name and a description to the source structure ( Figure ).


10/17

Step 3. Maintain Source Fields

In this step, you need to list what fields are present in the source structure. The easiestway is to click on 'Table Maintenance' icon to enter Fieldname, Type and Length for eachfield as shown in Figure.

Note that your input file will have four fields as key fields and you need to update three fields in the system.

Step 4: Maintain Structure Relations


11/17

Execute a step to 'Maintain Structure Relations'. (See Figure) Since, there is only oneSource and Target Structure, the relationship is defaulted automatically.

Step 5: Maintain field mapping and conversion rules

Field RF02D-D0310 represents that you chose 'Sales view' for the customer Master

screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310and click on Constant rule icon to choose the constant value of 'X'.

If your source file already has the field value, you choose rule 'Source Field'.

Keep cursor on field 'KUNNR' and click on 'Assign Source field' icon to choose sourcefield CUSTOMER from structure XD02S as shown in Figure.


12/17

Similarly, assign 'Source Field' rules to the remaining fields.

Once all the fields are mapped, you should have an overview screen as shown in Figure.


13/17

Step 6: Maintain fixed values, translations, user-defined routines

You can also maintain re-usable translations and user-defined routines, which can beused across conversion tasks. In this case, that step is not required.

Step 7: Specify files

In this step, we define how the layout of the input file is. The input file is a [Tab]delimited with the first row as field names. It is present on my PC (local drive) asC:\XD02.txt. (See Figure)


14/17

Create an Excel file ( Figure ) with your data and save it as a Tab-delimited text file onyour local drive (C: ) and name it XD02.txt.


15/17

Step 8: Assign files

Execute step 'Assign Files' (Figure) and the system automatically defaults the filename tothe source structure.

Step 9: Read data

In this step, LSMW reads the data (Figure) from the source file (from your PC's localdrive). You have the option to read only selected rows and convert data values to internalformat.

Step 10: Display read data

This step (Figure) is optional. If required, you can review the field contents for the rowsof data read.


16/17

Step 11: Convert data

This is the step that actually converts the source data (in source format) to a target format.

Based on the conversion rules defined, source fields are mapped to target fields.

Step 12: Display Converted data

Again this is an optional step to view how the source data is converted to internal SAPformat

Step 13: Create batch input session

Once the source data is converted in an internal format, you can create a batch session to process updates


17/17

Step 14: Run Batch Input Session

You can execute the BDC session by Run Batch input session. Executing a batch inputsession is a standard SM35 transaction for managing BDC sessions. Once you havesuccessfully executed the batch input session, the customer master records are updated inthe system. You can confirm this by viewing the customer master records (XD03).