SAP ABAP Data Element /BOBF/OBM_LOCKABLE (Node is lockable separately)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷ AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration
⤷ /BOBF/CONFIGURATION (Package) Business Object Processing Configuration
⤷ AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration
⤷ /BOBF/CONFIGURATION (Package) Business Object Processing Configuration
Basic Data
Data Element | /BOBF/OBM_LOCKABLE |
Short Description | Node is lockable separately |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BOOLE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 40 | Node is lockable separately |
Documentation
Definition
An indicator to define if a node is lockable.
Use
This indicator can be used to define:
- If a node can be locked on its own
- If the node is locked with its parent node
- Some other grandparent nodes
Dependencies
A lockable node needs to be loadable on its own by definition because the business object processing framework refreshes the data in the buffer if the lock property changes.
A transient node cannot be defined as lockable.
A delegated node cannot be defined as lockable.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |