LSMW

[Former Member]

HI.

Pls tell me what is use of LSMW? why we need to prefer LSMW.

How can find whether all records are updated successfully or not?

regards.

jay

[Former Member]

HI.

Pls tell me what is use of LSMW? why we need to prefer LSMW.

How can find whether all records are updated successfully or not?

regards.

jay

[Former Member]

hi,

No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.

The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.

More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.

The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.

So although it was designed for uploading of legacy data it is not restricted to this use.

We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.

The SAP transaction code is 'LSMW' for SAP version 4.6x.

For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.

You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.

If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw

The LSM Workbench carries out the following tasks:

Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)

Converts the data from the source format into the target format

Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working online.

Execute the transaction LSMW to start transfer of data,Before using the LSMW we should have good knowledge about the business object and the fields that will be transferred.

There are 14 steps that are normally used and these are :

1) Maintain Object Attributes.

2) Maintain Source Structures.

3) Maintain Source Fields.

4) Maintain Structure Relations

5) Maintain Field Mapping and conversion rules .

6) Maintain Fixed Values,translations ,user defined routines.

7) Specify Files .

😎 Assign Files .

9) Read DATA.

10) Display Read Data.

11) Convert Data.

12) Display Converted Data.

13) Create Batch Input Session.

14) Run Batch Input Sesion.

Hope this helps, Do reward.

Edited by: Runal Singh on Feb 15, 2008 4:57 PM

[Former Member]

Difference between BDC & LSMW

LSMW offers different technique for migrating data: Direct input, BAPI, Idoc, Batch input recording. While BDC basically uses batch input sessions and CALL TRANSACTION method.

Limit on number of records which can be uploaded in one session of BDC (999 records). No such limit in LSMW.

LSMW is more to do with configuration while BDC involves programming.

LSMW

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:

- Import data (legacy data in spreadsheet tables and/or sequential files)

- Convert data (from source format to target format)

- Import data (into the database of the R/3 application)

Principles of LSM Workbench

Basic Principles of LSM workbench:-

Most of the functions should reside in R/3. No collection of individual programs on different 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.

Features:-

Integrated in R/3 and thus independent of individual platforms

The import technique to be used in an individual case, depends on the business object as well as on the availability of standard input programs

Data consistency due to standard import techniques:

Batch input

Direct input

BAPIs (Business Application Programming Interfaces)

IDocs (Intermediate Documents)

Structured way of working, because you have to finish every step before starting the next step

Pre-requisites for LSMW

Make sure that SAP customizing is finished.

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, one 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).

Preferred methods of input are described in order of preference:

IDOC’s

Advantages: Fast to load, easy processing, low programming for standard IDOC’s

Disadvantages: Good knowledge of IDOC processing required, time consuming if changes have to be made to a created IDOC

2. BAPI’s

Advantages: Fast to load, easy processing, logical interface for functional/end user based on the business processes involved.

Disadvantages: Not always complete with all input fields of a transaction

3. Standard/Direct Input

Advantages: Well tested method, Fast to load, easy processing.

Disadvantages: No enjoy transactions, not always complete with all input fields of a transaction.

4. Batch Input

Advantages: Easy modifiable, all fields are available, easy re-processing.

Disadvantages: Comparatively slow, to use new screens or tabs a new recording has to be created, not easily usable for enjoy transactions, dependant on user settings, difference in foreground and background processing may occur.

Regards.

[Former Member]

Legacy System Migration Workbench(LSMW) is a tool for Uploading the Data into SAP.

Go through the links:

http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html

http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt

http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip

http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt

http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt

http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf

LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC .

Advantages:

1 no need to write large code .almost 60% logic is provided by the tool only.

2 LSMW mapping is done by SAP

3 we can transfer data using session ,direct Input BAPI and IDOC

4.used for single time data transfer

5.It is mostly used for standard transaction codes and predefined objects.

Disadvantage :

only used for single data transfer.

only used for large amount of data.

BDC:

Advantages:

1 used for small as well as large amount of data.

2 we can transfer data for customized applications as well as predefined applications

3 we can transfer data through Recording with Session,Call transaction and Direct Input method.

4 We can check errors in sm35 in case of session method

Disadvantages:

doesn't support enhancements.

we have to provide explicit mapping.

BDC is the way to transfer data by writing a batch input program which can use either session or call transaction method.

LSMW used to transfer data without/less code.

What type of data we transfer using LSMW?

LSMW is best suited for transferring master data.

Actually BDC and LSMW are not comparable at all.

for example LSMW itself can use BDC as a way of mass data transfer.

BDC is a mass data transfer technique via screen logic of existing SAP Data entry transactions. It behaves as if you are manually making thousand of entires into sap system as a background job. And that is probably the reason why BAPI's are preffered over BDC's.

On the other hand LSMW is a tool to facilitate DATA migration from other legacy systems ... It contains step by step procedure for data migration.

Like Managing Data Migration Projects , Creating Source Structures , Mapping Source structures wid Target structures , etc etc

LSMW internally might well be using the following techniqes for data transfer..

1. IDOX

2. Direct Input / BDC

4. BAPI's

LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :

LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.

LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.

LSMW mapping is done by SAP while in BDC we have to do it explicitly .

LSMW is basically for standard SAP application while bdc basically for customized application.

Coding can be done flexibly in BDC when compared to LSMW

"The Data Transfer Workbench (or DX Workbench, transaction SXDA) is an integrated SAP tool that supports data transfer and analysis. It

does not have the built-in features for mapping for source structures to target structures, but it will allow you to integrate Legacy System Migration Workbench (LSMW) objects as processing tasks within a run definition. The DX workbench has many features for creating

test data and performing data migrations - for example, logging of data migration runs.

However, if you need to map or convert data, you should use the LSMW. Or, you can integrate

your LSMW objects as task within a more user-friendly data migration run, in which the LSMW

project steps "Read data", "Convert data," and "Start IDoc processing" are automated

and use the features of both tools. If you donot need logging and automated data migration

runs, you can perform your data migration without the DX Workbench."

LSMW is having different different options and as in BDC we have to code

a program but i suppose the main difference in both the cases is:-

LSMW has been developed mainly for the Functional people who has no

knowledge of the technical aspects of report or BDC in ABAP because its very user friendly and handy to use.

So, simply they can upload the master records using LSMW.

Earlier they had to contact to a ABAP person and ask him to create a BDC taking extra time and efforts.

we use BDC for custom applications.we use LSMW for standard applications and tcodes.

BDc is technique provided by SAP to upload data from legacy to r/3. where as LSMW is a toll to upload data.

In BDC we have to write coding but in LSMW no need to wrtie logic.

LSMW is used only for single time uploading where as we can use BDC pg as many times we want

Refer this

For BDC:

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

Check these link:

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://www.sap-img.com/abap/question-about-bdc-program.htm

http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/

http://www.planetsap.com/bdc_main_page.htm

http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html

http://www.saptechnical.com/InterviewQ/interviewQ.htm

http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm

i think it is usefull for

Reward is usefull

[Former Member]

Hi.

How can check whether all records are updated or not in LSMW?

Jay

[ThomasZloch]

LSMW does not do the update itself. A specific program (or BAPI or method or IDoc or BDC session) called by the LSMW will do it.

Depending on that program (or...) the resulting messages (or protocol or log) will let you know whether everything has been updated or whether there were errors.

Cheers

Thomas