Pricing with BRFplus
Definition
You can use the price determination rule to define prices for utilities products dynamically and according to other attribute values. You can record one active rule only for pricing in the product. You can only define and execute pricing using BRFplus if you have selected the price source BRFplus
in the product. Prices are made available using the price object in the Product Finder and Configurator.
The following table contains an overview of the pricing characteristics:
Application usage |
PD - Pricing |
Reference object / cardinality |
Product / 1:1 |
Versioned |
Yes |
Redefinition |
No |
Implementation class |
CL_CRM_ISU_BRF_APPL_USAGE_PD |
Inbound parameter |
Variable according to the context generated |
Return value |
Table with DDIC reference type CRMT_ISU_PRC_COMPONENT_DATA_T |
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 |
Attribute used as the basis for defining the field value |
|||
Boolean expression |
Applies or does not apply |
|||
Result |
||||
COMPONENT |
Price component type |
Price component types that were defned in Customizing. |
CHAR (4) |
You can define the components using the transaction under |
COMPONENT_NO |
Price component number |
Sequence number that can be determined across several rows for a price component type |
NUMC (3) |
|
VALID_FROM |
Valid from |
DATS (8) |
Date from which the price is valid |
|
VALID_TO |
Valid to |
DATS (8) |
Date to which the price is valid |
|
COMP_VALUE |
Price |
DF34_DEC (31) |
||
COMP_CURR_KEY |
Currency |
CUKY (5) |
||
COMP_QUANTITY |
Quantity |
DEC (31) |
Quantity basis for the price, such as a scale limit |
|
COMP_UNIT_KEY |
Unit |
CHAR (3) |
Unit of measure |
|
PRICE_UI_TEXT |
Price as a text to be displayed on the UI |
CHAR (40) |
Prepared price for display, for example with currency information or detailed information about the price |
|
TEXT |
Long text that describes the price component |
CHAR (255) |
If no text is determined, the description of the price component type from Customizing is displayed here. |
Note
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.
Example
The price Agreement Charge
is determined according to the automatic debit
payment method. The Agreement Charge
was defined in Customizing as price component type AGEB
. If the payment method automatic debit
is chosen, the charge is only $9.90 intead of the standard §29.90. The system uses the attribute automatic debit
as a context-dependent input parameter and creates the decison table according to this attribute value.
Generate an entry in the decision table for every admissible value to ensure that the BRF application returns the required result:
Condition - Automatic Debit |
Result - Value or Key |
Result – COMPONENT |
Result - COMP_VALUE |
Result - PRICE_UI_TEXT |
‘ ‘ |
AGEB |
29,90 |
$ |
$29.90 - Standard charge |
‘X’ |
AGEB |
9,90 |
$ |
$9.90 EUR - Reduced charge due to automatic debit |