← Interview Prep
● Scenario-Based

Real Business Scenarios.

These are the questions that separate consultants from architects. No textbook answer — interviewers want to see how you think, how you structure a solution, and whether you've actually done this in production.

Hints point you in the right direction. Hints point you in the right direction. Think through each scenario and compare your approach against the structure.

Pipeline

Pipeline & Execution Scenarios

S-01
Targeted Pipeline Run — 100 out of 1,000 Positions
You need to run the pipeline for only 100 specific positions out of 1,000 total. Describe at least 2 approaches. Which is more effective and why?
Direction Hint
Think about Position Groups (assign positions to a named group, run pipeline by group) vs Specific Position mode (run individually). One is repeatable and scalable. The other is good for one-off testing. Consider which approach works better when the 100 positions change every month.
Intermediate
S-02
Transaction Correction at Scale — 1,000 Bad Records in 10,000
You imported 10,000 transactions. You later discover that 1,000 of them have incorrect values. How do you correct only those 1,000 transactions and rerun the pipeline for just those affected positions — without disturbing the other 9,000?
Direction Hint
You need to identify the 1,000 bad transactions (Research workspace or direct DB query), decide between correction vs reversal approach, and then target only the affected positions in the pipeline rerun. Which reset strategy do you use, and what happens to credits already allocated from the bad transactions?
Intermediate
S-03
Cumulative Payment Calculation — Post, Post Again, Post Again
First pipeline run generates $100. You Post it. Second run generates $150. You Post again. Third run generates $80. How much is shown in Payment at this point — and what are the Applied vs Trial vs Posted amounts?
Direction Hint
The key is understanding how the Post stage handles incremental runs. It's not additive in a simple way. Think about what "Applied" status means when the balance from a prior post is incorporated into the next payment calculation. This is a Deloitte favourite — they want the exact numbers with reasoning.
Advanced
S-04
Plan Modification — Identify & Re-Run Affected Positions Only
You modified one compensation plan mid-month. How do you identify all transactions associated with that plan and run the pipeline only for those affected positions — without touching unrelated positions?
Direction Hint
Trace the chain: Plan → Titles assigned to that Plan → Positions on those Titles → Transactions for those Positions. Which DB tables or workspaces let you do this trace? Once identified, use Specific Position mode. What's the risk of running incremental vs full recalculation here?
Advanced
S-05
Finalized Group + Position Move — What Happens to Payment?
You finalized a Position Group. Then you move one position out of that finalized group into a non-finalized group. What happens to that position's existing payment and balance? Does the next pipeline run affect it?
Direction Hint
Finalization is at the period/position-group level. Moving a position to a different group doesn't retroactively change what was finalized. But the next pipeline run behavior depends on the mode and period. Think about what "finalized" really protects and when the new group membership takes effect.
Advanced
CMID Design

Rule Design Scenarios

