Understanding Consumer Product Eligibility Criteria

The operands to be compared by consumer product eligibility criteria rules are identified using characteristic types. The characteristic types must have a characteristic entity of Consumer Product Eligibility Operand. The value of these characteristics are populated by the Operands algorithms that are defined on the related Consumer Contract Type’s business object. The base product provides Consumer Contract Type (BO) – Operands algorithm 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 Contract Type (BO) – 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 eligibility criteria rule.

The comparison results define what action should be taken when the criteria rule is applied. If the comparison is true or false, the result can be that the consumer product is eligible, the consumer product is not eligible 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 is eligible, the consumer product is not eligible, the next eligibility rule should be checked or an error should be generated.