← Interview Prep
● By Company

Know what each company asks.

These are exact question sets from real interviews at each company — organized by round. Walk in knowing their focus areas, their traps, and what level of depth they expect.

Accenture Deloitte Open Symmetry Aspire Digital Datalogics Enquero TCS SAP
Ac

Accenture

Variables & Precedence Pipeline Modes Credit Rules Rate Table vs Lookup MDLT Versioning Formula Functions

Accenture Round-1 is heavily configuration-focused. They want to know if you've actually built plans — not just read about them. Variables precedence, MDLT, and the Rate Table vs Lookup Table distinction come up in almost every round.

Round 1 — 18 Questions
1
Tell me about yourself.
Structure: years of experience → components configured → specific achievements. Keep it under 2 minutes. Have a concise "client system" story ready.
2
What is Quota and where is it used in SAP Commissions?
Attainment tracking tool assigned at position hierarchy level. Referenced in Secondary Measurement Rules and Incentive Rules for attainment-based compensation.
3
What is a Rate Table and where are they used?
Attainment-based stepped/straight commission tables. Restricted to Incentive Rules ONLY. Two-dimensional. Know the function that references them.
4
What information is available on the Organization Dashboard?
Participant overview, position hierarchy, roll relationships, title and plan assignments, version history. Know what each section shows.
5
Explain Variables, their use, and what happens when the same variable is assigned at both plan and title level. Which takes precedence?
The most specific assignment wins. Position overrides Title, Title overrides Plan, Plan overrides Default (variable level). Know all 4 levels and why this matters for commission rate overrides.
6
What are the 4 types of Credit Rules in SAP Commissions?
Two sources (Transaction, Order) × two directions (Direct, Indirect) = 4 combinations. Direct = who made the sale. Indirect = who rolls up in the reporting hierarchy.
7
What is Incremental Pipeline mode? How is it run and what happens when you use it?
Processes only new or changed data since the last run. Faster but can miss edge cases when changes affect previously processed transactions. Know when NOT to use it.
8
What are the stages of pipeline processing?
6 stages in order. Know the input, output, and what each stage produces. Be ready for "which stage runs SM?" follow-up.
9
How do you run the pipeline? Walk me through the steps.
Manage Pipeline → Select period → Choose mode → Choose position scope → Run. Know how to monitor progress and where to find errors.
10
What are the types of pipeline run? Can it be run for a particular position?
Full, Incremental, and Specific modes. Yes, you can target specific positions or position groups. Why would you run for specific positions only?
11
How will you test a rule you just created without running for all positions?
Specific Position mode + test position. Verify the full chain: Credits → Measurements → Incentives → Deposits. Check Research workspace for results.
12
What functions are present in the Formula workspace? Name at least 4–5.
LOOKUP(), DATEADD(), IF(), ISNULL(), SUM(), DAY(), MONTH(), YEAR(), STRING(), SUM PRIOR MEASUREMENT. Know which are used most in production rules.
13
Explain the Pay, Post, and Finalize stages in detail.
Pay = trial payments and balances (temporary). Post = permanently records payments. Finalize = locks the period. After finalize, new pipeline results become balances in next period.
14
What happens when the pipeline runs after a period is already finalized?
New calculation results are treated as incremental balances — they don't overwrite finalized data. The system generates difference amounts that flow into the next open period.
15
For a two-dimensional table, would you use a Lookup Table or a Rate Table?
Depends entirely on the purpose. Rate Table = attainment-based tiers → commission rates. Lookup Table = any 2D value mapping not tied to sales attainment. Key: Is attainment the driver?
16
Can MDLT have versions?
MDLT is created via XML import. Version behavior depends on how effective dates are managed in the import XML. This is a trap — know the exact answer and how it differs from standard Lookup Tables.
17
What are the Global Values in SAP Commissions?
Calendars, Credit Types, Event Types, Earning Codes, Earning Groups, Fixed Value Types, Reason Codes, and Base Unit Types. Know what each one does.
18
What is stepped vs straight commission?
Stepped = different rates for different attainment tiers. Straight = single flat rate on everything. Rate Tables handle both configurations. Know how to build each in a rate table.
De

Deloitte

Pipeline Deep-Dive Pay/Post/Finalize Scenarios Rate Table vs MDLT System Design

Deloitte focuses heavily on pipeline stage mechanics and scenario-based questions. They expect you to have hands-on experience with Pay/Post/Finalize edge cases and be able to design rule solutions from scratch in the interview.

Interview Questions
1
Tell me about yourself and your roles and responsibilities.
Lead with your ICM system overview: what industry, what system architecture, what components you owned. Be specific — don't just list technologies.
2
How would you rate yourself in Data Integration and Configuration?
Be honest but strategic. Deloitte probes whatever level you claim. Have a specific example ready for each area you claim expertise in.
3
Explain all pipeline stages in detail and differentiate each.
6 stages. For each: what is the input, what does it do, what is the output, which tables are populated. Know which stages can run independently and which require prior stages to complete.
4
What is the Pay, Post, and Finalize stage — explain each and differentiate.
Pay = trial. Post = permanent. Finalize = locked. After finalize, new calculations flow as balances to next period. Be ready for "what happens if you run Post twice?" follow-up.
5
Scenario: Jan 2021 Pay/Post/Finalize complete. Payments from Jan still need to reflect in Feb. Step-by-step approach?
Two paths: Unfinalize Jan (risky) or create February adjustment transactions. Deloitte expects you to know the safer production approach and the risks of each.
6
Scenario: Participant joined 1st–15th paid in current month, 16th–30th in next month. What formula and rule?
DAY() function on start date. IF condition. The placement of this logic — Deposit Rule vs Incentive formula — is what they're testing. Know both options and when each is appropriate.
7
What is the difference between Incentive and Commission? Basic Incentive vs Per-Credit?
Incentive = umbrella term. Commission = variable pay per sale. Basic = aggregate from measurement. Per-Credit = evaluates each credit individually against a rate table. This distinction affects how stepped rates work.
8
Where are commissions saved in the system?
Results tables: CS_INCENTIVE, CS_DEPOSIT, CS_PRIMARYMEASUREMENT. Which workspace lets you view these post-pipeline? Which stage populates which table?
9
Can Rate Tables be used in Secondary Measurement (SM) rules?
This is a trap question Deloitte uses frequently. Rate Tables are restricted to Incentive Rules ONLY. The answer is no — and if you say yes, expect immediate follow-up.
10
What is a Rate Table vs MDLT — explain each and differentiate.
Rate Table = 2D, attainment-based, Incentive Rules only. MDLT = multi-dimensional, non-attainment lookup, XML-created. Key: MDLT handles complexity Rate Tables can't — and they test this with follow-up scenarios.
11
Scenario: Table with 3 columns (products, amounts), multiple rows. Use MDLT or Rate Table? Design the incentive rules.
3-column matrix without attainment tiers → MDLT. Create via XML. Reference in Lookup Table Variable. Use LOOKUP() in Incentive Rule formula. Walk through the exact rule configuration.
12
Rate Table and MDLT — when would you choose which? (Deeper follow-up)
Deloitte asks this from multiple angles in the same interview. They want to see you're not reciting — you actually understand the design decision. Have 2–3 real project examples ready.
OS

Open Symmetry

Organization Setup Classification Transactions End-to-End Plan Design

Open Symmetry structures their interview as a practical walkthrough of the system. Organization → Classification → Transactions → Rules. They want to see that you can build a system end-to-end, not just answer isolated questions.

Organization
1
How do you create a position and participant, and what is the recommended way to terminate them?
Manual vs import for creation. Termination: set Termination Date — don't delete. Deletion removes audit history. Keep all records for historical commission calculations.
2
How do you load Organization data and what is the importance of loading order?
Dependencies: Participants first, then Positions, then Title Assignments, then Plan Assignments. Wrong order = foreign key violations and silent data quality issues.
3
What are Roll Relationships and how does a manager get their commission share from subordinate transactions?
Roll Relationships define the credit path between positions. Managers get credit via Indirect Credit Rules that take Direct Credit output as input and roll up via the Reporting roll type.
Classification
4
What are Classifiers and what is their use?
Leaf nodes of the category hierarchy. They are the actual product codes, postal codes, or customer IDs that get matched against transaction fields during the Classify pipeline stage.
5
What is the use of Classification Rules and what are Territories?
Classification Rules live in Root Category and define what transaction fields map to classifiers. Territories group classifiers/categories into named filters used to route credits to positions.
Transaction & Results
6
How do you load, remove, and manage transactions?
Load via VnT or direct file. Remove via Reset from Validate (removes VnT'd transactions) or Research workspace deletion. Know when each method is appropriate and what gets preserved.
7
What is Unfinalized and Unpost? What is the difference between Finalized and Posted?
Posted = permanent payment record (reversible). Finalized = period locked (requires Unfinalize before Unpost). Order matters: Unfinalize → Unpost → reprocess. Know the cascading effects on downstream periods.
8
How do you calculate balances and send them to the next period?
Balances carry forward automatically. Pay stage calculates trial payments and running balances. Finalize locks them. Next period pipeline picks up the balance as the starting point for the earning group.
Plan Design — Walk-Through
9
Walk through building a sample plan with all components (Variables, Rate Table, Quota, Credit Types, Position Groups, Roll Relationships, Earning Codes, Earning Groups).
Open Symmetry expects a complete end-to-end walkthrough. They want to see you can sequence the build correctly and explain the dependency chain between components. This is the final boss question of their process.
AD

Aspire Digital

Credit & Deposit Hold Date Field Semantics Multi-Calendar Plans Project Experience

Aspire Digital asks targeted questions about specific system behaviors that require hands-on experience to answer correctly. Date fields, holds, and calendar usage are their consistent focus areas.

6 Questions
1
What is Credit Hold and Deposit Hold? How are they different?
Credit Hold stops credit generation for a position at the Allocate stage. Deposit Hold places the final deposit payment on hold for manual review at the Pay/Post stage. Different stages, different purposes.
2
What is the difference between Credit Start Date and Processing Start Date on a position?
Credit Start Date controls when credits start flowing TO this position. Processing Start Date controls when the pipeline INCLUDES this position in calculations. Two independent gates that often get confused.
3
How do you use different calendars in a single compensation plan?
Each rule in a plan can reference a different period type. Monthly commission rule + quarterly bonus rule in the same plan. Calendar is assigned at BU level. Know how period types interact at calculation time.
4
How do you import data into Transactions, Organization, and Classification?
Three different paths. Transactions via VnT. Organization via participant/position import workspace. Classification via category import. Different file formats and validation rules apply to each.
5
Can we allocate credit without a position/title assignment? How?
Yes — Territory variable assignment directly to the position. Reference the territory variable in the Credit Rule. Bypasses the standard title→plan assignment path. Useful for specific edge cases.
6
Walk through your project role — SDLC phases, data types, processing frequency, and client system overview.
Structure: requirements → design → config → SIT → UAT → go-live → hypercare. Be specific about data volumes, daily/monthly/quarterly cycles, and which ICM components you owned vs the team.
DL

Datalogics

UNIX Basics PL/SQL SAP Commission Core Custom vs Standard

Datalogics covers all three layers: UNIX shell, PL/SQL, and SAP Commissions. They expect a full-stack practitioner who can work at the backend as well as the configuration layer.

UNIX — Basics
1
What are directories in UNIX? What is bash? What is the directory structure?
Directories are filesystem containers. Bash is the default shell scripting language. Standard structure: /, /bin, /etc, /home, /var, /tmp, /usr. Know what each major directory stores.
PL/SQL — Basics
2
What are default packages in PL/SQL?
DBMS_OUTPUT, DBMS_SQL, UTL_FILE, DBMS_JOB, DBMS_SCHEDULER, DBMS_LOB, UTL_HTTP. Know what each does and when you'd use it in an SAP Commissions backend context.
3
What are exceptions and exception types in PL/SQL?
Predefined (NO_DATA_FOUND, TOO_MANY_ROWS, ZERO_DIVIDE), User-defined, and RAISE_APPLICATION_ERROR. Know the EXCEPTION block structure and when to use WHEN OTHERS.
SAP Commission — Core Concepts
4
What is the difference between custom and core SAP Commission functionality?
Core = standard out-of-the-box features (CMID rules, pipeline, VnT). Custom = Stage Hooks, stored procedures, shell scripts, custom ODI interfaces, custom reporting queries. Know the implications of each on upgrades.
5
VnT process, pipeline types, Stage Hook process, Quotas, Territories, attainment, global settings, administration, role-based security, scripts storage.
Datalogics covers the entire breadth in one interview. Be ready to answer any of these as a quick-fire round. They want breadth first, depth second. Know at least 2 sentences for each topic.
En

Enquero

2-Round Process Pipeline Fundamentals TRACE Tables PMR & GAs Reset Logic

Enquero has a clear 2-round structure: Round 1 tests fundamentals hard. Round 2 goes deep on system internals — TRACE tables, reset logic, and PMR specifics that only practitioners know.

Round 1 — Fundamentals
1
Pipeline stages, modes, Rate Table function, SM stage placement, Quota basics.
Round 1 is a filter round. If you stumble on pipeline stage order, SM placement, or the Rate Table lookup function name — you don't pass. Know these cold before any Enquero interview.
Round 2 — System Internals
2
What is Reset from VALIDATE and Reset from CLASSIFY? What do they each clear?
Reset from Validate removes the VnT'd/imported transaction data. Reset from Classify removes classification results. Know exactly which database tables are cleared by each and whether credits are affected.
3
What are the TRACE tables? Why are they used?
TRACE tables (e.g., CS_CREDITTRACE, CS_PMCREDITTRACE) store the detailed path of how each credit contributed to a measurement. Essential for debugging pipeline results and auditing payments. Know at least 3 TRACE table names.
4
Which rule does NOT have Generic Attributes? Why?
Primary Measurement Rule (PMR) does not have GAs. The reason is structural — PMR aggregates from credits and doesn't carry individual transaction-level attributes. This is a specific trap Enquero uses to separate real practitioners from candidates who've just read the docs.
5
Types of Incentive Rules and their meanings — Per-Credit vs Aggregate.
Per-Credit evaluates each individual credit against a rate table. Aggregate evaluates the total measurement value. Key difference: stepped rates on individual credits (Per-Credit) vs flat rate on total (Aggregate). With real numbers: $10+$20+$15+$25 = different outcomes depending on which type.
6
Requirements gathering, environment setup, KM (Knowledge Management) process.
Enquero Round 2 also tests soft skills. Requirements gathering approach, how you document system knowledge, and how you onboard to a new client environment are all fair game alongside the technical questions.
TC

TCS

Full Breadth Client Communication Requirement Gathering Stage Hooks ODI/VnT

TCS covers everything from "What is a commission?" to Stage Hook implementation. They also heavily test soft skills: can you explain the system to a non-technical business stakeholder and gather requirements from scratch?

22 Questions Across Technical + Soft Skills
1–4
Pipeline stages, Processing Unit (PU) usage, Role/User security, Backend database experience.
TCS starts with quick-fire basics. PU is a specific question — know why PU exists (data segregation for pipeline runs) and how it differs from BU (organizational/administrative).
5–8
Dashboard experience, generating credits without position/title assignment, Rate Table usage, SM stage placement.
The credit-without-title question is a TCS signature question. Answer: Territory variable directly on the position. They want to see you know this workaround from real project experience, not theory.
9–12
Rule creation prerequisites, Roll Relationships for manager credit, What is a Commission, Yearly bonus design.
For yearly bonus: TCS expects you to know SUM PRIOR MEASUREMENT or SUM PRIOR INCENTIVES. They'll probe: "More than one way to do it" — have two approaches ready.
13–17
Identifying credits by purpose, ODI/VnT issue resolution, client system explanation, roles & responsibilities, Stage Hook experience.
Stage Hook is a deep-dive topic for TCS. Have a real example: which stage you hooked, what the script/procedure did, how you tested it. They'll probe until they find the edge of your knowledge.
18–22
Environment setup, convincing clients to use SAP Commission, accommodating requirements from non-technical business users, requirement collection methodology.
TCS soft skill questions are not fluff — they're scored. Have a structured answer for requirement gathering (workshops, current-state analysis, shadow payroll). And for "convincing clients" — lead with TCO and audit trail.
SAP

SAP (Official)

PL/SQL OOP Concepts BULK Collect vs Cursor Pipeline Performance Stage Hooks Transaction Architecture

SAP's own interview is technically demanding. They combine PL/SQL depth with SAP Commissions pipeline performance and configuration. Expect deep follow-up on every answer — they probe until they find your ceiling.

PL/SQL Section
1
Relate OOP concepts to PL/SQL.
Packages = Classes. Procedures/Functions = Methods. Package body = private implementation. Package spec = public interface. Overloading is supported. Encapsulation via package body privacy. SAP expects a clean OOP→PL/SQL mapping.
2
Function vs Procedure — differences, return values, IN/OUT parameters, when to prefer which.
Functions must return a value; procedures don't. Functions can be used in SQL expressions (with restrictions). Procedures are better for DML operations. SAP probes the IN/OUT/IN OUT parameter behavior specifically.
3
What is a Cursor, where is it used, and how?
Explicit vs implicit cursors. FOR loop cursors. OPEN-FETCH-CLOSE pattern. When does cursor processing become a bottleneck and what replaces it?
4
What is BULK Collect? FOR vs FOR ALL? Why use BULK Collect for large data?
BULK Collect reduces context switches between PL/SQL and SQL engines. FOR iterates in PL/SQL (slow for DML). FORALL sends bulk DML to SQL engine in one call (fast). SAP wants specific performance numbers or rationale.
5
What are Collections in PL/SQL?
INDEX BY (Associative arrays), Nested Tables, VARRAYs. Each has different storage model and use case. Essential for BULK Collect and FORALL patterns.
6
Can procedures be used in SELECT queries?
No. Functions can, with restrictions (no DML, deterministic preferred, no transaction control). This is a quick trap question — wrong answer ends the PL/SQL section early.
SAP Commissions — Pipeline Performance
7
Pipeline stages, pipeline modes, incremental mode, rule performance optimization, PU and BU usage.
SAP expects you to know which log to look at for rule timing, how to order rules for performance, and why PU exists. They'll probe with: "What specifically makes a rule slow?"
8
Transaction architecture: orders vs transactions, unique columns, SalesTransaction table structure, how transactions are classified.
Orders vs Transactions: different input sources for Credit Rules. Unique key = comp date + line + subline + order ID + seq. Classification happens in the Classify stage using Classification Rules against classifier data.
9
MDLT creation, XML import errors, manual payments, adjustments, Query to Value limitations.
MDLT XML import errors are a real production pain point. SAP wants to know if you've encountered them. Query to Value limitations: scope, performance, and which contexts it's not allowed in.
10
Unpost, Unfinalize, Stage Hooks, FINALIZE stage mechanics, POST stage mechanics.
SAP goes deep on Stage Hooks — they want to know the exact XML descriptor structure, the three implementation types, and how the log files are named. Have a real example of a Stage Hook you implemented.
← Scenario-Based Questions     ← Back to Interview Prep Hub

Want the full answers?

Connect to discuss, or get monthly updates on the SAP ICM space.

Connect with Me → 📬 Get monthly updates