Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  Processing External Data →  ABAP Database Access →  Data Consistency 


An application program can be split into several program sections, which are processed in sequence using different work processes. Each switch of a work process is associated with an implicit database commit, which means that an application program is not associated with a single database LUW automatically. More specifically, this applies to dialog-oriented applications with classic dynpros in SAP GUI in which each dialog step is assigned a database LUW.

To ensure the data consistency of application programs that are executed across multiple work processes, the change statements are not executed directly in an SAP LUW. Instead, they are first registered and then executed by a single work process, that is in a single database LUW.


Other versions: 7.31 | 7.40 | 7.54

Bundling Methods

The following techniques are available for bundling the change statements in a database LUW:

  • Update (bundling using function modules)
The statement CALL FUNCTION ... IN UPDATE TASK is used to register an update function module for later execution in an update work process (synchronous and asynchronous update) or in the current work process (local update). In updates, no forbidden statements can be executed and no authorization checks can be made. Synchronous and asynchronous updates are executed in their own update sessions. Local updates, on the other hand, only open a new internal session.
  • Transactional RFC (bundling using function modules)
The statement CALL FUNCTION ... IN BACKGROUND UNIT is used to register a remote-enabled function module for later asynchronous execution in the background and through the RFC interface (background RFC).
  • Bundling using subroutines
The statement PERFORM ... ON COMMIT is used to register a subroutine for later execution in a different work process.


A function module can be specified as either an update function module or as remote-enabled, but not both at the same time. The update is used to realize SAP LUWs within AS ABAP, while transactional RFC creates LUWs in distributed systems.

Statements for SAP LUWs

Each opening of a new internal session (except for the statement CALL DIALOG) starts a new SAP LUW which can be controlled by the ABAP SQL statements


  • The statements COMMIT WORK and ROLLBACK WORK determine the limits of a SAP LUW. An ABAP program can be divided into any number of SAP LUWs, whereby the end of an ABAP program always ends the last SAP LUW as well. Calling ABAP programs with CALL TRANSACTION or SUBMIT ... AND RETURN provides the option of nesting SAP LUWs.

  • The system class CL_SYSTEM_TRANSACTION_STATE contains methods that return the status of the current SAP LUW.

SAP LUWs and internal sessions

Each closing of an internal session ends the current SAP LUW. If a program is ended or an internal session closed using

and procedures are still registered in the current SAP LUW, the SAP LUW is ended and the procedures are not called or rolled back. Registered update function modules remain on the database but can no longer be executed.


If a program is called using

a new SAP LUW opens, but not a new database LUW. This means that a database rollback in this SAP LUW can roll back all registration entries made by the statements CALL FUNCTION IN UPDATE TASK or CALL FUNCTION IN BACKGROUND TASK in the tables VB... or ARFCSSTATE and ARFCSDATA. Under certain circumstances, the statement ROLLBACK WORK in the called program can also affect the interrupted SAP LUW. To prevent this, an explicit database commit must be executed before the program is called. This problem does not occur in local updates.







Forbidden Statements in Updates

Authorization Checks in Updates

SAP LUW, Examples