Defining Rule Attributes
To define classification rule attributes:
1. Navigate to the Rule Attributes window.
By default, choose Classification Rules from the Setup menu, choose Rules, select a rule in the list of children and choose Rule Attributes.
The Rule Attributes window for this rule opens. The child rule you selected appears in the Current Rule field.
2. For Revenue Class, enter the name of the revenue class associated with this rule.
Choose a revenue class from the list of values. A rule may or may not have a revenue class. If the rule does not have a revenue class, then its children rules must define the revenue class. If a rule has a revenue class, then the revenue class will be assigned to the transaction only if none of its child rules match the transaction.
When classifying a transaction, if the compensation transaction passes this rule, Oracle Sales Compensation evaluates children rules, attempting to obtain the most granular revenue classification possible. If no children rules are satisfied, Oracle Sales Compensation assigns the revenue class you specify in this field.
Suggestion: If possible, assign a revenue class to every rule in the hierarchy so that Oracle Sales Compensation is always able to assign a revenue class to each compensation transaction. In some cases, however, you might need to associate a revenue class with only the last in a series of rules the compensation transaction must satisfy. See Defining Multiple-Condition Rules for more information.
3. Enter one or more conditions that characterize the revenue class.
Enter one condition per line, providing the following information:
User Column Name: Enter the name of the column in the compensation transaction tables that stores the attribute.
Hierarchy: Enter the name of the hierarchy that the condition is based on. Oracle Sales Compensation lets you define the conditional value of an attribute in terms of its ancestor values in a hierarchy you define.
For example, for its Consulting revenue class, Global enters PROD_CODE in the Attribute field and CON in the Value field.
- Specify one of the following choices from the alternative region:
Low and High Values: This choice allows you to enter a range of values for the attribute by entering values in the Low Value and High Value fields.
For example, suppose Global's identifies products in its PC line by numbers instead of alphabetic codes. If all products in the Multimedia PC line have numbers from 1201 to 1600, Global enters PROD_CODE in the Attribute field, 1201 in the Low Value field, and 1600 in the High Value field. Any product code within the range--including the low and high value--satisfies the condition.
Hierarchy Values: Selecting this option allows you to enter the value in the hierarchy you want to match. The fields that appear are Hierarchy and Hierarchy Values. If the value of the transaction attribute rolls up the hierarchy to the value you specify, the compensation transaction satisfies the condition.
One Value: Specify the exact value the attribute must have to satisfy the condition in the Value field.
Not: Specify the inverse of a value you defined in one of the previous three ways by checking Not. The compensation transaction satisfies the condition if the attribute is not equal to the specified value, is not between the range of values specified, or does not roll up to the specified ancestor value.
If you need to define more than one condition for the rule, see Defining Multiple-Condition Rules for information on how Oracle Sales Compensation processes multiple conditions.
4. After you define all conditions for a rule, define the sibling and child rules.
5. Navigate to the Classification Rules window
By default, choose Classification Rules from the Setup menu.
When you add rules and revenue classes, you must synchronize the new rule and revenue class definitions before they can be used in compensation plans. You do not need to synchronize if you only rearranged the rules.
Module Status displays either SYNCHRONIZED if the currently defined revenue classes and rules have been synchronized, or UNSYNCHRONIZED if you have made changes in your definitions since they were last synchronized.
7. Save your work and exit the window.
Note: To make sure that your classification rules are applied to transactions, you must check the Classification Rules check box in the Transactions window. See Adding Fields to the Transactions Form to Apply Classification Rules: page .
