Application Development and Automation 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: 
Read only

Synchronize Vs ASynchronize

Former Member
0 Likes
934

Hai guru..

SAP is totaly Synchronize and when we are going to use DML statements I mean Data manupulating lang.

Insert, update ...like that

or LUW ( logical unit work )

It will change to ASynchronize

at that time we are going to use Commit work and wait.. to change again in Synchronize ..is it correct .

2 REPLIES 2
Read only

Former Member
0 Likes
527

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

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.

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

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.)

Check this link for diff of sync & async

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

synchronous: in this method it won't update any record until it will get acknoweldgement for updating.

Asynchronous: in this method it won't wait for acknoweldge ment for updating the record, directly it will update the record into the data base.

Basic type :

Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)

Type in ZINVRV01 and click on Basic IDoc type, click the Create icon

There is one more option is there extended idoc means if already existed idoc u can add more messeges.

Regards,

Chandru

Read only

Former Member
0 Likes
527

DML Statments are used to insert records in database.

As far as sap is concerned the SQL is used as DML.

Now When u update a database table through SQL commit work will Combine all updates in 1 LUW

Where do u need Asynch updates?

Its all getting Sync update

Lemme know why u need to use commit work and wait??