Session Method and Call Transaction Method

[Former Member]

Hi Abapers,

While transferring the data from NON-SAP to SAP using BDC, we can use CALL TRANSACTION or SESSION METHOD.

My ques is:

1) What are the main difference between these two methods.

2)In which scenarioes, we decide that we should go for CALL TRANSACTION method or SESSION METHOD.

With Regards,

Rupinder

[Former Member]

Generally.. if we want to update the data online, we will go for Call transaction.

If we want to update the data at scheduled time we will go for Session method.

Thanks,

Rajinikanth

[Former Member]

Hi,

We use the call transaction method to upload the data automatically and generate a report for the errors, where as when we use session method the documents will not be created automatically and they will be created only when that session is processed.

For call transaction method you need to handle the errors explicitly, where as in the session the system itself will take care of the errors.

When we have huge volume of data to be transferred in that case we use the session method, otherwise we can go ahead and use the call transaction method.

Thanks,

Mahesh.

[venkatasriram_mygapula]

Hi,

call transaction method is faster than session method.

if your flat file has small amount of data you can go for call transaction method.

if it is uge amount of data you can go for session method.

in calc transaction method you have to create internal table for error records.

in session method if there are any error records when you are updating into the database table error records moves to error log in session(sm35).

in call transaction we can use one application at a time.

in session method we can run two or more applications at a time.

regards.

sriram.

[Former Member]

Hi kaur,

Call Transaction method:

In this method, the ABAP/4 program uses the call transaction <T-code > using <bdc_tab> mode <mode> update <update > method.

In u2018Call Transactionu2019, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.

Synchronous Processing

We can update the database both synchronously and asynchronously. We can specify the mode in the program.

No batch input processing log

While execution it starts from the first.

Faster than session method

Classical or session method

n this method, ABAP/4 program read the external data that is to be entered to the SAP system and stores the data in the batch input session.

When the prgm has finished creating the session, we can run the session thro the TC SM35. This method involves FM like BDC_OPEN,BDC_INSERT,BDC_CLOSE

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.

Asynchronous Processing

Synchronous Database update.

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

Detailed Log will be generated for all the sessions

While executing it wont start from the first. It will start from the place where it ends with error.

While executing it wont start from the first. It will start from the place where it ends with error.

If Found Help Full Do Reward.

Regards.

Eshwar.

[Former Member]

Hi rupinder kaur,

BATCH INPUT SESSION is an intermediate step between internal table and database table. Data along with the action is stored in session ie data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.

in call transaction we cannot code multiple transactions.

we can code only one transaction at a time.

the main difference is for immidiate update of database we use call trasaction method while the session method will be processed in the background at off peak times

call transaction-synronous processing

session-asyncronous processing,syncronous update

Session and Call Transactions are the methods in BDC Programming.

Session Method works in Background and as well as in Foreground. Where as Call Transaction Method Works in Foreground. (Note: No Display Mode is equal to Background Processing in call transaction method).

Session Method can handle Multiple Applications at a time. Where as Call Transaction Method can handle only one Application.

Session Method holds Log File by Default. Where as in Call Transaction Method no Log File by Default. We have to design Log File by using BDCMSGCOLL.

Session Method Updates the Database Synchronously. Call Transaction Method Updates the Database Asynchronously. (Note: Asynchronous updation is Faster than Synchronous

thanks

karthik