Callidus Commissions: The Oracle-Based ICM Platform

Before there was SAP SuccessFactors Incentive Management, there was CallidusCloud Commissions — and before that, Callidus Software. SAP acquired CallidusCloud in 2018 for $2.4 billion. The Callidus Commissions platform was the centrepiece of that acquisition. Many enterprise customers still run it today, either as a retained legacy system or mid-migration to SAP's HANA-based platform. To work with either effectively, you need to understand where it came from.

What Callidus Commissions Is

Callidus Commissions is an Incentive Compensation Management (ICM) platform purpose-built for enterprise sales organisations. It automates the calculation, payment, and reporting of sales commissions, bonuses, MBOs (Management by Objectives), and other incentive plan types. At enterprise scale, this means processing millions of transactions per period, applying complex plan rules, and generating compensation statements for thousands of participants.

The platform runs on Oracle Database. Its calculation engine, pipeline processing, and data persistence layer are built with Oracle SQL and PL/SQL. The schema uses a CS_ prefix convention for all core tables — CS_PARTICIPANT, CS_COMP_PLAN, CS_RESULTS, and so on.

Core Modules

Callidus Commissions is structured around five core functional areas:

• Plan Management — designing and maintaining incentive plans: rule sets, rate tables, attainment tiers, accelerators, and draw structures.
• Participant Management — the hierarchy of participants (sales reps, managers, directors), their plan assignments, quota allocations, and territory assignments.
• Transaction Processing (Pipeline) — the pipeline that transforms raw sales transactions (orders, bookings, invoices) into calculated compensation results through configurable rule stages.
• Calculation Engine — executes the mathematical rules: quota attainment, tier lookups, multipliers, cap enforcement, draw calculations, and incentive splits.
• Compensation Statements — generates the output documents that sales participants see: what they earned, why they earned it, and how it breaks down by plan and component.

The Oracle Database Schema: Key Tables

Understanding the Callidus Commissions Oracle Database schema is essential for reporting, troubleshooting, and migration planning. These are the tables you'll encounter most:

-- Participants (sales reps, managers, org hierarchy)
CS_PARTICIPANT      (ID, PARENT_ID, NAME, POSITION_ID,
                     STATUS, EFFECTIVE_DATE, ...)

-- Incentive plan definitions
CS_COMP_PLAN        (ID, NAME, PLAN_TYPE, STATUS,
                     EFFECTIVE_START, EFFECTIVE_END, ...)

-- Plan assignment to participant
CS_PLAN_PARTICIPANT (PLAN_ID, PARTICIPANT_ID, PERIOD_ID,
                     QUOTA_AMOUNT, ...)

-- Raw input transactions
CS_CREDIT           (ID, PARTICIPANT_ID, TRANSACTION_DATE,
                     AMOUNT, CURRENCY_CODE, ...)

-- Pipeline calculation results
CS_RESULTS          (ID, PARTICIPANT_ID, PLAN_ID, PERIOD_ID,
                     RESULT_AMOUNT, STATUS, ...)

-- Compensation statements
CS_COMP_STATEMENT      (ID, PARTICIPANT_ID, PERIOD_ID, STATUS)
CS_COMP_STATEMENT_LINE (STATEMENT_ID, LINE_TYPE,
                         DESCRIPTION, AMOUNT, ...)

-- List all Callidus tables with row counts
SELECT table_name,
       num_rows
FROM   user_tables
WHERE  table_name LIKE 'CS_%'
ORDER BY num_rows DESC;

-- Find all columns in a specific table
SELECT column_name, data_type,
       data_length, nullable
FROM   user_tab_columns
WHERE  table_name = 'CS_RESULTS'
ORDER BY column_id;

-- Inventory all PL/SQL objects
SELECT object_name, object_type,
       last_ddl_time
FROM   user_objects
WHERE  object_type IN (
  'PACKAGE', 'PROCEDURE',
  'FUNCTION', 'TRIGGER'
)
ORDER BY object_type, object_name;

The Calculation Pipeline

The Callidus Commissions pipeline is the sequence of processing stages that transforms input transactions into compensation results. Each stage applies rules in order: credit allocation, quota attainment calculation, tier/rate lookups, multipliers, caps, and finally incentive calculation. The pipeline is configurable — implementation teams define the stages and their rule logic.

Pipeline runs are logged in CS_PIPELINE_RUN and step-level detail in CS_PIPELINE_STEP_LOG. When calculations produce unexpected results, the first place to look is the pipeline run log — it shows you exactly which rules fired, in what order, and what data they operated on.

Callidus Workflow: The Precursor to SAP Advanced Workflow

Callidus had its own workflow engine before SAP acquired it — used for plan approval processes, quota disputes, and compensation adjustments. This workflow engine was rebranded and extended as SAP Advanced Workflow after the acquisition. The scripting language it uses, Groovy, carried through from the Callidus era.

If you're on a legacy Callidus Commissions instance, your workflow configuration and any Groovy scripts in it will migrate to SAP Advanced Workflow when you move to SAP SuccessFactors Incentive Management. Some scripts migrate cleanly; others reference Callidus-specific APIs that no longer exist in the SAP version and need rewriting.

What Carried Over to SAP SuccessFactors IM