See exactly what's inside The SD Vault.
10 real interview questions · 1 full configuration scenario · 1 Ready Reckoner topic · No login, no signup
Most SAP SD prep platforms hide their content behind a paywall — you pay first, then find out if it's any good. We do the opposite. Below are real entries pulled straight from the library, exactly as our paid learners see them.
Read through the samples. Decide for yourself if the depth, S/4HANA-awareness, and project-floor honesty match what you need. Then make the call.
10 Sample Interview Questions
These are real entries from the library — not blog-paraphrased filler. Each question is graded by difficulty, has a complete answer, and includes an interview tip from 17+ years on the project floor.
What are the key steps in the SAP Order-to-Cash process?
The Order-to-Cash process in SAP SD covers the entire sales cycle from customer inquiry to cash receipt. The standard steps are: (1) Pre-sales activities — Inquiry (VA11) and Quotation (VA21); (2) Sales Order creation (VA01); (3) Availability check and Transfer of Requirements to MRP; (4) Delivery creation (VL01N) including picking and packing; (5) Goods Issue posting (VL02N); (6) Billing document creation (VF01); (7) Accounting document generation in FI; (8) Customer payment and clearing. Each step generates documents that are linked via document flow, viewable in VA03.
💡 Interview Tip
Interviewers often ask you to walk through OTC end-to-end. Draw the flow on a whiteboard if possible. Mention that each step creates a document and they are all linked via document flow (VA03 → Environment → Document Flow).
How does document flow work in SAP SD and how do you view it?
Document flow in SAP SD creates a chain of linked documents through the OTC process. Each subsequent document references its predecessor — a delivery references a sales order, a billing document references a delivery. This linkage is stored in tables VBFA (Sales Document Flow) and can be viewed via T-code VA03 → Environment → Document Flow or VL03N → Environment → Document Flow. The document flow shows the complete history: inquiry → quotation → order → delivery → goods issue → invoice → accounting document. It is invaluable for troubleshooting because you can see the status of each step.
💡 Interview Tip
Mention table VBFA which stores predecessor/successor document relationships. Interviewers may ask about VBUK (header status) and VBUP (item status) tables which track completion status — and that VBUK / VBUP are merged into VBAK / VBAP in S/4HANA.
What happens during Goods Issue posting in the delivery process?
Posting Goods Issue (PGI) in T-code VL02N is a critical step that triggers several parallel events: (1) Inventory is reduced by the delivered quantity (movement type 601); (2) Cost of Goods Sold (COGS) account is debited and inventory account credited in FI/CO; (3) The delivery status changes to "Goods Issue Posted"; (4) The billing due list is updated, making the delivery eligible for billing; (5) Transfer of Requirements is reversed in MRP as the demand is fulfilled. PGI is irreversible without a cancellation posting. The PGI date becomes the billing date reference.
💡 Interview Tip
Interviewers often ask what happens to the stock value. PGI debits COGS (P&L) and credits inventory (Balance Sheet) — this is the revenue recognition trigger in many scenarios. In S/4HANA, this posts to ACDOCA directly.
How do you troubleshoot a situation where a delivery cannot be created from a sales order?
To troubleshoot delivery creation failures from a sales order, check the following: (1) Incompletion log — VA02 → Edit → Incompletion Log (missing shipping point, route, etc.); (2) Schedule lines — check if confirmed quantity > 0 and if availability check has confirmed the quantity; (3) Credit block — check if the order is on credit hold (VKM1 for credit release); (4) Delivery block — VA02 header/item delivery block field; (5) Date check — requested delivery date must be in the past or today; (6) Plant assignment — plant must be assigned to the item; (7) Shipping conditions — must match between customer master and order. Use the delivery creation log (VL01N → error log) for specific error messages.
💡 Interview Tip
Structure your troubleshooting answer logically: check document status → check master data → check configuration. This shows methodical thinking which interviewers value highly.
What are the five elements of the Condition Technique in SAP SD pricing?
The Condition Technique in SAP SD pricing consists of five interconnected elements: (1) Condition Types — define the type of pricing element (e.g., PR00 for base price, K007 for customer discount, MWST for tax). Each has calculation type and condition class; (2) Access Sequences — define the search order for condition records (e.g., first check by customer/material, then by material alone); (3) Condition Tables — the database tables where condition records are stored, defined by key field combinations (e.g., table 305: customer + material); (4) Condition Records — the actual values maintained (e.g., ₹500/EA for material M001 for customer C001), maintained via VK11; (5) Pricing Procedure — the sequence of condition types with step numbers, subtotals, requirement routines, and alternative calculation routines.
💡 Interview Tip
This is THE most important pricing concept. Draw all five elements and their relationships. Many candidates mix up condition tables (structures) with condition records (data). Condition tables are configuration; condition records are master data.
What is the purpose of the Requirement Routine in a pricing procedure?
A Requirement Routine (VOFM → Requirements → Pricing) is an ABAP function that acts as a prerequisite check for a condition type to be active. If the routine returns FALSE, the condition type is skipped. Common requirement routines: Routine 2 — condition only active if item billing relevance allows; Routine 10 — only for foreign currency orders; Custom routines can check any document fields. Example: If your freight condition ZFRT should only apply to orders above ₹10,000, you create a custom requirement routine that checks the order net value. Routines are assigned in column "Reqt" in the pricing procedure (T-code V/08).
💡 Interview Tip
Distinguish requirement routines from alternative calculation routines (AltCBV column in pricing procedure). Requirements determine IF a condition applies; AltCBV determines HOW the value is calculated. Both are VOFM routines but serve different purposes.
How does an Access Sequence work in SAP SD pricing?
An Access Sequence is an ordered list of condition tables that the system searches through to find a valid condition record. For example, access sequence PR02 might search: (1) Customer/Material specific record → (2) Customer/Material Group → (3) Price List/Material → (4) Material alone → (5) General price. The search stops at the first table where a valid record is found. This creates a hierarchy from most specific to most general. Tables are searched in sequence order; lower numbers are searched first. Access sequences are assigned to condition types (V/06).
💡 Interview Tip
The "Exclusive" indicator on an access sequence step means: if a record is found in this table (even with value zero), stop searching further. This is useful when you want to explicitly override with a zero-price record and not fall through to a higher-level price.
Explain the concept of Copy Control in SAP SD.
Copy Control defines how data flows from one document type to another in the OTC chain. It is configured in SPRO → Sales → Maintain Copy Control for Sales Documents (or Billing Documents, or Deliveries). Copy control settings exist at three levels: Header (controls how header data like pricing date, payment terms are copied), Item (controls item-level copying including pricing type — G for copy unchanged, B for re-determine), and Schedule Line (controls quantity and date copying). Key configuration includes the Copying Requirement (VOFM routine that checks preconditions) and the Data Transfer Routine (VOFM routine that determines what data is transferred). Table TVCPA controls sales-to-sales copying, TVFK controls billing-to-sales.
💡 Interview Tip
Pricing type is a critical setting — "G" copies prices unchanged (important for returns/credit memos referencing original), "B" redetermines, "D" copies and makes them fixed. Always know which pricing type applies to your business scenario.
How are returns processed in the OTC cycle?
Returns processing in SAP SD follows a reverse OTC flow. A Return Sales Order (document type RE, T-code VA01) is created with reference to the original billing document or sales order. The item category REN is determined automatically. A Return Delivery (VL01N with delivery type LR) is then created, and goods are received back into the plant using movement type 651 (returns from customer). Finally, a Credit Memo (document type G2 or RE billing type) is created via VF01 to credit the customer. The credit memo posts to FI reducing the customer receivable.
💡 Interview Tip
Mention quality inspection integration — in S/4HANA, returned goods can be routed to quality inspection before being accepted into stock. Also mention the difference between returns with and without reference.
What is a Scale in SAP SD pricing and how is it configured?
A Scale (or Condition Scale) allows pricing to vary based on quantity or value ordered — the more you buy, the lower the price. There are two types: (1) Graduated — each quantity tier has its own price, and the price for the entire quantity is the price of the tier reached (e.g., 1–99 units: ₹100, 100+ units: ₹80 — ordering 150 units = ₹80 each); (2) Base Point Scale — complex graduated scales. Scales are configured by setting the "Scale Type" in the condition type (V/06). When maintaining condition records (VK11), you enter the scale table with "From" quantities/values and corresponding prices. The Scale Basis field in condition type controls whether scale is based on order quantity, order value, or weight.
💡 Interview Tip
Scales are critical for B2B pricing. Be ready to explain the difference between graduated (step) scales and cumulative scales. Also know that scales can be currency-based for value discounts — "if order exceeds ₹1 lakh, give 5% additional discount."
220+ more questions inside The SD Vault. Including the advanced scenarios that interviewers actually use to filter senior candidates.
1 Sample Configuration Scenario
Every scenario in The SD Vault is a real configuration exercise — exact IMG paths, every T-code, and the gotchas that catch people on go-live. Here's one in full.
Configure a New Sales Organization and Assign to Company Code
End-to-end setup of a new Sales Organization in SAP S/4HANA SD, from enterprise structure creation to first test order.
Business Context
Your company is expanding into a new region and needs a dedicated Sales Organization "1020" for the North India market. This Sales Org must be assigned to Company Code 1000, linked to relevant Distribution Channels and Divisions, and all dependent SD configuration must be activated before the first order can be processed.
Solution Approach
Enterprise structure setup in SAP SD follows a strict sequence: define → assign → configure dependent objects. The Sales Organization is the top-level SD organizational unit, so all subsequent configuration flows from it. Key principle: never skip the assignment steps — they are the glue between SD and FI/MM organizational structures.
Step-by-Step Configuration
Define Sales Organization
📍 Enterprise Structure → Definition → Sales and Distribution → Define Sales Organization
Create Sales Org 1020 with name "SD North India". Enter Company Code: 1000. Currency: INR. Save.
Assign Sales Org to Company Code
📍 Enterprise Structure → Assignment → Sales and Distribution → Assign Sales Organization to Company Code
Map: 1020 → 1000. This is mandatory for FI billing postings to reach the correct company code.
Assign Distribution Channel to Sales Org
📍 Enterprise Structure → Assignment → SD → Assign Distribution Channel to Sales Org
Add: 1020 + 10 (Direct Sales), 1020 + 20 (Retail).
Assign Division to Sales Org
📍 Enterprise Structure → Assignment → SD → Assign Division to Sales Org
Add: 1020 + 00 (Cross-Division), 1020 + 01 (Product Division).
Set Up Sales Areas
📍 Enterprise Structure → Assignment → SD → Set Up Sales Area
Create combinations: 1020/10/00, 1020/10/01, 1020/20/00.
Assign Plant to Sales Org (for delivery)
📍 T-code: OVX6
Assign supplying plant(s) to Sales Org 1020.
Configure Pricing Procedure for new Sales Org
📍 T-code: OVKK
Assign pricing procedure determination: Sales Area 1020/10/00 + Customer PP + Document PP → Procedure ZSTAN.
Maintain Output Determination
📍 T-code: NACE (Application V1)
Create condition records for BA00 (order confirmation) for new Sales Org 1020.
Test with Sales Order
📍 T-code: VA01
Create order with Order Type OR, Sales Org 1020 — verify pricing procedure, output, and document number range.
Key T-Codes
⚠ Field Notes / Gotchas
Always test the complete OTC cycle (order → delivery → billing) for a new Sales Org before go-live. Missing assignments only surface when processing — not during configuration. Common missing steps: forgetting to assign plant to Sales Org (OVX6) or missing pricing procedure in OVKK.
37 more configuration scenarios inside. Including pricing procedures with GST, credit management with FSCM, third-party processing, returns & rebates, and S/4HANA-specific exercises.
1 Sample Ready Reckoner Topic
Ready Reckoner = quick-reference cheat sheets you actually use the night before an interview. Concise, structured, no fluff. Here's one in full.
Pricing Condition Technique
How Pricing Works in SAP SD
Pricing in SAP SD uses the Condition Technique — a flexible framework that determines prices, discounts, and surcharges across every sales document.
The Five Building Blocks
- Condition Types — Define what the condition is (PR00 = price, K007 = customer discount, MWST = tax)
- Access Sequences — Define the search strategy (which tables to search, in what order)
- Condition Tables — Store the actual condition records (key field combinations)
- Pricing Procedure — Groups condition types with calculation rules (step, counter, from, to, requirement)
- Procedure Determination — Links procedure to sales area + customer pricing procedure + doc pricing procedure
Typical Pricing Procedure Steps
| Step | Cond Type | Description |
|---|---|---|
| 10 | PR00 | Base price (list price) |
| 20 | K004 | Material discount |
| 30 | K005 | Customer/material discount |
| 40 | K007 | Customer discount % |
| 100 | NETPR | Net price (subtotal) |
| 110 | MWST | Output tax (VAT/GST) |
| 900 | TOTAL | Final amount |
Key T-Codes
- V/06 — Maintain condition types
- V/07 — Maintain access sequences
- V/08 — Maintain pricing procedures
- VK11 / VK12 / VK13 — Create / Change / Display condition records
- OVKK — Pricing procedure determination
29 more Ready Reckoner topics inside. Including partner determination, item categories, schedule line categories, output determination, FSCM credit, and S/4HANA-specific differences.
What you get on this page vs. inside
| Item | This Free Page | Inside The SD Vault |
|---|---|---|
| Interview Questions | 10 | 230+ |
| Configuration Scenarios | 1 | 38 |
| Ready Reckoner Topics | 1 | 30 |
| Daily Challenges (5-Q quick rounds) | — | Daily |
| XP, streaks & gamified progress | — | ✓ |
| Bookmark + offline review | — | ✓ |
| S/4HANA-specific content callouts | Some | Throughout |
| Lifetime updates as S/4HANA evolves | — | ✓ |
If the samples landed — the full library is waiting.
Lifetime access. One-time payment. Built and curated by an SAP SD Solution Architect with 17+ years on real S/4HANA projects.
See Pricing →Or browse more free reference content: T-Codes, Tables, Pricing Procedure, Credit Management, Order-to-Cash, Interview Questions.