You can group transactions into physical batches to improve performance. Use any of these methods for grouping transactions:
The application can intelligently determine the calculation batches based on the number of credits to be processed. It determines the optimal number of batches and batch sizes (number of participants) to be included in each calculation batch, based on the volume of credits to be processed and the number of included participants. Here's how to enable this method:
In the Manage Parameters UI, the Batch Processing Parameters region, select the Use batch information provided at the transaction level option for Classification and Crediting Batch Processing and for Rollup and Calculation Batch Processing. The application preserves the batch number as it moves each transaction from one entity to another, for example, from transaction to credit or credit to earning. Note: Ensure that transactions belonging to the same participant all have the same batch number. Use the Manage Parameters task in the Setup and Maintenance work area to set the Number of Batches parameters. Select the Use batch size determined by the application option for these parameters:
To balance the processing of workloads, administrators can configure classification, crediting, rollup, and calculation processes to group participants by transaction volume into specific numbered batches. This feature maximizes processing performance even with skewed transaction data or large volumes of data. For example, you can put participants who receive hundreds of thousands of credit transactions every week into separate batches, one for each participant, for processing. You can then put other participants who receive fewer transactions together into another batch. If you provide a batch number for a participant, then the application uses that batch number to group participants. All participants that have the same batch number are grouped together for processing. If you don't provide a batch number for all of the participants, then the application divides the transactions for the remaining unnumbered participants equally into different batches. The Number of Batches value determines the number of those batches. Here's now to provide a batch number for a participant:
Page 2The application populates the Changed Events Log with all plan and plan assignment changes. Logging these change events lets you run the calculation process for only the participants that require it. You can check the log to see the list of events and all participants affected by change events to get an idea of how long a calculation will take. This table shows the four levels the application can track changed events for with descriptions of each.
In the log table, the REVERT_TO_STATE column tells the calculation process what state it must revert transactions to.
Page 3When you create a calculation request, you specify process parameters including for which participant to calculate earnings. Make your request at a time when others aren't making changes to compensation plans to be calculated. Use the Manage Calculation Processes task in the Credits and Earnings work area to create calculation requests. When you submit calculation, it implicitly decides whether to run calculation in incremental or full mode for a specific participant. If you select calculation for all participants or for participants in a plan, then the calculation not only reverts and re-runs for the participants in the Change Events Log, but it also updates the earnings for the rest of the participants. This ensures that earnings are updated, even for participants who have changes affecting their earnings that aren't recorded in the change log. These two options are recommended as best practice selections. If you select calculation for all participants in notify log, then the calculation only runs for the participants in the Change Events Log. Use the Calculate For parameter to specify the participants to include.
For any participant specified for calculation, you can select Include Reporting Participants. For participants with this option selected, the calculation request also includes all of the participants in the participant hierarchy that report up to the specified participant. Page 4Incremental calculation uses all of the change events for the Compensation Plans and Participant Assignments work areas logged in the CN_TP_NOTIFY_LOGS_ALL table. This table lists the logged change events for the Compensation Plans work area, including the involved attributes, operation, and the revert status of the log entry.
This table lists the logged change events for the Participant Assignments work area, including the involved attributes, operation, and the revert status of the log entry.
Page 5The calculation process uses classified credit transactions and valid incentive compensation plans and plan components to calculate participant earnings transactions. Compensation plan configurations, such as whether to true up earnings and to calculate incentives for each event or per interval, affect calculation processing. Configure compensation plans, including plan components and performance measures, in the Compensation Plans work area. Parameters that you set when creating the calculation request in the Credits and Earnings work area and transaction status constrain the classified credit transactions used during processing. The calculation process consists of two phases, Eligibility and Calculation. Before beginning the Eligibility phase, the calculation process updates each entry in the Changed Events Log with these values:
The process only runs for the incomplete log records with the corresponding scheduled process ID, ensuring that it doesn't include any changes made during the current run. The Eligibility phase performs these actions:
The Eligibility phase doesn't identify the plan component and measure for any transactions where you elected to skip the Eligibility phase. The process assumes that you provide the plan component name. The Calculation phase computes the measure attainments and plan component earnings for all eligible transactions. It stores the intermediary and final calculation results, such as formula output, attainment or earning, input achieved, rates and rate tiers, for each earnings transaction. This information is essential for transaction-to-payment audits and reporting purposes. The Calculation phase does these actions:
This table lists the actions that the Calculation phase performs for plan components based on the Calculate Incentive selection.
Calculation doesn't maintain any direct link between earnings and credit transactions. Instead, you use the Earning Basis selections to edit the measures while associating them with the plan component. The application links the earning and credit records using this logic:
When calculation processing completes, the process updates all of the log records with the corresponding concurrent request ID and the status to Complete. Page 6
Alex Anders 25,000 50 Western Audio 1.00 250 Haley King 25,000 50 Western Audio 1.00 250 Robert Rivera 50,000 100 Western Audio .25 1.25 Andrew Brown 25,000 100 Western Audio Video Not applicable Not applicable Andrew Brown 25,000 100 Western Audio Video Not applicable Not applicable Lily Cox 25,000 100 NA Audio Video Not applicable Not applicable Lily Cox 25,000 100 NA Audio Video Not applicable Not applicable Richard Barta 25,000 100 NA Audio Video Not applicable Not applicable Richard Barta 25,000 100 NA Audio Video Not applicable Not applicable Page 7When you investigate a dispute, review earnings, or get questions about a credit, you require details. You may have questions about an earning amount. How did it come about? Who was credited? Is the earning from a single transaction or a group of transactions? You can analyze each step of the calculation for an earning in the Calculation Detail UI, available from the Manage Earnings UI. Here are some questions and where you can find answers.
Calculation Detail shows the most recent calculation, not necessarily the calculation when it was paid. Page 8Here are examples of what you can look for if your calculation process runs too long.
Page 9Ensure that you have at least three times the number of batches as workers (or processing threads) to keep all workers busy simultaneously, most of the time.
Start with the recommended configuration and refine the parameters based on your testing results. Page 10You can add only valid plans when creating a calculation request. If a plan later becomes invalid due to changes, then when you submit the calculation request, the request status changes to Failed during validation. The calculation request process log contains a list of the plans that failed validation, so that you can correct the issues and submit the request again. Page 11If the participant isn't the direct participant for a transaction, then the transaction isn't in the list in Manage Transactions. For example, you see a transaction when viewing a participant in Snapshot, but that transaction is gone in Manage Transactions because it's filtered on the direct participant. A direct participant is listed directly on the transaction. Rules use other information on a transaction to credit a participant. That participant isn't a direct participant. Search for the participant under Manage Credits or Manage Earnings to see details on the base transactions where the credited participant isn't the direct participant. Page 12Calculation was run but the earnings you expect to see are missing. In this scenario, the credits associated to the transaction were calculated. Then either a change was made to the same transaction or to its associated credits. If the Revert Transactions process is run, it either deletes the earning records if not paid, or moves the earnings to history if paid. Either way, the Revert Transactions process clears the earnings. The earnings are only recreated if Calculation is run again after the transaction is changed. If Calculation isn't run, the earnings remain missing for that transaction. Page 13The calculation process can fail for a variety of reasons during either the Eligibility or Calculation phase. The calculation process updates the transaction status based on the reason for the failure. Before you submit a calculation request, ensure the following:
Eligibility processing links classified credit transactions to the compensation plan components and performance measures assigned to the specified participants. The process tries to validate invalid plans. If it can't do this, then it does the following:
Here are some typical reasons for an Eligibility phase error:
If the Calculation process fails, then it changes the transaction status to Failed calculation. Check for any recent changes to the plan components or performance measures of the plan being calculated. Are the plan components and performance measures all valid? Fix what you find and then recalculate. Here are some reasons for a failed calculation:
Page 14Credit transactions can fail eligibility validation during processing. The research assistant provides an analysis of eligibility errors and the means to correct errors in the same UI. The Analyze icon in the search results table of the Manage Credits page opens the research assistant.
For example, you can change dates in the Compensation Plan and Plan Components tabs. Use the Performance Measures tab to identify the performance measure that matches the transaction credit category. Page 15The Calculate Incentive Earnings process creates measure attainment records and earnings records for participants. If the process ends with errors or incorrect data, you can follow these solutions to fix it. Verify that you have these prerequisites to running Calculate Incentive Earnings:
Take these steps to resolve the error.
The process succeeded, but the credits are in a state other than Eligible.
The status of the process request is Succeeded, but the earnings in the Manage Earnings page have the status Calculation Error.
The process succeeded and the earnings in the Manage Earnings page have the status Calculated. But your earnings amounts are incorrect.
The process succeeded, but the earnings aren't calculated for a particular plan component.
Page 16The Assign Incentive and Draw Plans task includes activities to create and manage pay groups and payment plans.
This diagram shows that the Assign Draws and Incentives task comes after Model and Configure Incentive Plans and before transaction processing within the Manage Incentive Compensation business process flow. Page 17The payment business process controls how you pay salespeople, including these aspects.
This chart shows the Determine Incentive Payment business process entities and the relationships between them, whether one-to-many, many-to-one, or many-to-many. Use pay groups to define the frequency of payments and gather participants who are on the same payment cycle and sent to the same application. For example, group monthly participant payments as Pay Group A for your payables application and Pay Group B for your payroll application. You must assign participants to a pay group to include them in a payment batch when you run the payment process. You can assign multiple pay groups to a participant, but only one pay group assignment can be active at a time. You create and manage pay groups in the Participant Assignment work area. You can assign a pay group to one or more payment batches, but a payment batch can have only one pay group assigned.
Paysheets are worksheets generated when you create a payment batch. A payment batch contains multiple paysheets, and each paysheet contains this information:
Payment plans contain rules regarding payment draw, draw recovery, and cap amounts to pay to assigned participants. The payment process uses these rules to populate participant paysheets with computed participant payment adjustment amounts against earnings for the period. You can assign multiple participants with a payment plan. You can also assign multiple payment plans to a participant, but only one plan assignment can be active at a time. Page 18Incentive compensation managers and analysts create payment plans in the Participant Assignments work area to provide and recover participant draw payments against actual earnings. Use payment plans to specify when and how much to pay and at what frequency. Prevent negative payments by using a zero minimum amount.
Tip: Individualize draw amount, recovery amount, cap amount, and assignment start or end dates for participants in the Participant Snapshot work area. |