Dynamic Value Help with BRFplus

Definition

You can use rules with the value help type to model a context-dependent value help. We recommend using a corresponding rule for dependencies with one or more different configuration attributes.

In the case of simple value helps without dependencies, such as checkbox fields, we recommend using data elements with the corresponding domain definitions.

The following table contains an overview of the characteristics of a dynmaic value help using BRFplus:

Application usage	CV = Dynamic value help
Reference object / cardinality	Attribute / 1:n
Versioned	Yes
Redefinition	Yes
Implementation class	CL_CRM_ISU_BRF_APPL_USAGE_CV
Inbound parameter	Variable according to the context generated
Return value	A table containing all admissible value help entries

Expression Type for Function: Decision Table

Generate an entry in the decision table for every admissible value to ensure that the BRF application returns the required result:

Column	Description	Possible Entries	Data Element	Comment
Condition
Such as attribute X
Result
ISURSLT_KEY	Value - Key	Key value that is suitable for the attribute	CHAR40
ISURSLT_VALUE	Value - Text	Description of the key value (optional)	CHAR80	If the description contains an initial value, the system automatically uses the description from the fixed values table for the assigned data element. If no description is available, the system uses the key and its unit as a description.
ISURSLT_INVALID	Invalid indicator	'X' = invalid ' ' = valid	Boolean value	The column Inadmissible Value can be used to assign a value help description for field values in error messages.
IUR_ICON	Icon	‘icon_alert.gif’	STRING	Is only evaluated in the OData service for the Product Finder and Configurator.
IUR_ADD_INFO	Additional information for the attribute		STRING	Is only evaluated in the OData service for the Product Finder and Configurator.

Note Note

A value help is dynamic if it is dependent on other configuration attributes. You must add attributes by choosing Add Context Attributes. These can come from the current product, a higher-level product or a product determination object.

End of the note.

Note Note

You can also assign expressions to condition columns. If you require parameters for these expressions, such as Become Item GUID, you must first add these by choosing Add Context Attributes. At runtime, the system processes the decision table again if the value of a context attribute in the condition columns in the decision table has changed.

End of the note.

Example

According to the attribute Credit Rating, the value help for the Payment Method attribute offers a variable selection. This means that a new rule of the value help type is defined for the payment method attribute. The system uses the attribute Credit Rating as a context-dependent input parameter and creates the decison table according to this attribute value.

1: Very good credit rating, annual payment method
2: Medium credit rating, monthly payment or advance payment, annual payment method is offered but flagged as inadmissible
3: Poor credit rating, advance payment only

The decison table contains the following values in the example shown here:

Condition - Credit Rating	Result - Value or Key	Result - Value or Text	Result – Invalid
1	ANNUALLY	Annual payment method
2	ANNUALLY	Annual payment method	X
2	MONTHLY	Monthly payment method
2	PREPAY	Advance payment
3	PREPAY	Advance payment