SAP SD Interview Questions & Answers (2026 Edition)
Preparing for an SAP SD interview? This guide covers 15 real SAP SD interview questions with detailed answers — spanning the basics of enterprise structure, pricing procedure configuration and S/4HANA-specific topics. Every answer is written the way a senior interviewer expects to hear it — with real configuration paths, T-codes and business context.
Whether you are a fresher preparing for your first SAP opportunity, or an experienced consultant targeting an S/4HANA implementation role, this page gives you a solid foundation. At the bottom you will find 10 more advanced interview questions from inside The SD Vault — the complete platform with 230+ curated questions.
Basic SAP SD Interview Questions
These foundational questions are asked in almost every SAP SD interview — from fresher level to senior. If you cannot answer these confidently, start here.
Q1.What is the organisational structure in SAP SD?
The SAP SD organisational structure is built around four key elements: Sales Organisation (responsible for selling and distributing products), Distribution Channel (the route through which goods reach the customer — e.g. wholesale, retail, direct), Division (a product grouping dimension), and Sales Office/Sales Group (optional, for internal reporting). A Sales Area — which is the combination of Sales Org + Distribution Channel + Division — is the central control element for sales documents, pricing, and master data determination.
Q2.What is a Sales Area and why is it critical?
A Sales Area is the unique combination of Sales Organisation, Distribution Channel and Division. Almost every activity in SAP SD — customer master maintenance, condition records, sales document creation, reporting — is performed within the context of a specific sales area. If a customer, material or condition record is not extended to the relevant sales area, the sales process will fail. Sales Area also drives pricing procedure determination via the OVKK table.
Q3.What are the main sales document types in SAP SD?
The four categories of sales documents are: Inquiry (IN) — a pre-sales enquiry from a customer; Quotation (QT) — a legally binding offer; Sales Order (OR) — the standard order that triggers fulfilment; and Contracts & Scheduling Agreements (CQ, DS, LP) for long-term arrangements. Each document type is configured in VOV8 and controls critical behaviours: number range, delivery block, billing block, item category determination, screen sequence and pricing procedure (via DoPP).
Q4.What is the Order-to-Cash (OTC) cycle in SAP SD?
The OTC cycle spans six key steps: (1) Pre-sales activities — Inquiry and Quotation, (2) Sales Order creation (VA01), (3) Availability Check and ATP, (4) Delivery processing and Picking (VL01N / VL06O), (5) Goods Issue — which reduces inventory and posts cost of goods sold in FI, and (6) Billing (VF01) — which creates the invoice and posts revenue/tax to FI. Each step integrates with MM, WM, FI and CO modules.
Q5.What is the difference between a sales document, delivery document and billing document?
The sales document (e.g. sales order) captures the customer commitment. The delivery document (outbound delivery) handles physical execution — picking, packing, post goods issue. The billing document creates the financial invoice, transfers revenue to FI and settles the accounts receivable. All three are linked via the document flow (VBFA table) and can be viewed through the document flow button in VA02/VL02N/VF02.
SAP SD Pricing Procedure Interview Questions
Pricing is the most tested area in any SAP SD interview. Senior interviewers go deep — determination logic, condition technique, account keys, routines. Master these five and you will handle 80% of pricing questions.
Q6.How is the Pricing Procedure determined in SAP SD?
The Pricing Procedure is determined by a combination of three keys: (1) Sales Area — Sales Org + Distribution Channel + Division, derived from the sales document header, (2) Customer Pricing Procedure (CuPP) — a 1-digit indicator on the customer master in the Sales Area → Sales tab, and (3) Document Pricing Procedure (DoPP) — a 1-digit indicator configured on the Sales Document Type in VOV8. These three values are mapped in transaction OVKK to resolve the actual Pricing Procedure. If any key is missing or mismatched, pricing determination fails silently.
Q7.What is the Condition Technique in SAP pricing?
The Condition Technique is a flexible framework used across SAP to find the right condition value for a given scenario. It consists of five elements: (1) Condition Type (e.g. PR00 for base price), (2) Access Sequence — the sequential list of condition tables SAP searches, (3) Condition Tables — the actual key combinations where condition records are stored, (4) Condition Record (VK11) — the actual price/discount value, and (5) Pricing Procedure — which groups all relevant condition types in a calculation sequence.
Q8.What is the difference between a Statistical condition and a non-Statistical condition?
A Statistical condition is calculated and displayed on the sales document for information purposes but does NOT affect the net value of the item or the accounting posting. Classic example: VPRS (cost condition) must be Statistical, otherwise it would reduce revenue and post incorrectly to FI. A non-Statistical condition, by contrast, is included in the net value calculation and posts to the G/L account linked via its Account Key.
Q9.What are Account Keys in a pricing procedure?
Account Keys are the bridge between SD condition types and FI G/L accounts. Each revenue-relevant condition type in the pricing procedure is assigned an Account Key (e.g. ERL for revenue, MWS for tax, ERS for discounts, EIN for COGS). The Account Key is then mapped to a specific G/L account in transaction VKOA, based on the chart of accounts, sales organisation, customer account assignment group and material account assignment group. Without a valid VKOA entry, billing release to accounting will fail.
Q10.What are Requirement and Alternative Calculation Routines?
These are small ABAP routines (created via VOFM) assigned to condition types in the pricing procedure. (1) Requirement Routine — decides whether the condition is even evaluated. If it returns false, the condition is skipped silently. (2) Alternative Calculation Type (AltCT) — replaces the standard calculation logic with custom ABAP code. (3) Alternative Condition Base Value (AltCBV) — changes the base value the percentage is applied against. Standard routines are 1–999; custom routines are numbered 600+.
SAP S/4HANA SD Interview Questions
If the role is on an S/4HANA implementation, these questions separate candidates who have actually worked on S/4HANA from those with only ECC experience.
Q11.What is the difference between SAP ECC SD and S/4HANA SD?
Key S/4HANA SD changes include: (1) Business Partner (BP) replaces the legacy Customer master — transaction XD01 is replaced by BP with roles like FLCU00 (FI customer) and FLCU01 (SD customer), (2) Simplified data model — tables like VBUK, VBUP are replaced by VBAK/VBAP with status fields moved inline, (3) Universal Journal (ACDOCA) unifies FI and CO postings, (4) Advanced Available-to-Promise (aATP) replaces classic ATP, (5) Advanced Conditions (BRFplus integration) adds rule-based pricing, and (6) Fiori apps replace many legacy GUI transactions.
Q12.What is the Business Partner concept in S/4HANA?
Business Partner (BP) is the central master data object in S/4HANA for all customers, vendors and contact persons. It consolidates what was previously stored as separate Customer (KNA1, KNB1, KNVV) and Vendor (LFA1, LFB1) masters. BP roles define the functional perspective — for SAP SD, the key role is FLCU01 (Customer — Sales & Distribution), which maintains sales area data. For FI integration, FLCU00 (Customer — FI) holds company code data. Transaction BP replaces XD01/XD02/VD01.
Q13.What are Advanced Conditions in S/4HANA pricing?
Advanced Conditions (introduced in S/4HANA 2020+) enable rule-based pricing using BRFplus decision tables instead of traditional condition records in VK11. Pricing rules can now be maintained through Fiori apps by business users without needing ABAP development. Advanced Conditions are especially useful for complex pricing scenarios (tiered pricing, customer-product exceptions, time-bound logic) that would otherwise require custom routines.
Q14.What is the Universal Journal (ACDOCA) and how does it affect SD?
The Universal Journal (table ACDOCA) is a single source of financial truth in S/4HANA — it merges FI, CO, ML, AA and CO-PA into one line-item table. For SD: billing document postings go directly into ACDOCA with the account key, profit centre, segment and cost centre attributes attached. This simplifies margin analysis — the old costing-based vs account-based CO-PA split is largely obsolete. Real-time profitability reporting is now possible without extracting to BW.
Q15.What is the Output Management change in S/4HANA?
S/4HANA introduces a new output management framework based on BRFplus and Adobe Document Services, parallel to the legacy NAST-based system. The new framework uses Output Types defined per business object, with BRFplus determining which output to issue and Adobe Forms replacing SAP Script/Smart Forms for layout. Legacy NAST output is still supported in the short term, but greenfield S/4HANA projects typically adopt the new framework. Configuration is done via the Output Management IMG node and Fiori apps.
Advanced SAP SD Interview Questions
The following 10 advanced questions — and 215+ more — are available inside The SD Vault with complete, step-by-step answers including configuration screens and T-code walkthroughs.
Walk me through the complete Third-Party Sales process including PR/PO integration and billing dependencies.
How do you configure Intercompany Sales billing between two company codes? List all the objects involved.
What is the difference between Consignment Fill-Up, Issue, Pickup and Return? When would you use each?
How does Credit Management work in S/4HANA (FSCM) vs classic SD Credit Management in ECC?
Explain Route Determination and what factors drive the determination in a delivery.
How do you configure Rebate Processing (Condition Contract Management) in S/4HANA?
What is the Availability Check (ATP) in S/4HANA? How is it different from classic ATP?
How do you handle Free Goods (Inclusive vs Exclusive) in pricing? Give a real-world example.
Walk me through configuring a new Sales Document Type from scratch — copy control, item category, number range.
How do you troubleshoot a billing document that is stuck — not released to accounting?
215+ More Questions Inside The SD Vault
Complete answers with configuration paths, T-codes, and real-project scenarios. Lifetime access — one-time payment.
Unlock All Questions →Frequently Asked Questions
Are these SAP SD interview questions for freshers or experienced professionals?
Both. The Basic section covers questions typically asked to freshers and 0-2 year consultants. The Pricing Procedure and S/4HANA sections cover questions asked to consultants with 2-8 years of experience. Inside The SD Vault, 230+ questions are tagged by difficulty level — Fresher, Mid-Level and Senior — so you can focus on what matches your target role.
How should I prepare for an SAP SD interview?
Start with the fundamentals: enterprise structure, sales area, order-to-cash flow, and standard sales document types. Then go deep on pricing procedures — this is the most frequently tested area. For S/4HANA-specific roles, study the Business Partner concept, Universal Journal and Advanced Conditions. Practise explaining configuration paths and real-world scenarios out loud — interviewers value clarity of thought as much as factual knowledge.
What is the difference between SAP SD and SAP S/4HANA SD?
SAP SD (Sales & Distribution) is the functional module. S/4HANA is the next-generation ERP platform that runs on the SAP HANA database. In S/4HANA, the SD module is simplified — Business Partner replaces Customer master, ACDOCA replaces multiple FI/CO tables, Advanced Conditions enable rule-based pricing, and Fiori apps replace many GUI transactions. The core SD concepts remain unchanged, but the data model and user interface are modernised.
Is SAP SD a good career in 2026?
Yes. SAP SD remains one of the most in-demand functional modules because every manufacturing, retail and distribution company needs order-to-cash capability. With ongoing S/4HANA migrations running until 2030+, SAP SD consultants with S/4HANA skills are especially sought after. Mid-level SD consultants in India typically earn ₹10-18 LPA, with senior and architect roles reaching ₹25-45 LPA.
How many questions are inside The SD Vault?
The SD Vault contains 230+ curated interview questions with detailed answers, 38 real-world configuration scenarios, and 30 Ready Reckoner topics for quick revision. All content is written by an SAP SD Solution Architect with 17+ years of S/4HANA project experience. Access is a one-time purchase with lifetime access — no subscription, no recurring fees.
Ready to ace your SAP SD interview?
Get lifetime access to 230+ interview questions, 38 real-world scenarios, and 30 Ready Reckoner topics — all inside The SD Vault.
Get Lifetime Access →