topic Re: COMMIT WORK AND WAIT in Application Development and Automation Discussions

COMMIT WORK AND WAIT

Former Member — Tue, 30 Jun 2009 08:27:59 GMT

Hi,

Can any one explain me the difference between COMMIT WORK and COMMIT WORK AND WAIT?

Actually I am trying to Use:

{ CALL TRANSACTION XD01 USING BDCDATA

MODE 'N'

UPDATE 'S'

MESSAGES INTO MESSTAB. }

This Statement I want to use only Customer Data to Validate. Once the validation happens, I want to Roll back all changes using

BAPI_TRANSACTION_ROLLBACK. Is it possible to Roll Back? Does it validate Customer data rather than Create Customer.

Please give me any other pointers, If possible?

Regards,

Re: COMMIT WORK AND WAIT

Former Member — Tue, 30 Jun 2009 08:33:56 GMT

Hi Sekhar,

Commit work----

> when you use commit work it will hit the database and store immediately.

commit work and wait----

> this statement will hit the database and wait sometime to process the second record in an loop.

if you want to validate the customer you can use validations before the BDC process and filter if you want to use roll back then check the sy-subrc after your call transaction if it fails then you can rollback.

Re: COMMIT WORK AND WAIT

former_member556412 — Tue, 30 Jun 2009 08:35:38 GMT

The statement COMMIT WORK completes the current SAP-LUW and opens a new one, storing all change requests for the current SAP LUW in the process.

and if you specify the AND WAIT addition to Commit work the program until the update work process has executed it (asynchronous updating).

Re: COMMIT WORK AND WAIT

uwe_schieferstein — Tue, 30 Jun 2009 08:35:49 GMT

Hello Sekhar

Irrespective of whether the update mode is Sychronous or Asynchronous the customer will not be created if any of the validations fails so there is no need for any ROLLBACK WORK.

Regards

Uwe

Re: COMMIT WORK AND WAIT

Former Member — Tue, 30 Jun 2009 08:36:10 GMT

commit work ( asynchronous updating )

commit work and wait ( synchronous )

Re: COMMIT WORK AND WAIT

Former Member — Tue, 30 Jun 2009 08:38:11 GMT

The data are usually saved by processes running in update task or background, these processes are raised at the end of a transaction (or LUW, Logical Unit of Work)) by COMMIT WORK statament.

If it uses the addition WAIT, the program waits for the end of all processes, if it doesn't use ti, the program goes on without to wait for them.

So:

- commit work is asynchronous process, because the program runs while the saving process are running too,

- commit work and wait is synchronous process, because the programs runs after the saving process are over.

Try to check the SAP HELP for LUW, here u can find out all informations u need

If you want to check some validation, it's better to create a BI simulation without to save, but to exit from trx only: that works if the validation is not triggered as soon as the data is saved

Max

Re: COMMIT WORK AND WAIT

Former Member — Tue, 30 Jun 2009 11:42:18 GMT

commit work -> all records get updated into the table one by one (if there are more than 1 record or more than 1 table)

commit work and wait -> system waits untill all the records are updated to the tables and then it moves to the next statement.

i think u r updating data using BDC.So if there is any error then it will rollback automatically.

Regards

Sajid