Session and Call Transaction

[Former Member]

Hi All,

I have query i.e we all know that Call Transaction is faster method compared to Session Method.

But when there is more amount of data why we use Session Method why not Call Transaction Method.

How can we decide to use which method.

thanks & regards

shashikanth naram.

[Former Member]

hi check this we will always use the call transaction method and session method in combine ....the data is processed through the call transaction ...if the error is occured in the call transaction then it will be processed by the session method automatically...if u had any doubts u can ask...

regards,

venkat.

[Former Member]

hi,

With CALL TRANSACTION USING, the system processes the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.

Your program prepares the data and then calls the corresponding transaction that is then processed immediately.

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

Create a session on the batch input queue.

Offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging.

Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.

Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function module calls from the ABAP program.

The most important aspects of the 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 batch input program must not open a session until it has closed the preceding session.

pls reward if helpful.

[Former Member]

Hi shashikant,

1. Yes you are right, session method is generally preferable.

2. The reasons are :

a) we have CONTROL over the process

b) the session method provides screens to

see the results of the upload - which transactions

failed and which were successful.

(In call transaction, we have to write code

to show those errors and other things)

c) we can re-enter those wrong records again by

even seeing what went wrong in the screens,

when that record was being entered as bdc.

regards,

amit m.