Senior & Lead Interview Questions

Multiple strategies exist — rule ordering, avoiding overuse of formulas, proper use of categories vs territories, minimal use of Query to Value. Which log do you check first?

There's a specific pipeline log that shows stage-by-stage timing and individual rule execution time. Knowing the log name is a literal interview question.

It runs automatically and identifies groups of position relationships that can be processed independently — enabling parallel processing. Why does it matter for performance?

This stage handles a specific edge case in credit allocation — not the main credit step. Think about credits that need special routing.

Pre/post hooks at each pipeline stage. Three methods: Shell Script, Stored Procedure, Java Class. Each has a different configuration in StageHookDescriptor.xml.

StageHookDescriptor.xml file location, stagename, pre/post type, command path, pipelineArgs (period, stage), and the log that gets generated (stagename_.log or _stagename.log).

Data quality issues, missing classification rules, configuration errors, timeout issues, bad rule logic. Also: defer reset during active pipeline.

Yes — and this has a specific use case for incremental processing. What does "defer reset" actually defer, and what risk does it introduce?

Four statuses, different permanence. Trial = temporary. Posted = permanent but can still be reversed. Applied = incorporated into payment. Finalized = locked.

Short answer: Yes, but with strict steps and consequences. You must Unfinalize first, then Unpost, then re-run.

ODI manages data movement from client's on-premise systems to the SAP Commissions cloud. What are the key folder types in the ODI Dropbox structure?

Manual folder vs automated. When you drop a file in manual folder, do you need to drop an audit file along with the data file?

Appears in ODI file naming conventions. Controls how the data is loaded.

Different naming convention when you include extended generic attributes vs when you don't. The naming pattern changes based on what's being sent.

Two-way process: push via ODI to cloud, extract via CDL or Informatica. What specific data types are extracted (credits, measurements, incentives, payment balances)?

Packages are analogous to classes. Procedures/Functions are methods. Overloading exists. Encapsulation via package body. This is a direct SAP interview question.

Reduces context switches between SQL and PL/SQL engines. FOR vs FORALL: FOR loops row-by-row in PL/SQL, FORALL sends bulk DML to SQL engine. When is bulk collect essential?

FOR iterates in PL/SQL context. FORALL sends bulk DML operations to Oracle SQL engine in a single call. Critical performance difference for large datasets.

Procedures cannot be used in SELECT — but Functions can, with restrictions. What restrictions apply to functions used in SQL statements?

Three types: INDEX BY tables, nested tables, VARRAYs. Essential for BULK COLLECT. Each has different storage and use-case characteristics.

Four prerequisites. Organization data (participant/position), classification data, position assignment, then rule creation. Missing any one of these causes the rule to not fire.

Two-step approach: Territory variable assignment to the position, then reference the territory variable in the Credit or Measurement rule. TCS interview question.

Think TCO, scalability, audit trail, regulatory compliance, pipeline reliability, integration ecosystem. What specific customer objections do you typically address?

Discovery workshops, current-state analysis, data flow mapping, comp plan document review, shadow payroll. What deliverable do you produce before any configuration?

Database schema differences (CS_ vs CSC_ prefixes), data volume migration, custom stored procedures that must be rebuilt, ODI vs legacy interfaces, testing strategy.

PU is the technical unit that runs the pipeline for data segregation. BU is administrative/organizational. Why would you have 4 BUs but only 1 PU?

Plan distribution, participant acknowledgment tracking, dispute management. An often-overlooked feature that matters a lot for compliance.

Different product — SAP Advanced Workflow has its own scripting layer using Groovy. Stage hooks here are Groovy-based, not XML descriptor files. Know the difference.

Logging strategy, context object inspection, null handling patterns. What happens if a Groovy script throws an exception mid-workflow?

APM/SAP Producer Pro manages the full agent lifecycle — recruitment, contracting, licensing, performance tracking — integrated with the compensation layer.