Hierarchy

⤷

⤷

Basic Data
Data Element | /BOBF/DET_TRIGGER_KEY |
Short Description | Determination Request 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 request node is a business object node that triggers adetermination if instances of this node are changed.
Use
The business object processing framework executes all determinations that are triggered based on the assigned determination request nodes where the node instances have been changed.
Dependencies
The relevant changes for triggering depend on the determination time and have to be assigned in addition to the determination request node assignment.
For After Loading, the relevant change condition is the loading of node instances whereas for all other determination times, the relevant change conditions for triggering are the creation, update or deletion of node instances.
Example
If you want to cumulate some quantities or values from an document item to the document header, a determination should be defined on the header node that is triggered by changes of the item nodes.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |