Welcome, Guest Login Register

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Added by Tarun Gambhir, last edited by Tarun Gambhir on Jan 08, 2009

ABAP Development / Data Transfers - BAPI, BDC, ALE, LSMW, DX-WB / LSMW

Steps to create a simple LSMW using batch input recording

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 supports conversion of data of the legacy system in a convenient w ay. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.

Furthermore, the LSM Workbench provides a recording function that allow s to generate a "data migration object" in an entry or change transaction

To start w orking w ith the LSM Workbench, use transaction LSMW:

Click on the execute button once the project, subproject and the object are created.

Click Back.Now record usingBatch Input RecordingData Migration - Step by Stepvia

Batch Input Recording

Step 1: Maintain Object attributes

In this example, you will be updating the Material master records with the help of

recording a transaction (MM01). Choose radio buttonBatch Input Recordingand click

on the recording overview icon to record the R/3 transaction. Enter

theRecordingname asMM01_REC2, the description asMM01 Recording method, and

the transaction code asMM01.

Click on the create button to create new project, subproject and the object. As show n below .

Project, Subproject and Object:

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

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

- Subproject: An ID w ith a maximum of 10 characters that is used as further structuring attribute.

- Object: An ID w ith a maximum of 10 characters to name the business object.

In the initial screen, All objects provides a list of all projects created already. My objects displays a list of all objects you created personally. All objects of the project

project as tree structure. Project documentation displays any documentation w ritten for the individual popups and processing steps. you can print the project documentation out, send it and save it in

various f ile formats.

Click on the execute button once the project, subproject and the object are created.

Click Back.Now record usingBatch Input RecordingData Migration - Step by Stepvia Batch Input Recording

Step 1: Maintain Object attributes

In this example, you w ill be updating the Material master records w ith the help of recording a transaction (MM01). Choose radio buttonBatch Input Recordingand click on the recording overview icon to

record the R/3 transaction. Enter theRecordingname asMM01_REC2, the description asMM01 Recording method, and the transaction code asMM01.

Click on create to record the transaction.

Click on Done.

Click on Done to actually start recording the transaction.

Enter the f ields required for recoding a transaction successfully.

Note that the f ields are populated w ith default values. The values you entered w hen you recorded the transaction are set by default.

*Double-click on the f ieldRMMG1-MATNRand enter the name asMATNRand the description asMATERIAL NUMBERand remove the default as show n below :

Repeat this step for all f ields.Similarly, double-click on all other f ields w ith default values and make appropriate changes. Once you have made changes, the recording overview screen looks as show n

below :

Click on SAVE to save the recording. The click on BACK icon to the main screen. Save the w hile going back to the main screen.

After completing the recoding the system w ill automatically take you to the second step as show n below :

Step 2. Maintain Source Structures

Click on CREATE to create a source structure. Give a name and a description to the source structure as show n below :

Save the source structure and go to the main screen.

Step 3. Maintain Source Fields

In this step, you need to list w hat f ields are present in the source structure. The easiest w ay is to click on 'Table Maintenance' icon to enter Fieldname, Type and Length for each f ield as show n:

Save w hile coming back to the main screen.

Step 4: Maintain Structure Relations

Execute a step to 'Maintain Structure Relations'. Since, there is only one Source and Target Structure, the relationship is defaulted automatically.

Save w hile coming back to the main screen.

Step 5: Maintain f ield mapping and conversion rules

Keep cursor on f ield 'MATNR' and click on 'Assign Source f ield' icon to choose source f ield MATERIAL from structure MM01V6 as show n

Similarly, assign 'Source Field' rules to the remaining f ields.

Once all the f ields are mapped, you should have an overview screen as show n

Save w hile coming back to the main screen.

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

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

Step 7: Specify files

In this step, w e define how the layout of the input f ile is. The input f ile is a [Tab] delimited w ith the f irst row as f ield names. It is present on my PC (local drive) as C:\MM3.txt.

Double Click on the legacy data.

Save w hile going to main screen.

Create an Excel w ith your data and save it as a Tab-delimited text f ile on your local drive (C and name it MM3.txt.

IMPORTANT

****The Structure of the f lat f ile should be proper otherw ise data w ill not be uploaded.. All the mandatory f ields should be present in the f lat f ile for the required transaction

Step 8: Assign f iles

Execute step 'Assign Files' and the system automatically defaults the f ilename to the source structure.

Save w hile going to main screen.

Step 9: Read data

In this step, LSMW reads the data from the source f ile (from your PC's local drive). You have the option to read only selected row s and convert data values to internal format.

Here 1 to 2 represents the number of row s to be read from the f lat f ile. If you don't specify any number the system w ill read all the row s from the f lat f ile. We have 2 row s in the f lat f ile hence from 1 to 2.

After w e execute the data read from the f lat f ile is as show n below .

Step 10: Display read data

This step is optional. If required, you can review the f ield contents for the row s of data read.

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 f ields are mapped to target f ields.

Click BACK to come back to main screen.

Step 12: Display Converted data

Again this is an optional step to view how the source data is converted to internal SAP format.

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.

Click EXECUTE button to execute a batch inout session.

Step 14: Run Batch Input Session

You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the

batch input session, the Material master records are updated in the system. You can confirm this by view ing the Material master records (MM03).

Select the session and click on the PROCESS icon.

You can Process the session in foreground or background or can only display errors.

Select the Processing Mode and then click on the PROCESS tab to executive the session.

After the session is completely processed you can confirm this by view ing the Material master records (MM03) or in the table MARA.

Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright