SAP ABAP Data Element OB_PRE_LOCK_METHOD (Name of a Pre-Lock function module)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CTS-ORG (Application Component) Transport Organizer
⤷
SCTS_OBJ (Package) CTS: Object Editing (Including Transport Objects)

⤷

⤷

Basic Data
Data Element | OB_PRE_LOCK_METHOD |
Short Description | Name of a Pre-Lock function module |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FUNCNAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table | TFDIR |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | PreLock FM |
Medium | 20 | Pre-Lock Func Module |
Long | 40 | Pre-Lock Function Module |
Heading | 50 | Pre-Lock Function Module |
Documentation
Definition
ZDM enablement requires mechanism to ensure that tables accessed by an AIM or an API used by an AIM can be locked. If explicit locking is required a function module can be specified that will be invoked right before the AIM is invoked to lock on the bridge instance the tables against production usage.
Use
The AIM for a transport object defines that it uses an API and this API defines a pre-lock function. If such a transport object is found the pre-lock method of the API will be invoked with this object before it is passed to the AIM.
The pre-lock function module will receive an internal table of structure E071 that contains the list of objects that will be processed by an AIM. It has to follow the interface and implementation rules for an AIM.
Dependencies
Example
History
Last changed by/on | SAP | 20141013 |
SAP Release Created in | 740 |