ABAP for Cloud Development
AS ABAP Release 914, ©Copyright 2024 SAP SE. All rights reserved.
ABAP - Keyword Documentation → ABAP RAP Business Objects → RAP - Behavior Definitions → RAP - BDL for Behavior Definitions → RAP - Managed and Unmanaged Behavior Definitions → RAP - EntityBehaviorDefinition → RAP - EntityBehaviorBody → RAP - RAP BO Operations → RAP - RAP BO Operation, Additions →
RAP - lock:none
Syntax
... (lock:none) ...
Description
The RAP BO operation addition lock:none
prevents the locking mechanism for the entity instance for which an action is executed. As a prerequisite, the RAP locking mechanism must be defined and implemented.
lock:none
can be used for the following operations:
- Instance-bound non-factory actions
- Instance-bound factory actions
- Note: Since static actions are not related to a specific instance, they are non-locking by definition and this syntax element is not applicable.
- Note: The locking mechanism is only prevented for the action itself. Possible modify calls in the action implementation are not affected by the non-locking specification in the action definition. Consequently, an instance is locked if it is modified by an action even if the action is defined as non-locking.
Availability
- Managed RAP BO
- Unmanaged RAP BO
- In projection and interface BDEFs, the RAP locking settings from the base BO are automatically reused and do not need to be explicitly defined. For details, see the topic RAP -
use
, Projection and Interface BDEF.