TL;DR
SAP SuccessFactors Incentive Management is the HANA-based evolution of Callidus Commissions — same core ICM concepts, new platform architecture on SAP HANA Database.
The platform has five core layers: Plan Administration, Participant Management, Pipeline Processing, Calculation Engine, and Compensation Statements. Every implementation is built around these.
SAP Advanced Workflow is a separate but tightly integrated tool — it sits alongside SAP SuccessFactors IM, not inside it.

SAP SuccessFactors Incentive Management is SAP's cloud-native incentive compensation management platform. Built on SAP HANA Database and delivered as part of the SAP SuccessFactors suite, it handles the full lifecycle of sales incentives: plan design, quota management, transaction processing, calculation, dispute resolution, and compensation statement generation. If you came from Callidus Commissions, the concepts are familiar — the platform is new.

Architecture Overview

SAP SuccessFactors Incentive Management runs on SAP HANA Database in SAP's cloud infrastructure. The core data model uses the CSC_ prefix (vs Callidus's CS_). The calculation engine and pipeline processing are reimplemented for columnar storage performance — what took minutes on Oracle Database runs in seconds on SAP HANA Database at equivalent data volumes.

The platform integrates with the broader SAP ecosystem through SAP Business Technology Platform (BTP): data flows in from SAP S/4HANA or HR systems via BTP integration suites, and data flows out to SAP Embedded Analytics for reporting and SAP Datasphere for enterprise data integration.

Five Core Layers

1. Plan Administration

Where incentive plan logic is defined: plan types (commission, bonus, MBO, SPF), calculation rules, rate tables, attainment tiers, quota structures, accelerators, and plan periods. SAP SuccessFactors IM provides a UI-based plan designer — most configuration is done through the interface, not direct database manipulation.

2. Participant Management

The organisational structure of sales participants: the hierarchy (rep → manager → director → VP), position assignments, territory alignment, quota allocations per participant per period, and plan eligibility. In SAP SuccessFactors IM, participants are managed through the Position hierarchy — different from Callidus Commissions which used a flat participant tree with explicit parent/child relationships.

3. Pipeline Processing

The pipeline is the processing sequence that transforms raw credit transactions into incentive results. Configurable stages execute in order — credit allocation, territory matching, quota attainment lookup, rule application, tier resolution, cap enforcement, and incentive calculation. Pipeline run control is one of the most critical operational skills in SAP SuccessFactors IM.

SAP HANA Database SQL — Monitor pipeline run status
-- Monitor active and recent pipeline runs
SELECT
  r.ID          AS RUN_ID,
  r.PIPELINE_ID,
  r.STATUS,
  r.PERIOD_ID,
  r.START_TIME,
  r.END_TIME,
  SECONDS_BETWEEN(r.START_TIME,
    COALESCE(r.END_TIME, CURRENT_TIMESTAMP))
                AS DURATION_SEC,
  r.ROWS_PROCESSED
FROM   CSC_PIPELINE_RUN r
WHERE  r.START_TIME >= ADD_DAYS(CURRENT_DATE, -7)
ORDER BY r.START_TIME DESC;

4. Calculation Engine

The calculation engine evaluates plan rules against participant results: applies rate tables, resolves tiers, calculates quota attainment percentages, applies multipliers and accelerators, enforces caps and draws, and produces the final incentive amounts. Results land in CSC_RESULTS and child tables.

SAP HANA Database SQL — Query calculation results
-- Get detailed results for a participant's period
SELECT
  p.NAME              AS PARTICIPANT,
  cp.NAME             AS PLAN_NAME,
  r.PERIOD_ID,
  r.RESULT_AMOUNT,
  r.INCENTIVE_AMOUNT,
  r.STATUS,
  q.QUOTA_AMOUNT,
  ROUND(r.RESULT_AMOUNT /
    NULLIF(q.QUOTA_AMOUNT, 0) * 100, 2)
                      AS ATTAINMENT_PCT
FROM   CSC_RESULTS r
JOIN   CSC_PARTICIPANT p  ON p.ID = r.PARTICIPANT_ID
JOIN   CSC_COMP_PLAN  cp ON cp.ID = r.PLAN_ID
LEFT JOIN CSC_QUOTA   q
  ON  q.PARTICIPANT_ID = r.PARTICIPANT_ID
  AND q.PERIOD_ID      = r.PERIOD_ID
  AND q.PLAN_ID        = r.PLAN_ID
WHERE  p.NAME = :participant_name
  AND  r.PERIOD_ID = :period_id
ORDER BY cp.NAME;

5. Compensation Statements

The end output: compensation statements visible to each participant showing what they earned, how the calculation was done, and a breakdown by plan component. Statement generation is a pipeline stage itself — and statement formatting is one of the most common customisation requests in any implementation.

SAP HANA Database: Key Tables

TablePurposeCallidus Equivalent
CSC_PARTICIPANTParticipant/position master dataCS_PARTICIPANT
CSC_COMP_PLANIncentive plan definitionsCS_COMP_PLAN
CSC_RESULTSPipeline calculation resultsCS_RESULTS
CSC_QUOTAQuota allocations by participant/periodCS_PLAN_PARTICIPANT
CSC_PIPELINE_RUNPipeline run audit logCS_PIPELINE_RUN
CSC_CREDITInput credit transactionsCS_CREDIT

Integration Ecosystem

SAP SuccessFactors Incentive Management does not operate in isolation. The ecosystem around it is part of what you're implementing:

  • SAP Advanced Workflow — workflow automation and approval processes. Tightly integrated, runs alongside SAP SuccessFactors IM. Uses Groovy scripting for custom logic.
  • SAP Embedded Analytics (part of SAP Analytics Cloud) — built-in reporting and dashboards on SAP HANA Database data. The primary reporting layer for most implementations.
  • SAP Crystal Reports — pixel-perfect report output, often used for compensation statements and formal reporting requirements that need precise layout control.
  • SAP Datasphere — enterprise data integration layer. Used when SAP SuccessFactors IM data needs to be combined with data from other systems (CRM, ERP, HR) for unified analytics.
  • SAP Joule — the AI copilot layer. Beginning to add AI-assisted query, anomaly detection, and natural language interaction capabilities to SAP SuccessFactors IM.
💡The most common implementation mistake: Treating SAP Advanced Workflow as a minor configuration task. It is a separate product with its own design, testing, and deployment lifecycle. Scope it as its own workstream — not as a sub-task of SAP SuccessFactors IM configuration.