Calculating Results in SAP Incentive Management

Objective

After completing this lesson, you will be able to calculate results in SAP Incentive Management.

About the Pipeline

The processing engine is called the Pipeline. This engine performs tasks to process compensation, import data, create payments and balances, and many more tasks. Running a pipeline is key to compensation and generates Dashboards, Reports, and other results.

The Pipeline should be run consistently and in sequence with other tasks. For example, an organization may wish to do the following:

  • Import data from source systems daily at 11 PM local time.
  • Run Compensate and Pay daily at 11:30 PM local time.
  • Update data in Dashboards weekly.
  • Post payments and balances monthly, ten days after the end of the period.

The Pipeline engine is used to perform the following tasks:

  • Run a Compensation Calculation for All Sales Deals calculates payee payments and balances. This is often called the Calculation and is the most common type of Pipeline.
  • Import Data from Stage validates and transfers data from staging tables to production.
  • Import Plan Data imports plan and plan-related data from an XML file. This is often done to move new plan designs from one environment to another.
  • Purge Import Data clears a batch of data records from the staging tables.
  • Approve Calculated Data creates a new dataset that can be leveraged in dashboards.
  • Purge Approved Data deletes data from the Approve Calculated batch.
This screenshot shows an example using the pipeline.

In this course, we will focus on the first task: Run a Compensation Calculation for All Sales Deals. For simplicity, we will refer to this task as the Calculation.

Stages of Compensate and Pay 

The first four stages of the Calculation are generally run together as a sequence called Compensate and Pay. These four stages begin with transactions and process the plan rules to produce trial payments and balances. The four stages of Compensate and Pay are:

  • Classify: This stage compares transaction fields to the classifiers we set up in the category hierarchies. The transaction is classified when there is a match between a transaction field and a classifier. The transactions are grouped based on transaction entries that match the classifiers.
  • Allocate: Classified transactions are processed by credit rules using direct transaction assignments, territory requirements, conditions, and roll relationships to allocate credits to Positions. Primary Measurements then aggregate Credits.
  • Reward: Secondary Measurements are calculated from previously calculated measurements or other compensation plan elements. Incentive values are determined, and deposit amounts are created and marked with deposit release information.
  • Pay: Balances from prior periods are applied to the current balance, and payments are generated.

    At this point, this is only a Trial payment. This is because Compensate and Pay is usually run multiple times during the period, so we are not ready to mark the amount as permanent.

    This diagram explains the stages of Compensate and Pay.

Post and Finalize Stages

Post and Finalize are additional calculation stages that mark calculations from the Pay stage as permanent and close the period.

During the Post stage, payments and balances from the Pay stage are permanently stored. Each posted payment represents a payout to a participant. This stage is generally run only once at the end of the period, although it can be run multiple times if needed.

Finalizing a period stops any new compensation from being paid in the current period. Further transactions, credits, or deposits can be processed in a finalized period, but any values that are calculated will be marked as a balance for payment in the next open period.

Both Post and Finalize have an Undo option. However, it’s important to be careful with this feature, as it only affects the most recent Pipeline run.

This screenshot shows the Finalize and Post menu options.

Compensation Calculation Results

The calculation is typically run at least once per calendar period. This generates results data that can be viewed for each phase based on compensation processing for each period. Using the associated results workspaces, you can track compensation results from transactions to payments for specific periods.

Once a calculation is run, the Pipeline Details pane displays a summary of results and information regarding Stage Statistics, Errors, and Logs.

This screenshot shows an example of calculation results.

Calculation Results Workspaces

Each type of compensation rule has its own results workspace, which is populated with the output for each Position assignment for the period. You can see the results workspaces under the Calculations menu.

This screenshot shows the calculation results workspace options.

Calculation Output Example: Credit Rule

Let’s look at an example of how the credit rule returns a set of results in the Credits workspace.

Amy Whitton made three sales, each of which came in as a transaction preassigned to her Position, with a credit type of Product Revenue. The Credit Rule generated three credits, each with the output name and credit type we configured in the credit rule and a value that reflects the original transaction value. The details in the lower pane reflect all the information about the credit, which can then be used as input for the rest of the rules in the plan.

This screenshot shows an example of a credits workspace.

Summary

  • A Pipeline is a processing engine that performs tasks to process compensation, import data, create payments and balances, etc. Running a pipeline is key to compensation and generates Dashboards, Reports, and other results.
  • One of the key tasks the Pipeline engine is used to perform is to Run a Compensation Calculation for All Sales Deals, also referred to as Calculation.
  • The first four stages of the Calculation (Classify, Allocate, Reward, and Pay) are generally run together as a sequence called Compensate and Pay. Compensate and Pay is usually run multiple times during the period, so the payment is not considered permanent yet.
  • Post and Finalize are additional calculation stages that mark calculations from the Pay stage as permanent and close the period.
  • Each type of compensation rule has its own results workspace, found under the Calculations menu.

Decisions Checklist

Based on the content in this section, please review the list of implementation decisions your company may need to make before implementation begins and discuss them with your stakeholders, project team, and SAP implementation consultants. In this way, you will be better prepared to begin the implementation.

  • How often will you run the calculation?
  • Will you run the calculation for all payees simultaneously, or do you need to use a different schedule based on region, line of business, or other criteria?
  • At what point in the compensation period are payments posted?