Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 


Former Member
0 Kudos


What are the advantages of LSMW over BDC?




Former Member
0 Kudos

Hi Anu,

1. lsmw - no programming requried,

whereas in call transaction & bdc session,

programming required.

2. in call transaction,

no session concept

(data is updated AS SOON AS we run the prgoram)

where as in lsmw, and session,

SESSION is generated (in both cases)

Only after when we run this session,

does the data get updated.

3. In call transactin program,

we have to handle error list and take action.

whereas in lsmw, & session,

(since session is run)

flexibility is there to check and control errors.


amit m.

Former Member
0 Kudos

LSMW is More of GUI. Not much of coding is required as in BDC.

0 Kudos

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

more details...

Active Contributor
0 Kudos


In LSMW no coding/less coding is required for data transfer.

Batch input session/call transaction is completely based on coding only.

Above all the major difference is LSMW is not suited for frequent data transfer whereas Batch input techniques are well suited...


Abdul Hakim

Former Member
0 Kudos


Check the following:-

Diff. between LSMW and BDC???



Former Member
0 Kudos

Hai Anu Raadha

Go through the following Document




What is BDC or batch input

The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.

BDC functions:

· BDC_OPEN_GROUP : Opens a session group

· BDC_CLOSE_GROUP : Closes a session

· BDC_INSERT : Insert a BDC scenario in the session

· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.

It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.

The object itself is maintanable through the transaction SE24.

BDC methods:





Opens a session

SUBRC (Return Code – 0 OK)

SESSIONNAME (Session to be created)


Closes a session



Resets the BDC Internal Table...

None. Normally, for internal purpose…


Handles a new screen

PROGNAME (Name of the program)

DYNPRONR (Screen Number)


Puts a value on the screen

FIELDNAME (Name of the field)

FIELDVALUE (Value to be passed)


Constructor - Initializes NO_DATA

NODATA (No data character). The constructor is called automatically when the object is created.


Launches a session with RSBDCBTC



Calls a transaction with the current BDC Data

MODE (Display Mode)

UPDATE (Update Mode)

TCODE (Transaction to be called)


Inserts the BDC scenario in the session

TCODE (Transaction to be called)

BDC techniques used in programs:

1) Building a BDC table and calling a transaction,

2) Building a session and a set of BDC scenarios and keeping the session available in SM35,

3) Building a session and lauching the transaction right after closing the session.



BDC using Call Transaction

BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP

program. The process involves building an Internal BDC table containing the screen information needed to

execute the required transaction and then passing this to the Call transaction command (See code example).

The full procedure for creating a BDC program is as follows:



What is the difference between batch input and call transaction in BDC?

Session method.

1) synchronous processing.

2) can tranfer large amount of data.

3) processing is slower.

4) error log is created

5) data is not updated until session is processed.

Call transaction.

1) asynchronous processing

2) can transfer small amount of data

3) processing is faster.

4) errors need to be handled explicitly

5) data is updated automatically






A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.


The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.

The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.

The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.

LSMW vs DX Workbench

The LSM Workbench covers the following steps:

Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).

Convert the data from source format to target format.

Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).

Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.

SAP provides this tool along with documentation to customers and partners free of charge.

Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).


Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available

Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.

Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available

Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.

Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10

Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !

Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20

Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.

Thanks & regards

Sreenivasulu P