About Data Collection for Oracle Sales Compensation
To calculate a compensation payment, you need to obtain different kinds of data--for example, the salesperson's name, the amount of the sale, the sale date, and other information. Just as you might gather this data from billing or receivables departments today, Oracle Sales Compensation obtains the information from applications that perform these functions, letting you define what data you need and where the data is stored (Figure 4 - 1).
The nature of the sales task varies highly from sales organization to sales organization, causing companies to compensate salespeople in different ways. For example, one company might award compensation credit to salespeople based on the type of product sold, while other companies compensate based on customer account or the territory where the sale was made, or some other combination of information.
Because companies use different criteria to compensate salespeople, the data each company requires to determine whether to award a compensation payment also varies. For example, organizations that pay salespeople based on product type need to collect data on product types when a sale is made. Companies that pay compensation based on the customer to which the product was sold need to collect data about the customer account for each sale. A company that pays salespeople by both criteria needs to collect both types of data.
To set up Oracle Sales Compensation for collection of compensation data:
1. Define the set of books for the Oracle Sales Compensation collector instance.
2. Define what data your organization needs to calculate a compensation payment. You specify this data by defining a compensation transaction, or the smallest logical unit of data on which your organization can calculate compensation.
3. Define which sources you want to collect the data from--Oracle Receivables or a foreign source. You specify the source documents (such as invoices) you want to base compensation payments on. You also indicate the mapping between source transaction columns and sales compensation columns.
4. Make choices about collection processing. For example, you define how many compensation transactions you want to collect at one time, whether you want to be notified of new transactions, and other processing options.
