ABAP Keyword Documentation →  ABAP - Reference →  Processing External Data →  ABAP Database Accesses →  Object Services →  transaction service 

Transaction Service Overview

The classic SAP transaction concept is based on SAP LUWs in which changes to the database are bundled into a single database LUW. The bundling techniques used here include programming database changes in procedures and registering them in a database LUW for later execution instead of performing them immediately. Such procedures include subprograms (registered using PERFORM ON COMMIT) and update function modules (registered using CALL FUNCTION IN UPDATE TASK). In both cases, the registered procedures are executed using the COMMIT WORK statement.

The transaction service in Object Services is also based on SAP LUWs and not on a new transaction concept. However, it does the bundling before the developer, so that the developer does not have to explicitly create and register procedures that change the database. Internally, the Transaction Service still works with the classic update function modules.

This concept permits interaction between classic and object-oriented transactions, controlled using a transaction mode that can be set for a given program.

Other versions: 7.31 | 7.40 | 7.54