topic Re: synchronous processing in call transaction in Application Development and Automation Discussions

synchronous processing in call transaction

Former Member — Fri, 01 Jun 2007 07:13:29 GMT

Hi experts,

1.what is the synchronous processing in call transaction method?

I want exactly how data transfers from flat file to internal table and internal table to application,application to database during synchronous proceessing in call transaction method?

Pls help me in this regard

thanks inadvance

surya.

Re: synchronous processing in call transaction

Former Member — Fri, 01 Jun 2007 07:19:08 GMT

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.

<b>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.</b>

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

Reward points if useful

Regards

Anji

Re: synchronous processing in call transaction

Former Member — Fri, 01 Jun 2007 07:20:55 GMT

Hi,

if you are using synchronous database update, no transaction is started until the previous transaction has been written to database.

ie. while uploading ten records and if the system finds any error in the second record it wont allow to save the third record until the second record has been get save.

but if you use asynchronous database update the system skip the second record and the next successive non error record get saved.

Thanks,

Anitha

Re: synchronous processing in call transaction

Former Member — Fri, 01 Jun 2007 07:43:31 GMT

Hi,

Message: A 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.

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.

Regards

Re: synchronous processing in call transaction

Former Member — Fri, 01 Jun 2007 07:46:56 GMT

Call transaction	<tcode> using <BDCTAB>
	Mode <A/N/E>
	Update <S/A>
	Messages into <MSGTAB>.

Parameter – 1 is transaction code.

Parameter – 2 is name of BDCTAB table.

Parameter – 3 here you are specifying mode in which you execute transaction

A is all screen mode. All the screen of transaction are displayed.

N is no screen mode. No screen is displayed when you execute the transaction.

E is error screen. Only those screens are displayed wherein you have error record.

Parameter – 4 here you are specifying update type by which database table is updated.

<b>S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.</b>

A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).

Parameter – 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:

Re: synchronous processing in call transaction

Former Member — Fri, 01 Jun 2007 14:34:35 GMT

hi,

i want how synchronous processing is happening?

that means how the data is transfering from internal table to application?

if one record is read from internal table and after validated control goes to database or control returns to second record?

pls give me relavent information for the above questions?