synchronous updation

[Former Member]

hi,

what exactly is synchronous updation???

and

asynchronous updation?

and how session and call transcation differ in this aspect??

[former_member787646]

Hi

Synchronous Update is Equivalent to COMMIT WORK AND WAIT.

Asynchronous Update is Equivalent to COMMIT WORK.

Hope this would help you.

Murthy

[Former Member]

how session and call transcation differ in this aspect??

[Former Member]

hi,

Session : Synchronous database update - During processing, no transaction is started until the previous transaction has been written to the database

Call transaction : Sync and Asynch dtaabase updating both possible. The program specifies which kind of updating is desired.

Regrads,

srilatha

[Former Member]

Any Example scenario ?

[Former Member]

HI ,

Synchronous update means that the database records are updated one after the other.The second one is updated only onece the first update is complete.In the meantime the second will wait for the first to update,

whereas,

Asynchronous update means that the updation of the second record does not depends on the updation of the first record.

Synchronous update:-

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

Asynchronous update:-

http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4cea79e11d1950f0000e82de14a/content.htm

Best of luck,

Bhumika

[Former Member]

Hi

Call transaction

1. synchronous updation

optional

2. errors can handled

explicitely

3. faster

4. less amount of data

5. updation takes place

during program execution

Session

1.only synchronous updation

2. error log is created

3. slower

4.more can transfer

5.updation takes place once the session being created

Regards,

Sravanthi

[Former Member]

Hi,

Database changes that are made via the SAP Update System and transferred to an update work process, can be carried out synchronously or asynchronously. The mode is specified in the ABAP source code of the SAP transactions and cannot be changed dynamically by the user.

The SAP transaction creates an update request with CALL FUNCTION u2026 IN UPDATE TASK, and transfers this to an update work process. Data is then written to the update tables at the end of a database LUW.

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.

Call Transaction

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

Session Interface

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,

Sujit

[Former Member]

Hi,

The session interface is synchronous update only. The batch input sessions are maintained by the system in the batch input queue.

But the calltransaction using interface are synchronous and asynchronous database updating both possible.

<removed by moderator>

Edited by: Mike Pokraka on Aug 4, 2008 2:19 PM