Hierarchy
⤷
⤷
Basic Data
| Data Element | /BOBF/OBM_ASSOC_RESOLVE |
| Short Description | Resolving Node for Association |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /BOBF/OBM_ASSOC_RESOLVE | |
| Data Type | NUMC | Character string with only digits |
| 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 | 10 | Res. Node |
| Medium | 15 | Resolving Node |
| Long | 20 | Resolving Node |
| Heading | 40 | Resolving Node for Association |
Documentation
Definition
The resolving node for an association defines which node buffer is called to resolve this association.
Use
The business object processing framework asks the buffer for the result of an association (if association calls are not configured). In a multi-buffer configuration, the resolving node for an association determines if the buffer of the source node or the buffer of the target node is called to resolve the association.
Dependencies
Example
Resolve by Target Node: compositions are typically specializations that are resolved by the target node buffer because the child nodes contain its parent information and/or the filter data for the specialization.
Resolve by Source Node: associations to the parent node or (in general) foreign key associations are typically resolved by the source node buffer because the source node already has the key of the related target node.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 702 |