Hierarchy
⤷ BC-SRV-BRF (Application Component) Business Rule Framework
⤷ SBRF (Package) Business Rule Framework
Basic Data
Data Element | BRF_TCONTEXT_ELEMENT_DIRECTION |
Short Description | BRF: Context Element Is Return Context Element |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BRF_BOOLE_D | |
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 | 10 | RtrnContxt |
Medium | 20 | Return Contxt Elemnt |
Long | 40 | Return Context Element |
Heading | 55 | Context Element Is Return Context Element |
Documentation
Definition
Use
Each context element has one direction of data flow. Usually, the direction of the data flow is from the application to the BRF. Accordingly, such a context element provides the application data for which BRF expressions are evaluated.
However, if you set this indicator, the direction of the data flow is reversed. Such a return context element returns the results of the evaluations in the BRF to the calling application.
Note: The BRF standard does not support any context elements that enable data flow in both directions.
Dependencies
The functionality of the return context elements is not part of the standard migration from the BRF to the FDT (Formula & Derivation Tool). Therefore, if you want to migrate from the BRF to the FDT, you must ensure in your application that the functionality of the return context elements is also migrated.
Example
The context contains the following context elements:
- Context element that stands for the entire contents of a request form (as filled out by the requester)
- Return context element that contains those fields that were calculated by the BRF. This might be a compressed or a corrected form of the request, for example.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 710 |