online

[Former Member]

y is call transaction is called online? and y session is called offline?

thanks & regards

[Former Member]

Hi Vicky,

Call Transaction is used called online and Session Method is called offline for the following reasons:

If you have huge amount of data in file ,then go for session method,

If you have run time validation ,then go for Call transaction

In general, Session method is slow but consistent and used for huge data upload.

Call transction method is fast but will not perform as consitant as session method for huge data upload.

Also see few differences as follows:

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

Session method is to populate the data by filling BDC structure and keep as session to process from SM37 to post in appropriate Transaction.

Call transaction method is to post the data directly into the Transaction from an Executable program.

Session method SAP defined Function modules. in session method, no sy-subrc is returned due to the basic characteristic of session method. 'Call transaction' always returns Sy-subrc.

The most important aspects of the batch session interface are: -

Asynchronous processing - Transfers 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 most important aspects of the CALL TRANSACTION USING interface are: -

Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.

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

session displays output in a different page but call transaction opens in a same page..performance wise session is best...

Reward points if helpfull.

Regards,

Kashyap