Previous	Next		Contents	Index	Navigation		Library

Each rule comprises one or more conditions. These conditions specify the characteristics a transaction must have to classify into a given revenue class. You associate a rule with each of your revenue classes, and Oracle Sales Compensation assigns that revenue class when the compensation transaction passes all conditions in the rule. You express each condition in terms of a transaction attribute value.

For example, Global awards compensation based on the type of products or services sold, and thus defines a transaction attribute for product code (Figure 3 - 10). This transaction attribute is represented in the compensation transaction tables as the column PROD_CODE. To determine whether to award consulting revenue, Global checks whether the product code is CON. In Oracle Sales Compensation, Global enters a rule to check for this type of revenue. The rule has one condition: PROD_CODE = CON:

Because Oracle Sales Compensation classifies a transaction by checking values of specific transaction attributes, be sure to specify all attributes you need for classification when you set up transaction collection.