Direct Input vs call transaction & Session method

[Former Member]

Can anybody explain the differences between Direct Input Method , Call transaction and Session Method?

[Former Member]

Hi,

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

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

Thanks,

Reward If Helpful.

[Former Member]

Hi,

BDC- Batch Data Communication.

there are:

->Session method

->Call transaction

->Direct input

->Session method:

BDC_OPEN_GROUP

POPPULATE BDC DATA STRUCTURE

BDC_INSERT

BDC_CLOSE_GROUP

->Call Transaction Method:

POPPULATE BDC DATA STRUCTURE

CALL TRANSACTION

<b>reward points if useful.</b>

regards,

Vinod Samuel.

[varma_narayana]

Hi..

Direct input: in this method there is no Transaction call . data is updated thru some Function modules. Only used when there is a Standard program available. Used in LSMW.

Eg: RMDATIND for material Master

Both Session and Call transaction methods are called as Batch input. Here a transaction is called to update the data.

Session method:

1. Data migration is done in two steps .. Generate session and Process session.

So resouces can be used efficiently. good for bulkdata migration.

2. Session method generates error log when u process a session.

3. No SY-SUBRC can be returned after each transaction is called.

4. Provides synchronous Updation only...

Call transaction method:

1. Data migration is done in single steps ..bcoz Transactions are called immediately after filling BDCDATA table. So good for small amount of data.

2. We have to collect error messages using BDCMSGCOLL Table

3. Returns SY-SUBRC and Messages ..after each Call Transaction..very useful feature for further processing based on the Status and Messages..

4. Supports Asynch or Synch Updation.

<b>reward if Helpful.</b>

[Former Member]

The most important aspects of the session interface are:

Asynchronous processing

Transfer data for multiple transactions

Synchronous database update. During processing, no transaction is started until the previous transaction has been written to the database.

A batch input processing log is generated for each session

Sessions cannot be generated in parallel. The batch input program must not open a session until it has closed the preceding session.

The most important features of CALL TRANSACTION USING are:

Synchronous processing

Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called

You can update the database both synchronously and asynchronously. The program specifies the update type.

Separate LUW (Logical Units of Work) for the transaction. The system executes a database commit immediately before and after the CALL TRANSACTION USING statement.

No batch input processing log

call transaction doesnt have log file

user has to main tain that one manually

but not in case of session method it have log file by default

and also call transaction returns sy-subrc in session method it doesnt return

when ur uploading small amount of transactional data after uploading if this data is input for another transaction in this case u have to use call transaction