Previous  Next          Contents  Index  Navigation    Library

Defining Multiple-Condition Rules

When you define two or more conditions for a rule, Oracle Sales Compensation processes the conditions as if they were joined by an AND operator. Thus, all conditions you specify for a rule must be true for the compensation transaction to pass the rule.

If any conditions associated with a revenue class can be true for a compensation transaction to be assigned to the class, you can define multiple sibling rules in the hierarchy, one for each condition. Because Oracle Sales Compensation evaluates other sibling rules if a transaction does not satisfy the first rule on a level in the hierarchy, Oracle Sales Compensation processes these rules as if they were joined by an OR operator. When a transaction fails a rule, Oracle Sales Compensation tests other sibling rules from left to right.

For example, suppose that Global classifies products by ID number and introduces new PCs long after its first models have been assigned their ID numbers. Global can enter two rules, and associate the PC revenue class with each of them:

If several revenue classes share multiple conditions, you can minimize data entry by creating a parent rule that includes the shared conditions, and defining only the unique conditions as child rules.

         Previous  Next          Contents  Index  Navigation    Library