Previous | Next | Contents | Index | Navigation | Library |
To pay sales compensation, your compensation department probably needs to:
During setup you define the structure of a compensation transaction, which tells Oracle Sales Compensation what information you need to collect to calculate compensation and where in the database this information is stored.
Oracle Sales Compensation supports two sources of transactions:
When you run a process to collect compensation transactions, among other information, Oracle Sales Compensation collects the following from the source transaction:
During setup, you categorize your sales revenue into revenue classes, which specify which types of revenue warrant compensation in your organization. When you run a process to classify transactions, Oracle Sales Compensation uses a set of conditions you define to determine the class to which the transaction belongs.
After you define revenue classes, you assign them to a compensation plan and assign the plan to a salesperson. Oracle Sales Compensation awards compensation if the revenue class of the transaction matches a revenue class assigned to the credit receiver's compensation plan.
Oracle Sales Compensation uses a predefined formula and compensation terms defined in the credit receiver's compensation plan to calculate the compensation amount.
When the compensation earnings have been calculated, you run a process to submit payment to the payment processing application of your choice.
The following figure shows an example of this process for a software invoice at Global Computers, Inc., a fictitious personal computer company:
When you pay compensation, you run each of the processes shown in Figure 1 -1. Each process is driven by information specific to your sales operations, and thus has some corresponding setup steps. How these steps are organized is explained next.
Previous | Next | Contents | Index | Navigation | Library |