5 MARCO REFERENCIAL
5.1 REFERENTE TEÓRICO
5.1.1 Salud Ambiental
The process of calculation comprises three main sections, as follows.
The Rollup Phase
During the Rollup phase, Oracle Incentive Compensation runs a process to determine all resources who should receive credit for a transaction based on the rollup date, and the resource hierarchy effective for that date. For every credit receiver, Oracle Incentive Compensation creates a new system-generated transaction and the lines are marked as Rolled Up.
Multiple resources can receive credit for the same transaction. For example, a sales manager may receive sales credit for his subordinate's transactions. If you choose to compensate multiple resources for the same transaction, you must organize your compensation groups into a hierarchy to specify the relationships among the credit receivers in your sales force.
When transactions are processed with a hierarchy in effect, resources in parent
positions automatically receive all of the sales credit applied toward resources in child positions that report to them, regardless of product. This roll-up credit is also called indirect credit.
When Oracle Incentive Compensation allocates sales credit to multiple credit receivers, each person receiving credit for the transaction receives 100% of the sales credit.
For example, in a hierarchy, three salespeople report to a manager; the manager reports to a director. The first resource receives $10,000 for an invoiced transaction, the second receives $5,000 for a different transaction, and the third resource receives $7,000 for another transaction. Each resource receives sales credit for the individual transaction that results from their work. However, if Managerial Rollup is checked for rollup, the salespeople's manager receives $22,000 in indirect rollup sales credit.
In addition to the three invoices mentioned, a fourth invoice gives the manager $15,000 in direct sales credit. The salespeople reporting to the manager do not receive any credit.
The manager's boss, the director, is at the top of the rollup hierarchy. The director receives a total of $37,000 in indirect rollup sales credit, including both the Manager's direct $15,000 credit and the $22,000 total for the three salespeople that rolls up to him through the manager.
What to Do if Rollup Fails
If Rollup fails, verify the following:
• The resource on the transaction is assigned to a compensation group.
• The group the resource is assigned to has the usage of Sales Compensation.
• If the resource on the transaction belongs to more than one compensation group, the profile OIC: MULTI_ROLLUP_PATH is set to Y (not Yes or y).
The Population Phase
During the Population phase, Oracle Incentive Compensation identifies the appropriate plan elements that are associated with the resource's compensation plan that have been allocated to the transactions. The application attempts to match transactions with the Plan Elements for the credited resources and if the match is successful, the transaction is populated.
The application performs the following checks during the Population phase. It
• Identifies the compensation period
• Identifies the plan element and assigned Sales Role and Compensation Plan (based on Plan Element to Product Mapping)
• Uses the Product Hierarchy (traversing the hierarchy upwards to determine the most general product)
• Handles revenue class overlap (The system generates a duplicate transaction line record for any transaction that is associated with more than one Plan Element due to revenue class overlap.)
• Handles multiple roots (The system creates a system-generated duplicate transaction line record for any transaction that is associated with more than one sales role within a compensation group.)
• Fails population. If the transaction does not find a matching revenue class in the compensation plan for the credited resource then no compensation can be calculated. Oracle Incentive Compensation displays a status of Failed Population (XPOP) in the transaction status column.
What to Do if Population Fails
1. Check if there is a role and in turn there is a compensation plan assigned to the resource on the date of the XPOP transaction. If there is no role or compensation
plan assignment and this is not intended, then assign the appropriate role and compensation plan to the resource.
2. If there is a compensation plan assigned to the resource, check whether the compensation plan has a COMPLETE status.
3. If compensation plan is complete, then check whether any of its plan elements effective on the date of the transaction has a matching revenue class with the transaction's revenue class. Whether there is a revenue class match is determined by the revenue class hierarchy. If the revenue class on the plan element is a parent revenue class of the revenue class of the transaction, it is a match.
4. If there is a revenue class match, then check and make sure that the involved revenue classes exist in the revenue class hierarchy. If not, add them to the revenue class hierarchy.
5. Make sure that the Revenue Class that the transaction was assigned is assigned to at least one Plan Element that is included in the resource's compensation plan.
6. Make sure that the Sales Compensation role that is assigned to the resource has either the Member or Manager box checked.
7. Make sure the resource's Sales Compensation role is a Group Member role for the date of the transaction.
8. Make sure that the group the resource is assigned to has the usage of Sales Compensation.
9. After the above setup is validated, run calculation again.
The Calculation Phase
During the Calculation Phase, Oracle Incentive Compensation performs the calculation on all transactions within the specified parameters. It evaluates the expressions defined on a given formula, looks up the rate from the rate table, calculates the compensation amount, and updates the transactions and balance tables with the results. Oracle Incentive Compensation displays a status for calculated transactions in the transaction status column.
The Calculation process calculates compensation based on the Calculation Rules (defined in Plan Elements). Calculation Rules include Commission Rate (defined in the Rate Table), Accelerators (earnings factor, multiplier, and transaction factors),
Accumulation or Non-Accumulation, Split or Non-Split, Interval-to-Date Quota or Annual Quota, Individual or Group By. If the application is unable to calculate the compensation for the transaction, the transaction is marked as 'XCALC' (Failed Calculation).
What to Do if Calculation Fails
If transactions failed to be calculated, Oracle Incentive Compensation displays a status of XCALC for those transactions. Check the following things if calculation fails for a transaction:
• The value passed to the Rate Table from the Input Expression is included in the Rate Table. (To prevent this problem always make the first tier of the rate dimension 0 to X instead of starting it as X to 10000, for example).
• No values in the Formula are divided by zero.
• All columns used in the formula to calculate are populated for the transaction.
• The formula packages are valid (regenerated).
• The number of inputs to the formula match the number of dimensions of the rate table.
• The type of formula input matches the rate table dimension type.