Difference between CALL TRANSACTION and SESSION Method

Difference between CALL TRANSACTION and SESSION Method


Call Transaction method
Classical or session method
In this method, the ABAP/4 program uses the call transaction <T-code > using <bdc_tab> mode <mode> update <update >  method.
In 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 
In ‘Call Transaction’, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
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.
Synchronous Processing
Asynchronous Processing 
We can update the database both synchronously and asynchronously. We can specify the mode in the program.
 
Synchronous Database update.
During processing, no transaction is started until the previous transaction has been written to the database.
No batch input processing log
 
Detailed Log will be generated for all the sessions
While execution it starts from the first.
 
While executing it wont start from the first. It will start from the place where it ends with error.
Faster than session method
Not as fast as call transaction method

Comments

Popular posts from this blog

Static and Instance - ABAP OO

Module Pool- Chain & Endchain

Module Pool - Event