COMMIT WORK AND WAIT

[former_member299080]

Message opened on behalf of colleague:

I just have a quick inquiry regarding COMMIT WORK AND WAIT, I

understand that this method performs the following:

"This form specifies synchronous processing. The COMMIT statement waits

for the end of processing. Control returns to your program after all

high priority (V1) function modules have run successfully."

"The AND WAIT form is convenient for switching old programs to

synchronous processing without having to re-write the code.

Functionally, using AND WAIT for update-task updates is just the same

as dialog-task updates with PERFORM ON COMMIT."

It says that before doing the actual commit it will wait for the end of

processing for all related updates against the transaction. However

does it also wait for any "user exits" to finish or does it go ahead

and performs the commit and updates then the user exit happens?

Thanks.

[Sm1tje]

the user exits are already processed, before you do the commit. Even all the inserts/updates you add (to ztables) in the user exit will be commited by the COMMIT WORK AND WAIT.

[Former Member]

Hi User exit is part of the transaction where you call a subroutine, or another function module or BADI method. So in my opinion it will wait. Unless there is a explicit commit work coded inside the user exit.

regards,

Advait