Hierarchy
⤷ FS-CM (Application Component) Claims Management
⤷ ICL_CDC (Package) FS-CM: Data Capture
Basic Data
Data Element | ICL_QSPARAM2 |
Short Description | Second BRF Expression for Determining Question Sequence |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BRF_EXPRESSION | |
Data Type | CHAR | Character String |
Length | 20 | |
Decimal Places | 0 | |
Output Length | 20 | |
Value Table | TBRF150 |
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 | 15 | 2ndBRF Expressn |
Long | 15 | 2ndBRF Expressn |
Heading | 0 |
Documentation
Definition
Second BRF expression for determination of the question sequence for structured facts capture.
Use
In your application you can display different question sequences for a facts capture category, depending on the context. You use Business Rule Framework (BRF) expressions (and associated values) and/or rules to control this context dependency. You use the priority to define the sequence of processing.
At runtime, the question sequence and/or the variant of the question sequence that fulfils the following conditions is displayed on the relevant screen:
- The value that is returned by the first BRF expression matches the value that you store in the First Value field
- The value that is returned by the second BRF expression matches the value that you store in the Second Value field
- The defined rule returns the value TRUE
If you do not define a rule, this field is not considered.
If you do not define any BRF expressions and values, the question sequence is only determined on the basis of the rule.
Notes:
- For frequently occurring combinations, enter as high a priority as possible (in other words, a low number), so that the system only needs to evaluate the minimum number of lines.
- In the last line (with the lowest priority, meaning the highest number), define a line in which neither BRF expressions nor a rule are specified. This line is always valid and thus determines the question sequence if none of the previous conditions are fulfilled.
Dependencies
You only need to define BRF expressions and/or rules if you wish to define several question sequences for a facts capture category.
Example
Example in the Line of Health Insurance:
You want to store several question sequences for the Claim Item Grouping facts capture category. Depending on the relevant context, a certain question sequence should be displayed.
For example, you can make a setting so that the question sequence Care Insurance, Ongoing Care (technical key NC3) is always shown at runtime if the following conditions are fulfilled:
- The subclaim type of the current subclaim is Ongoing Care Benefit (in other words, the BRF expression PFSCLT returns the value PFLP (specification in First Value field).
- The current claim item grouping category is Request (in other words, the BRF expression PDCCAT returns the first value for Request (specification in Second Value field).
If only one of the two conditions is not fulfilled, the line with the next highest priority is processed, and so on.
In this example, the question sequence is only determined by way of BRF expressions and their relevant values. No rules have been stored.
Example in the Line of P&C Insurance:
You want to store several question sequences for the Auto: Peril/Object/Location facts capture category. Depending on the relevant context, a certain question sequence should be displayed.
For example, you can make a setting so that variant 1 of question sequence Origin of Loss/Theft (technical key D01) is always shown at runtime if the following condition is fulfilled:
- Rule QUES1 returns the value TRUE
If the rule returns the value FALSE, the line with the next highest priority is evaluated, and so on.
In this example, the question sequence is only determined by way of the relevant rules that have been stored. No BRF expressions (or relevant values) have been stored.
History
Last changed by/on | SAP | 20110901 |
SAP Release Created in |