Understanding Consumer Product Component Eligibility Criteria

A consumer product component eligibility criteria rule requires the following components:

  • Operand to be compared

  • Comparison operator

  • Comparison value

  • Comparison results

The operands to be compared by consumer product component eligibility criteria rules are identified using characteristic types. The characteristic types must have a characteristic entity of Consumer Product Comp Eligibility Operand. The value of these characteristics are populated by the Contract Operands and Location Operands algorithms defined on the Consumer Product business object. The base product provides a Consumer Product (BO) – Contract Operands algorithm type that sets a characteristic value to indicate if the customer is or will be on autopay. Additional algorithms may exist for your implementation. To see the available algorithm(s), search for algorithm types of the Consumer Product (BO) – Contract Operands algorithm entity in the application.

The comparison operator can be one of the following: <, <=, <>, =, >, >=, Between, In or Is Blank.

The comparison value is recorded in the consumer product component eligibility criteria rule.

The comparison results define what action should be taken when the criteria rules is applied. If the comparison is true or false, the result can be that the consumer product component should be applied, the consumer product component should not be applied or the next eligibility rule should be checked. If there is insufficient data, that is the operand to be compared was not found, the result can be that the consumer product component should be applied, the consumer product component should not be applied, the next eligibility rule should be checked or an error should be generated.