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

BDC update

Former Member
0 Likes
743

Hi,

What is the major differnce between asynchornous update and synchronous update using BDC.

Will it affect any transaction if we make a continuous flow.

If i create GR based on A mode and using GR number i need to create Delivery.

1 ACCEPTED SOLUTION
Read only

abdul_hakim
Active Contributor
0 Likes
714

HI

With asynchronous update the called transaction doesnot wait for any updates that it produces to be completed.

It simply passes the update to sap update service.

The calling program cannot determine whether the update is successfull or not.But the processing will be fast in asynchronous mode.Error recovery and restart capability is less compared to synchronous update.

With synchronous update the called transaction wait for any updated that it produces to be completed.Processing is slower when compared to asynchronous update.But the called transaction is able to return any update error messages to the calling program.

Abdul

5 REPLIES 5
Read only

sreekanthgo
Contributor
0 Likes
714

Hi Ananda Krishnan,

Synchronous mode updates data into Data Base for all the tables which are related to the transaction at a single time. If any errors occurs it will ROLLBACK.

But Asynchronous mode updates data into Data Base one by one, if any error occurs it stops there.

Thanks,

Sreekanth G

Read only

abdul_hakim
Active Contributor
0 Likes
715

HI

With asynchronous update the called transaction doesnot wait for any updates that it produces to be completed.

It simply passes the update to sap update service.

The calling program cannot determine whether the update is successfull or not.But the processing will be fast in asynchronous mode.Error recovery and restart capability is less compared to synchronous update.

With synchronous update the called transaction wait for any updated that it produces to be completed.Processing is slower when compared to asynchronous update.But the called transaction is able to return any update error messages to the calling program.

Abdul

Read only

Former Member
0 Likes
714

Hi Anandha,

1.

What is the major differnce between asynchornous update and synchronous update using BDC.

SYNCHRONOUS : The program will wait for

call transaction to FINISH .

ASYNCHRONOUS : The program will NOT WAIT.

2. create GR based on A mode and using GR number i need to create Delivery.

There will be a problem. Its tricky !

Use SYNCHRONOUS MODE.

After That.

Also Use COMMIT WORK AND WAIT.

3. Then check out the GR Number for delivery purpose.

I hoe it helps.

Regards,

Amit M.

Read only

0 Likes
714

Hi

All std transactions store the data by processes in update tusk.

These processes work at the end, when a commit is called.

If you use ASYNCHRONOUS mode, your program won't wait for the end of trnasaction, while if you use SYNCHRONOUS it'll wait for the its end.

So if you use ASYNCHRONOUS mode, while your program working, the transaction is storing the data.

So if you have to read the data stored by transaction of BDC, if you use ASYNCHRONOUS mode, you couldn't read the data because it couldn't saved yet.

If you don't need to read the tables used by transaction, it shoul'd be better use ASYNCHRONOUS becouse it's better for performance.

If all you want to know is the number of delivery is used, you can read it from message table.

If you need to read the tables to store your own data in custom tables, you should use SYNCHRONOUS.

Max

Message was edited by: max bianchi

Message was edited by: max bianchi

Read only

Former Member
0 Likes
714

Hi,

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

An <b>Asynchronous</b> 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 <b>asynchronous</b> 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.