ABAP Keyword Documentation → ABAP − Reference → Processing External Data → ABAP Database Access → Data Consistency
SAP Locks
SAP locks must be persisted for the duration of SAP LUWs. For this reason, different work processes and, if applicable, a new AS Instances must be able to handle these locks.
SAP locks are based on lock objects. These are defined in ABAP Dictionary and enable locks to be set on one or more rows in a single database table or locks to be set on rows in multiple database tables associated using foreign key dependencies.
When a lock object is created, two lock function modules are generated whose names consist of the prefixes ENQUEUE_ and DEQUEUE_ and the name of the lock object.
More details can be found under SAP Lock Concept in the SAP Help Portal.
Other versions: 7.31 | 7.40 | 7.54
Setting SAP Locks
When called, lock function modules set or remove SAP locks. These function modules access a central lock table in the memory of a special work process of the current AS Instance. Every AS ABAP contains exactly one such table (administered by transaction SM12). An enqueue function module sets an SAP lock by writing a corresponding entry in the lock table. If a lock cannot be set because corresponding lock entries already exist in the lock table, the function module terminates with the exception FOREIGN_LOCK.
The most important input parameters of an enqueue function module are:
| Parameter | Meaning |
|---|---|
| MODE_dbtab | Type of the lock for the database table dbtab of the lock object. Possible values include "S" for ashared lock, "E" for anexclusive lock, "X"for an expanded exclusive lock that can be requested only once (unlike a regular exclusive lock withina program), and "O" for an optimistic lock, which behaves like a shared lock at first, but can be transformed to an exclusive lock. |
| KEY_FIELDS | For all key fields of the lock object, values can be specified that define the rows to be locked. If no value is specified for a key field, all corresponding rows are locked. |
| _SCOPE | Definition of the lock duration with respect to an SAP LUW. Possible values include "1" for handling the lock in the same program, "2" for passing the lock to theupdater, and "3" for handling the lock in the program and in the updater. |
Note
An SAP lock is checked by trying to set a corresponding lock and handling the exception FOREIGN_LOCK in the process.
Releasing SAP Locks
SAP locks can be released by deleting the associated entry in the lock table.
When an SAP lock is set using the function module ENQUEUE, the value passed to the input parameter _SCOPE determines the lock duration. Depending on the formal parameter _SCOPE, an SAP lock can be released as follows:
- If _SCOPE is set to 1, the lock is not associated with the current SAP LUW. The lock can be released either by calling the DEQUEUE function module if the value "1" or "3" is passed to the formal parameter _SCOPE, or by terminating the program.
- If _SCOPE is set to 2, the lock is associated with the current SAP LUW. If
CALL FUNCTION ... IN UPDATE TASKregistered at least one update function module, the statementCOMMIT WORKorROLLBACK WORKreleases the lock when the SAP LUW is completed. When usingCOMMIT WORK, the update function releases the lock after processing the update function modules. This type of lock may persist beyond the end of a program until the update procedure has been completed.
- If _SCOPE is set to 3, both the update function and the program must release the lock. Releasing the lock by update corresponds to _SCOPE having the value 2. Releasing the lock in the program corresponds to _SCOPE having the value 1. The full lock release is defined by who released the lock last.
If the function module DEQUEUE is used to release an SAP lock independently of the update, the formal parameter _SCOPE must be given a value that is greater than or equal to the value passed to the same parameter of the function module ENQUEUE.
Besides the _SCOPE parameter, the input parameters of a DEQUEUE function module correspond to those of the ENQUEUE function module. The additional parameter _SYNCHRON can then be used to specify whether the release of the lock should be delayed until program processing is resumed.