Question

[Former Member]

Hi,

What is the main differences beween BDC,LSMW and BAPI.

Thanks in advance

Rgds

venugopal

[Former Member]

check below...

BDC....

https://wiki.sdn.sap.com/wiki/display/HOME/DataTransfers-LSMW,ALE,+BDC

LSMW....

http://sap.niraj.tripod.com/id61.html

www.erpgenie.com/sap/saptech/lsmw.htm

[Former Member]

Hi

BDC- This is used to create data based on the Screens of the transaction and is used for Custom Screens mainly where there are no standard processes available

Not that suitable for large uploads of data

BAPI - Standard FM for a particular Business process. Will handle most of the standard developments and in most cases will also handle the custom developments as well. Good for large uploads

LSMW - Standard SAP tool for uploading of legacy data . Uses Batch /Direct Input Method to upload the data. Best suited for large amount of data. Also can use recording method for Custom developments.

[Former Member]

Hi,

To answer your question in short.

BDC - is a technique used to load data in bulk into the system

LSMW : is a data migration tool which is using the BDC or idoc technique to load data

BAPI : are a set of interfaces in ABAP which can be remotely called by another third party software, thus integrated the transactional data from two different applicaitons

Hope this helps

Please reward points if this satisfies you

[Former Member]

Hai Venu Gopal

BDC to BAPI as follows

The steps to be followed are :

1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).

[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]

2. Create a Z program and call the BAPi (same as a Funtion module call).

2. Now, if you see this BAPi, it has

-> Importing structures.

eg: SALESDOCUMENT: this will take the Sales order header data as input.

-> Tables parameters:

eg: ORDER_ITEM_IN: this will take the line item data as input.

Note :

Only specify fields that should be changed

Select these fields by entering an X in the checkboxes

Enter a U in the UPDATEFLAG field

Always specify key fields when changing the data, including in the checkboxes

The configuration is an exception here. If this needs to be changed, you need to complete it again fully.

Maintain quantities and dates in the schedule line data

Possible UPDATEFLAGS:

U = change

D = delete

I = add

Example

1. Delete the whole order

2. Delete order items

3. Change the order

4. Change the configuration

Notes

1. Minimum entry:

You must enter the order number in the SALESDOCUMENT structure.

You must always enter key fields for changes.

You must always specify the update indicator in the ORDER_HEADER_INX.

2. Commit control:

The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

For further details... refer to the Function Module documentation for the BAPi.

LSMW over BDC

Go through the following Document

BDC SESSION

CALL TRANSACTION

CALL DIALOG

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:

E BDC_OPEN_GROUP : Opens a session group

E BDC_CLOSE_GROUP : Closes a session

E BDC_INSERT : Insert a BDC scenario in the session

E 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:

Method

Description

Parameters

OPEN_SESSION

Opens a session

SUBRC (Return Code ? 0 OK)

SESSIONNAME (Session to be created)

CLOSE_SESSION

Closes a session

None

RESET_BDCDATA

Resets the BDC Internal Table...

None. Normally, for internal purposec

BDC_DYNPRO

Handles a new screen

PROGNAME (Name of the program)

DYNPRONR (Screen Number)

BDC_FIELD

Puts a value on the screen

FIELDNAME (Name of the field)

FIELDVALUE (Value to be passed)

CONSTRUCTOR

Constructor - Initializes NO_DATA

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

RUN_SESSION

Launches a session with RSBDCBTC

None

CALL_TRANSACTION

Calls a transaction with the current BDC Data

MODE (Display Mode)

UPDATE (Update Mode)

TCODE (Transaction to be called)

BDC_INSERT

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

-

---

BATINPUT/DIRECT INPUT

-

---

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.

GO THROUGH THIS LINK

http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm

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

Releases:

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.

Regards

Sreeni