SAP ABAP Data Element /BOBF/ACT_WRITE_KEY (Action Write Node)
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/ACT_WRITE_KEY |
Short Description | Action Write Node |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /BOBF/CONF_KEY | |
Data Type | RAW | Uninterpreted sequence of bytes |
Length | 16 | |
Decimal Places | 0 | |
Output Length | 32 | |
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 | 0 |
Documentation
Definition
An action write node is a business object node that is locked before a action is carried out.
Use
If you want to be sure that all necessary nodes needed in the action implementation are already locked, then all of the relevant nodes should be assigned as Write nodes for that action. The business object processing framework ensures this before executing the action.
If lock nodes are not assigned, the nodes are locked when they are changed the first time. This could lead to multiple single lock calls and potential lock errors in the middle of the execution, which should be avoided.
Dependencies
Assigning action write nodes is only relevant if a business object is not only lockable on root node.
The change mode for locking can be set in the action.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |