Skip to Content

ABAP Commit work and wait without asynchronous function modules

Oct 18, 2017 at 07:12 AM


avatar image


I have a question regarding COMMIT WORK AND WAIT.

What I understood so far is that the additionon of AND WAIT will make the processing synchronus, e.g. waiting for function module which were called IN UPDATE TASK.

However, what does this mean in case of changes which were called not in update task?

Considering I have made change via (non BAPI) standard function modules. These modules were not called in update task. Thus the "only" thing to do after committ is to actually write changes to the data base.

In my understanding in this case COMMIT WORK and COMMIT WORK AND WAIT will not make a difference as my changes will be processed synchronously anyways. This is since the pure COMMIT WORK will also wait for my changes to be written to the data base.

Am I right with this assumption?

Thank you very much for your help

10 |10000 characters needed characters left characters exceeded

Can anybody help me out with this question?

* Please Login or Register to Answer, Follow or Comment.

2 Answers

Horst Keller
Oct 23, 2017 at 09:07 AM
10 |10000 characters needed characters left characters exceeded
Raymond Giuseppi
Oct 23, 2017 at 09:11 AM

Read the COMMIT WORK statement documentation.

  • At a step, it will execute update task FM, if no high-priority update task FM "VB1" was registered, the WAIT will be ignored.
  • At the last step it will trigger a database commit, so validating change executed out of standard (...) Of course no other Explicit or Implicit Database Commits should have been already triggered)
  • Of course there can be delay due to database server and buffering, but this is an other story...
10 |10000 characters needed characters left characters exceeded