Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

bdc

Former Member
0 Kudos
105

regarding call transcations and sessions method

1 ACCEPTED SOLUTION

Former Member
0 Kudos
65

In simple terms, CALL TRANSACTION is immediate processing and a fast method in comparision whereas session method can be schedule according to our wish. Session method is although slow, but gives a valuable option of "error processing".

Details:

The most important features of CALL TRANSACTION USING are:

1. Synchronous processing

2. Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called

3. You can update the database both synchronously and asynchronously

The program specifies the update type

4. Separate LUW (logical units of work) for the transaction

The system executes a database commit immediately before and after the CALL TRANSACTION USING statement

5. No batch input processing log

The most important aspects of the session interface are:

1. Asynchronous processing

2. Transfers data for multiple transactions

3. Synchronous database update

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

4. A batch input processing log is generated for each session

5. Sessions cannot be generated in parallel

The batch input program must not open a session until it has closed the preceding session.

check this lin too:

https://www.sdn.sap.com/irj/sdn/forums

3 REPLIES 3

Former Member
0 Kudos
66

In simple terms, CALL TRANSACTION is immediate processing and a fast method in comparision whereas session method can be schedule according to our wish. Session method is although slow, but gives a valuable option of "error processing".

Details:

The most important features of CALL TRANSACTION USING are:

1. Synchronous processing

2. Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called

3. You can update the database both synchronously and asynchronously

The program specifies the update type

4. Separate LUW (logical units of work) for the transaction

The system executes a database commit immediately before and after the CALL TRANSACTION USING statement

5. No batch input processing log

The most important aspects of the session interface are:

1. Asynchronous processing

2. Transfers data for multiple transactions

3. Synchronous database update

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

4. A batch input processing log is generated for each session

5. Sessions cannot be generated in parallel

The batch input program must not open a session until it has closed the preceding session.

check this lin too:

https://www.sdn.sap.com/irj/sdn/forums

Former Member
0 Kudos
65

call transaction :

in that any one transaction method can be processed.also dose not generate log files.but expectly has to be define in the program using structure BDC

CALL SESSION

in that multiple transaction can be processed. and also in the screen method,errors logs on automatically generated</b>.

0 Kudos
65

hi all ,

bdc session method is good for when company is in already in implementation i.e

no.of users working in same application server sothat the performance is goes down in that case we for BDC Session method to process the programs at particular time.

i.e session object is created in application server and processed by enduser not developer.