S-06
Multi-Tier Commission Design — Two Product Lines, Threshold Trigger
An agent sells two product lines: Plan A and Plan B. If their total sales exceed $1,000, they earn 10% commission on Plan A sales and 20% on Plan B sales. Design the complete CMID rule set from scratch.
Direction Hint
You need separate Credit Rules per product line, separate Primary Measurement Rules to aggregate each, a Secondary Measurement Rule to calculate the total threshold check, and conditional Incentive Rules with different rate tables per product line. The threshold condition is the hard part — where does the $1,000 check live and how does it gate the incentive calculation?
Advanced
S-07
MDLT vs Rate Table — 3-Column Product/Region/Amount Table
A client has a compensation table with 3 columns: Product Line, Region, and Commission Amount. There are 500 rows covering all product-region combinations. Would you use an MDLT or a Rate Table? Design the incentive rule to use it.
Direction Hint
Rate Table is 2D and attainment-based. MDLT handles multi-dimensional lookups where the value is looked up by matching multiple index values — not by sales attainment. For a product × region → amount matrix, one of these is clearly wrong. Walk through how you'd create the structure and reference it in the Incentive Rule using LOOKUP().
Intermediate
S-08
Yearly Bonus — Pay in December, Accumulate All Year
A participant should receive a yearly bonus paid only in December, based on total annual sales. How do you design this? Walk through the Calendar, Measurement, Incentive, and Deposit Rule configuration.
Direction Hint
Think about SUM PRIOR MEASUREMENT or SUM PRIOR INCENTIVES functions to accumulate across months. Your Incentive Rule output period type = Annual. Your Deposit Rule only releases in the December period. The formula uses cumulative measurements. There are multiple ways to do this — which is most maintainable?
Advanced
S-09
Date-Based Pay Split — 1st–15th vs 16th–30th
Participants who join between the 1st and 15th of the month should be paid in the current month. Those joining between 16th and 30th should be paid in the following month. What formula do you write and in which rule does it live?
Direction Hint
You need DAY() function to extract the day from the participant's effective start date. IF(DAY(start_date) <= 15, currentPeriod, nextPeriod). The question is: does this condition live in the Deposit Rule's release date logic, an Incentive Rule formula, or somewhere else? And how do you reference "next period" in a formula?
Intermediate
S-10
Credit Without Position/Title Assignment
A specific product line needs to be credited to a position that doesn't have a formal title assignment in the system. How do you still get credit to flow to that position?
Direction Hint
Use Territory + Variable assignment. Assign the territory variable directly to the position (not via title). Reference that territory variable in the Credit or Measurement Rule. This bypasses the normal title-plan assignment path. Which workspace do you use for the variable assignment?
Intermediate
Pay / Post / Finalize

Period Management Scenarios

S-11
Cross-Period Recovery — January Finalized, Missed Payments Need February
January 2021 has been fully finalized. You discover payments that should have been in January were not captured. The business wants them reflected in February. What are your options, and which is safer in a production environment?
Direction Hint
Two paths: (1) Unfinalize January → Unpost → reprocess → re-Finalize. High risk in production, affects audit trail. (2) Create adjustment transactions in February that carry the January missed amounts forward. The second is usually preferred. How do you structure the adjustment and which Reason Code applies?
Advanced
S-12
Negative Payment Scenario — Balances and Carry-Forward
The system is configured to allow negative payments. A position generates a negative incentive value. Walk through exactly what happens at the Pay, Post, and Finalize stages. How does the negative balance carry into the next period?
Direction Hint
Negative deposits are stored as negative balance values. The Earning Group determines whether negative deposits from different earning codes offset each other. In the next period, the negative balance is "applied" against new positive deposits before any net payment goes out. Think about what happens if the position is terminated before the balance clears.
Advanced
S-13
Trace a Transaction to Its Payment
A participant disputes their payment. You need to trace one specific transaction all the way from ingestion through classification → credit → measurement → incentive → deposit → payment. How do you do this?
Direction Hint
The Research workspace is your primary tool. You can trace from Transactions → Credits (filter by salestransactionseq) → Measurements → Incentives → Deposits → Payments. At each stage, which table stores the link? The cs_CREDITTRACE table is especially useful here.
Intermediate
System Design

Architecture Scenarios

S-14
Large-Volume System Design — 100K Daily Transactions
A telecom client has 100,000 daily transactions. Dealers are paid monthly commission. Managers get quarterly bonuses. Design the high-level system architecture — calendars, PU design, position structure, pipeline strategy, and rule types.
Direction Hint
Multiple calendars (monthly + quarterly). Incremental pipeline for daily processing windows. Island Analysis for parallel processing. Position Groups for segmented runs. Monthly Credit + PM rules feeding into Quarterly SM rule for bonus. Consider how many Processing Units you need and why. Stage Hooks for pre/post validation. This is a Principal Consultant-level question.
Principal
S-15
Rate Change Mid-Quarter — Historical Data Must Not Change
The commission rate changes from 5% to 7% starting next month. Transactions already processed at 5% must not be recalculated. How do you implement this change without affecting historical results?
Direction Hint
Never overwrite Rate Table values in place. Use period-based Fixed Values or create new rate table versions with effective dates. Alternatively, use a date-conditional formula in the Incentive Rule. The safest approach uses versioning — which SAP Commissions objects support true versioning and which don't?
Advanced
← Advanced Questions Company-Specific Questions →

Want the full answers?

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

Connect with Me → 📬 Get monthly updates