ABAP - Keyword Documentation →  ABAP - Reference →  Processing External Data →  Data Consistency →  SAP LUW → 

COMMIT WORK

Quick Reference

Syntax

COMMIT WORK [AND WAIT].

Effect

The statement COMMIT WORK closes the current SAP LUW and opens a new one. All change requests from the current SAP LUW are then committed. In this case, COMMIT WORK performs the following actions:

  1. It executes all subroutines registered using PERFORM ON COMMIT.

    The order is based on the order of registration or according to the priority specified using the addition LEVEL. The following statements are not allowed to be executed in a subroutine of this type:

    PERFORM ... ON COMMIT|ROLLBACK
    COMMIT WORK
    ROLLBACK WORK

    The statement CALL FUNCTION ... IN UPDATE TASK can be executed.

  2. It triggers an internal event for the persistence service of the Object Services.

    If event handlers are registered by the persistence service, they collect the changes to the objects managed by the service and use CALL FUNCTION ... IN UPDATE TASK to pass them to a special update function module, registered as the final update module.

  3. It triggers the processing of all update function modules registered using CALL FUNCTION ... IN UPDATE TASK in the update work process or, for local updates, in the current work process as well.

    All high-priority ("VB1") update function modules are executed in the order of their registration and in a shared database LUW. If the addition AND WAIT is not specified, the program does not wait (in non-local updates) until the update work process has executed it (asynchronous updates), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).

    When all high-priority update function modules are completed successfully, the statement executes the low-priority ("VB2") update function modules in the order of registration in a shared database LUW in the update work process.

    No database commits and no database rollbacks can occur and the update control cannot be modified during the processing of an update function module triggered using COMMIT WORK is being processed. Any statements that would produce this situation are forbidden statements in updates and always produce runtime errors.

    After the execution of high-priority update function modules, the individual function modules registered using CALL FUNCTION ... IN BACKGROUND UNIT and CALL FUNCTION ... IN BACKGROUND TASK (obsolete) are each registered in their own database LUW by destination.

  4. It handles all SAP locks set in the current program in accordance with the value of the formal parameter _SCOPE of the corresponding lock function modules.

  5. Triggers a database commit on all currently open database connections, which also terminates the current database LUW and closes all database cursors.

The COMMIT WORK still triggers the event TRANSACTION_FINISHED from the system class CL_SYSTEM_TRANSACTION_STATE is triggered, whereby the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>COMMIT_WORK. The time when this event is triggered is described in the documentation for the event in the class:

Resources for preparation work can be cleaned up in the event handlers for this event before the update is performed. However, this is no guarantee that the update has not already been performed.

If the statement COMMIT WORK is executed by calling special programs, be aware of the following:

System Fields

sy-subrc Meaning
0 The addition AND WAIT was specified and the update of the update function modules was successful.
4 The addition AND WAIT was specified and the update of the update function modules was not successful.

The statement COMMIT WORK always sets sy-subrc to 0 if the addition AND WAIT is not specified.

Notes

Exceptions

Non-Handleable Exceptions