Differences between

[Former Member]

1. Synchronous / ASynchronous Processing

2. Synchronous / ASynchronous Updates

[prasanth_kasturi]

hi,

With synchronous updates, the program that outputs the statement COMMIT WORK AND WAIT waits until the update work process outputs the status of the update. The program can then respond to errors separately.

Synchronous updates can never be processed a second time.

As the calling program waits for the result and responds to it appropriately, you can assume that the error has been intercepted. If you try to processs a synchronous update in SM13 again, you will get the message This update request cannot be carried out retrospectively (synchronous update).

Synchronous updates are indicated by the symbol in the Info column in Update Management.

Updates generated by batch input sessions are always carried out synchronously. Batch input with CALL TRANSACTION USING can be updated synchronously and asynchronously. In addition to this, every 100th update in a background job is carried out synchronously in order to avoid delays in the Update System.

With asynchronous updates, the program that outputs the statement COMMIT WORK passes the update onto the Update System and does not wait for the update process to respond

[Former Member]

Hi,

1. Synchronous and Asynchronous Processing:

Asynchronous refers to processes that do not depend on each other's outcome, and can therefore occur on different threads simultaneously. The opposite is synchronous. Synchronous processes wait for one to complete before the next begins. For those Group Policy settings for which both types of processes are available as options, you choose between the faster asynchronous or the safer, more predictable synchronous processing.

By default, the processing of Group Policy is synchronous. Computer policy is completed before the CTRLALTDEL dialog box is presented, and user policy is completed before the shell is active and available for the user to interact with it.

Now see in case of ABAP, it will be much clearer:

http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4dda79e11d1950f0000e82de14a/content.htm

2. Synchronous / ASynchronous Updates:

Asynchronous Update u2013 The program does not wait for the work process to finish the update. Commit Work.

Synchronous Update u2013 The program wait for the work process to finish the update. Commit Work and Wait.

Please also have a look on these links:

http://fuller.mit.edu/tech/sync_asynchronous.html

http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4d4a79e11d1950f0000e82de14a/content.htm

Rewards if useful.

BR,

Alok Sharma

[Former Member]

Hi,

1)In call transaction there are 2 ways in which you could update.

Asynchronous Update – The program does not wait for the work process to finish the update. Commit Work.

Synchronous Update – The program wait for the work process to finish the update. Commit Work and Wait.

2)https://forums.sdn.sap.com/click.jspa?searchID=12181501&messageID=727442

Regards

Kiran

[Former Member]

Hi,

Calling Update Functions

Synchronous or Asynchronous Processing?

Function modules that run in the update task can run synchronously or asynchronously. You determine this by the form of the commit statement you use:

COMMIT WORK

This is the standard form, which specifies asynchronous processing. Your program does not wait for the requested functions to finish processing.

COMMIT WORK AND WAIT

This form specifies synchronous processing. The commit statement waits for the requested functions to finish processing. Control returns to your program after all high priority (V1) function modules have run successfully.

The AND WAIT form is convenient for switching old programs to synchronous processing without having to re-write the code. Functionally, using AND WAIT for update-task updates is just the same as dialog-task updates with PERFORM ON COMMIT.

Parameter Values at Execution

In ABAP, you can call update-task function modules in two different ways. The way you choose determines what parameter values are used when the function module is actually executed. Parameter values can be set either at the time of the CALL FUNCTION statement, or at the time of the COMMIT WORK.

With synchronous updates, the program that outputs the statement COMMIT WORK AND WAIT waits until the update work process outputs the status of the update. The program can then respond to errors separately.

Synchronous updates can never be processed a second time.

As the calling program waits for the result and responds to it appropriately, you can assume that the error has been intercepted. If you try to processs a synchronous update in SM13 again, you will get the message This update request cannot be carried out retrospectively (synchronous update).

Synchronous updates are indicated by the symbol in the Info column in Update Management.

Updates generated by batch input sessions are always carried out synchronously. Batch input with CALL TRANSACTION USING can be updated synchronously and asynchronously. In addition to this, every 100th update in a background job is carried out synchronously in order to avoid delays in the Update System.

With asynchronous updates, the program that outputs the statement COMMIT WORK passes the update onto the Update System and does not wait for the update process to respond

Regards,

Jagadish

[Former Member]

In batch session: Asynchronous processing means Data Transfer for multiple transactions.

Synchronous database update means during processing, no transaction is started until the previous transaction has been written to the database.

In call transaction: - Synchronous processing means Data Transfers for a single transaction. Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.

In synchronus Updating ,It will wait for work process to to finish the update .Before completing this update it willnot start another one.

In Asynchronus update, The program does not wait for the work process to finish the update (Asynchronous Update).

Please reward points if helpfull.