BDC error handling / Difference in synchronous and asynchronous

[itabhishek9]

Hello SDNites,

I have some very basic questions and I would prefer if you answer me giving me some good simple example.

1. What is the difference in synchronous and asynchronous update mode in termas of BDC? Please give an example.

2. How do we handle the error in Call transaction method. Suppose we have 10 records to be uploaded and my second record failed i.e. screen where recording was done was stopped in between. How do we handle the same?

Regards,

Abhi.

[itabhishek9]

Hi Abhishek,

1. In case of the Asynchronous updates of called the called programs is executed same as commit work but the program execution is not wait until the commit work execution gets completed.

2. in case of the Synchronous processing the updates for all the called programs is done same as commit work and program will not executes and program wait until all the updates are not completed,

e.g if you trying to change any document using BDC transaction then in case of the Synchronous processing program will not executes the next statement as long as all the tables related to the document got changed.

3. you can handle the Error in the BDC by capturing all the messages into BDC message table, which contains all the messages appeared in the BDC process with message class and message number.

CALL TRANSACTION 'transaction name' update mode messages into T_MESSAGES.

T_messages of type BDCMSGCOLL

[nirajgadre]

Hi Abhishek,

1. In case of the Asynchronous updates of called the called programs is executed same as commit work but the program execution is not wait until the commit work execution gets completed.

2. in case of the Synchronous processing the updates for all the called programs is done same as commit work and program will not executes and program wait until all the updates are not completed,

e.g if you trying to change any document using BDC transaction then in case of the Synchronous processing program will not executes the next statement as long as all the tables related to the document got changed.

3. you can handle the Error in the BDC by capturing all the messages into BDC message table, which contains all the messages appeared in the BDC process with message class and message number.

CALL TRANSACTION 'transaction name' update mode messages into T_MESSAGES.

T_messages of type BDCMSGCOLL

[Former Member]

This message was moderated.