Coose Method

[Former Member]

Hi

When to Choose Session Method

Call TC method

Direct Input method

LSMW

[Former Member]

hi

chk the link:

http://www.saptechies.com/difference-between-lsmw-and-bdc/

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

With all the luck,

pritam.

[Former Member]

Hi,

Check this link, you will get Detaild Description about all the methods of data tranfer-

http://aspalliance.com/1130_Batch_Data_Communication_BDC_in_SAP_R3.3

http://moryhanry.com/sapbdcmethod.html

Regards,

Sujit

[Former Member]

Hii!

Check out these links

http://moryhanry.com/sapbdcmethod.html

http://www.saptechies.com/difference-between-lsmw-and-bdc/

Regards

Abhijeet

[Former Member]

Hi

Good

Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is

not bi-directional.

BDC works on the principle of simulating user input for transactional screen, via an ABAP program.

Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.

In ‘Call Transaction’, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in

Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.

Batch Input (BI) programs still use the classical BDC approach but doesn’t require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file.

Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.

Thanks

mrutyun^

[Former Member]

Hi Vijaya,

Session Method is used when there is large amount of data to be processed. Here we can create a session and run it any time. Session Method is also used when we are dealing with transactions which are dependable, ie., after the completion of one transaction processing other transaction processing is done.

Call transaction is used for lesser amount of data when compared to session method. Here the processing is done along with the execution of the program.

Direct Input Method is nothing but a set of programs that are used to upload the data into the system and here all the required validations are done bye the system itself.

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.

Hope this helps you.

Regards,

Chandra Sekhar

[former_member787646]

Hi

Session Method is used to upload large amount of data into SAP system.

Call Transaction Method is used to upload small amount of data into SAP system.

Hope this would help you.

Murthy