Previous	Next		Contents	Index	Navigation		Library

Remember from Arranging Revenue Classes into a Hierarchy that you arrange revenue classes into a hierarchy. When matching the revenue class on a compensation transaction to a class on a salesperson's compensation plan, Oracle Sales Compensation uses this hierarchy to determine whether the class of the transaction rolls up in the hierarchy to any on the plan.

For example, in the PC revenue class, Global Computers compensates a field representative in Territory 4 only for sales of the Sentinel Multimedia PC, while compensating the Territory 4 manager for any type of PC sale (Figure 7 -5). When the Territory 4 salesperson sells a Sentinel Multimedia PC made-to-stock, Oracle Sales Compensation classifies it into the Sentinel_MM_Made-to-Stock class. Because this class rolls up in the revenue class hierarchy to the broader PC revenue class, Oracle Sales Compensation compensates both the Territory 4 salesperson and manager, if Global decides to roll up the sales credit (see How Does a Salesperson Hierarchy Work? for more information on rolling sales credit up the salesperson hierarchy).

In the Plan Elements window, Global assigns the Sentinel_MM_MTS class (and other classes) to the field salesperson's plan and the PC (and other classes) to the territory manager's plan.

Attention: Because Oracle Sales Compensation uses the revenue class hierarchy to determine if the class of the transaction matches a parent class on the salesperson's plan, ensure you do not assign two classes from the same rollup chain in the hierarchy. For example, if Global assigns both the Sentinel_MM_MTS and the PC revenue classes to the field PC salesperson's plan elements, Oracle Sales Compensation cannot find a unique match between the revenue class on the transaction and one on the plan.