CALL TRANSACTION & SESSION

[Former Member]

Hi,

Could somebody explain me out these doubts..

1> I want to upload for two trasactions (e g MM01 & XK01) in one custom program for session method. Shall i call two BDC_OPEN_GROUP for these two transactions .

Then it will create two sessions at a time and i can run both in SM35 to upload.

Or can we do for both by creating only one session???

I dont want to do recording for this.

2> Could you tell me any situation where we can choose only call transaction for uploadation??

Thanks in advance.

[Former Member]

U can use onli one BDC_OPEN_GROUP fm...

but after filling the bdcdata table ..

u need to call BDC_INSERT twice , one for MM01 second for XK01,,

and one BDC_CLOSE_GROUP.

********************

<b>Call transaction method is faster than Session method..

Here are the differences between these two..</b>

<u>

Use the CALL TRANSACTION USING statement</u>

Summary: 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

<u>Create a session on the batch input queue.</u>

Summary: 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.

regards,

sai ramesh

[Former Member]

Hi Sai,

Thanks for your reply.

in the second question i just want to know is there any scenario in real time where

we can go for only call transaction for the migration.

thanks.

[Former Member]

In general, Session can be done for all the transactions which support call transaction. The thumb rule is that if th number of records are less than 10000 you go for call transaction, other wise we should go for session.

BUt i don't see any scenario, where we HAVE to go for call transaction only.

Regards,

Ravi