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
Basic Data
| Data Element | /BOBF/DET_WRITE_KEY |
| Short Description | Determination 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
A determination write node is a business object node that is locked before a determination is carried out.
Use
If you want to ensure that all of the required nodes in the determination implementation are already locked, then all of the relevant nodes should be assigned as write nodes for that determination. The business object processing framework ensures this before executing the determination.
If lock nodes are not assigned, the nodes are locked when they are changed the first time. This could lead to multiple single reads to the buffer and the persistency, which should be avoided.
Dependencies
Assigning determination write nodes only makes sense if a business object is not only lockable on the root node.
The change mode for locking can be set in the determination.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 702 |
