Hierarchy

⤷

⤷

Basic Data
Data Element | /BOBF/OBM_DATA_ACCESS_RELEVANT |
Short Description | Attribute relevant for Data Access |
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 | 50 | Data Access relevant |
Documentation
Definition
Indicator that indicates if an attribute is relevant for the access of the data on the persistency.
Use
The indicator can be set for attributes assigned in the association binding to model that if the association is followed the value of this attribute is taken into account and evaluated when accessing the persistency. If this attribute is not set all target node instances are read into the buffer and the binding is evaluated in the buffer only.
The use of this setting depends heavily on the use cases. Sometimes the performance and the memory usage is much better using this indicator and sometimes using this indicator perfromance decreases while memory usage is stable.
- If an association is called with many different filter values during a transaction or even sometimes without any filter values the indicator should not be set.
- If usually only one filter value is used within the business object (e.g. language code is always the same) the indicator should not be set.
- If an association is called usually always with the same filter values within one transaction (and does not fulfill the latter case) teh indicator should be set.
Dependencies
The indicator can be set in the association binding only for binding types that independent on the source or target node instances of an association ( i.e. binding to filter attributes or constant values).
Example
An association to a language-dependent description node usually has a filter on the language code.
If in the binding to the language code this indicator is not set when accessing the node with a filter on the user language all descriptions in all languages are read into the buffer (if they are not already available in the buffer), but only the relevant is returned as result of this association as the evaluation is done in the buffer.
If in the binding to the language code this indicator is set when accessing the node with a filter on the user language only the description in the requested language is read into the buffer (if it is not already available in the buffer).
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |