Difference between UPDATE options for CALL TRANSACTION

Former Member — Thu, 11 Dec 2008 22:08:43 GMT

When using CALL TRANSACTION, you can specify one of thee update options:

Local
Synchronous
Asynchronous

I think the Synchronous and Asynchronous updates will decide whether to return to the calling program before or after the DB commit operation.

Can anyone explain what the use of Local would be?

Re: Difference between UPDATE options for CALL TRANSACTION

former_member156446 — Thu, 11 Dec 2008 22:19:01 GMT

Hi there... check the link below

You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:

A Asynchronous updating. In this mode, the called transaction does not wait for any updates 
it produces to be completed. It simply passes the updates to the SAP update service.
Asynchronous processing therefore usually results in faster execution of your data transfer program.

Asynchronous processing is NOT recommended for processing any larger amount of data. 
This is because the called transaction receives no completion message from the update 
module in asynchronous updating. The calling data transfer program, in turn, cannot determine
whether a called transaction ended with a successful update of the database or not.

If you use asynchronous updating, then you will need to use the update management
facility (Transaction SM12) to check whether updates have been terminated abnormally
during session processing. Error analysis and recovery is less convenient than with 
synchronous updating.

S Synchronous updating. In this mode, the called transaction waits for any updates that
it produces to be completed. Execution is slower than with asynchronous updating because 
called transactions wait for updating to be completed. However, the called transaction is 
able to return any update error message that occurs to your program. It is much easier for 
you to analyze and recover from errors.

L Local updating. If you update data locally, the update of the database will not be 
processed in a separate process, but in the process of the calling program. 
(See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)

[Link|http://help.sap.com/saphelp_sm32/helpdata/EN/fa/09715a543b11d1898e0000e8322d00/content.htm]

Re: Difference between UPDATE options for CALL TRANSACTION

Former Member — Thu, 11 Dec 2008 22:20:26 GMT

Check F1 help of Statement SET UPDATE TASK LOCAL.

from SE38

Re: Difference between UPDATE options for CALL TRANSACTION

former_member183804 — Thu, 11 Dec 2008 23:27:11 GMT

Hello Timothy,

the called ABAP-transaction shares NEVER a common Db-transaction with the calling program.

Regards

Klaus

topic Re: Difference between UPDATE options for CALL TRANSACTION in Application Development and Automation Discussions

Difference between UPDATE options for CALL TRANSACTION

Re: Difference between UPDATE options for CALL TRANSACTION

Re: Difference between UPDATE options for CALL TRANSACTION

Re: Difference between UPDATE options for CALL TRANSACTION