Organizational Structure
Q1. What are the organizational units in SAP SD?
Answer: The main SD organizational units are Sales Organization, Distribution Channel, Division, Sales Area (combination of the three), Sales Office, Sales Group, Plant, Storage Location, Shipping Point, and Loading Point. The Sales Area is the key unit — all SD master data and documents are created within a sales area.
Q2. What is a sales area and why is it important?
Answer: A sales area is the combination of Sales Organization + Distribution Channel + Division. It is important because customer master records, material master sales views, pricing, and sales documents are all maintained per sales area. You cannot create a sales order without a valid sales area.
Q3. What is the difference between a plant and a shipping point?
Answer: A plant is a logistics organizational unit where materials are produced, procured, or stored (e.g., a factory or warehouse). A shipping point is the organizational unit where deliveries are processed and goods issue is posted. One plant can have multiple shipping points, and the shipping point is determined in the sales order based on the plant, shipping condition, and loading group.
Master Data
Q4. What are partner functions in SAP SD?
Answer: Partner functions define the roles business partners play in a sales document — Sold-to Party, Ship-to Party, Bill-to Party, and Payer. They are determined automatically via partner determination procedures and stored in table VBPA. For example, goods go to the ship-to party while the invoice goes to the bill-to party.
Q5. What is a customer-material info record?
Answer: It stores customer-specific data for a material, such as the customer’s own material number or specific delivery tolerances. It is maintained per sales area and is useful when a customer refers to your product by their own part number.
Q6. What views of the material master are relevant for SD?
Answer: The Sales: Sales Org. 1, Sales: Sales Org. 2, Sales: General/Plant, and Foreign Trade views. They hold sales unit, delivering plant, loading group, transportation group, account assignment group, and tax classifications — all maintained per sales area and plant.
Order-to-Cash Process
Q7. Explain the standard order-to-cash process in SAP SD.
Answer: Inquiry → Quotation → Sales Order (VA01) → Delivery (VL01N) → Picking/Packing → Post Goods Issue → Billing Document (VF01) → Accounting Document. The documents are linked through the document flow table VBFA.
Q8. What is the difference between an inquiry and a quotation?
Answer: An inquiry is the customer’s request for a quote — it has no legal commitment. A quotation is the company’s binding offer to the customer with prices and validity dates. Both are sales document types, and a quotation can be referenced to create a sales order.
Q9. What is copy control in SAP SD?
Answer: Copy control defines the rules for copying data from a source document to a target document (e.g., order → delivery, delivery → billing). It controls which document types can be copied, how item data transfers, and routines for pricing and quantity logic. It is configured per document type combination.
Q10. What is the incompletion log?
Answer: The incompletion log flags mandatory fields missing in a sales document that block further processing (e.g., delivery or billing). It is controlled by incompletion procedures assigned to document types, and users can view it via the “Incompletion log” button in the sales order.
Pricing
Q11. Explain the condition technique in SAP SD pricing.
Answer: The condition technique has five elements: Condition Tables (key combinations like customer/material), Access Sequences (search order through condition tables), Condition Types (e.g., PR00 price, K004 discount), Pricing Procedures (the calculation schema), and Condition Records (the actual master data with amounts and validity dates, maintained via VK11).
Q12. What is a pricing procedure?
Answer: A pricing procedure is the calculation schema that defines the sequence of condition types applied to a sales document — base price, discounts, surcharges, freight, and taxes — and how subtotals and the net value are computed. It is determined by sales area, document pricing procedure, and customer pricing procedure.
Q13. How is pricing determined in a sales order?
Answer: Pricing is determined by the pricing procedure, which is found using the sales area, the document pricing procedure (from the sales document type), and the customer pricing procedure (from the customer master). The system then reads condition records via access sequences and calculates the net value.
Q14. What is the difference between VK11, VK12, and VK13?
Answer: VK11 creates condition records, VK12 changes them, and VK13 displays them. These are the master data transactions for pricing conditions such as prices, discounts, and surcharges.
Delivery and Shipping
Q15. What are the steps in the delivery process?
Answer: Create delivery with reference to the sales order (VL01N) → Picking (goods taken from storage) → Packing → Post Goods Issue (inventory reduced, delivery completed). After goods issue, the delivery can be billed.
Q16. What is picking in SAP SD?
Answer: Picking is the process of taking goods out of storage locations to fulfill a delivery. Picking quantities are entered in the delivery, and the system can generate transfer orders for warehouse-managed storage locations.
Q17. What happens during Post Goods Issue (PGI)?
Answer: PGI reduces inventory in MM (material document posted), updates delivery status to “completed,” changes requirements, and triggers the billing due list. It is the point where ownership of goods transfers to the customer.
Q18. What is a delivery due list?
Answer: The delivery due list (VL10A for sales orders) shows all sales order items due for delivery based on schedule line dates. Deliveries can be created collectively from this list instead of one by one.
Billing
Q19. What billing document types do you know?
Answer: F2 (Invoice), F1 (Order-related invoice), L2 (Debit memo), G2 (Credit memo), S1 (Cancellation), S2 (Cancellation), and IV (Intercompany billing). The billing type is controlled by copy control from the delivery or order.
Q20. What is an invoice list?
Answer: An invoice list (billing type LR) combines multiple billing documents for a payer into a single periodic statement. It is created with VF21 and is useful for customers billed frequently.
Credit Management and Availability
Q21. How does credit management work in SAP SD?
Answer: Credit control areas monitor customer credit exposure. Each customer gets a credit limit (FD32), and sales orders check against open orders, deliveries, and receivables. If the limit is exceeded, the order is blocked and must be released by authorized users (VKM1/VKM2).
Q22. What is the availability check (ATP)?
Answer: The Availability Check (Available-to-Promise) verifies whether the requested quantity can be confirmed on the requested delivery date, considering stock, planned receipts, and planned issues. It runs at order entry and creates schedule lines in VBEP. Rules are defined in checking groups and checking rules.
Q23. What is a credit control area?
Answer: It is the organizational unit in FI that monitors and controls credit given to customers. A credit control area can cover one or more company codes, and credit limits are assigned per customer per credit control area.
Tables and Transactions
Q24. Name the key SAP SD tables and what they store.
Answer: VBAK/VBAP (sales order header/item), LIKP/LIPS (delivery header/item), VBRK/VBRP (billing header/item), KNA1/KNB1/KNVV (customer master), KONV (document conditions), and VBFA (document flow). Our complete SAP SD tables list explains each in detail.
Q25. What are the most important SD transaction codes?
Answer: VA01/VA02/VA03 (create/change/display sales order), VL01N/VL02N/VL03N (delivery), VF01/VF02/VF03 (billing), XD01/XD02/XD03 or BP (customer master in ECC/S/4HANA), VK11/VK12/VK13 (condition records), and SE16N (table display).
Q26. How do you check the document flow of a sales order?
Answer: Open the sales order in VA03 and click the document flow icon, or query table VBFA with the order number in VBELV. VBFA links preceding documents (VBELV/POSNV) to subsequent documents (VBELN/POSNN).
Advanced Topics
Q27. What is a sales BOM?
Answer: A Bill of Material used in sales, e.g., a set or assortment sold as one item. In SD, BOMs explode in the sales order so components can be delivered and billed. Item category determination controls whether the BOM header or components are relevant for delivery and billing.
Q28. What is item category determination?
Answer: It determines the item category (e.g., TAN standard item, TANN free of charge) based on the sales document type + item category group (from the material master) + higher-level item category + usage. The item category controls delivery relevance, billing relevance, and pricing.
Q29. What is schedule line category determination?
Answer: It determines the schedule line category (e.g., CP, DN) based on item category + MRP type. The schedule line category controls whether an availability check runs, whether transfer of requirements happens, and whether the item is relevant for delivery.
Q30. What are customer hierarchies?
Answer: Customer hierarchies group customers into a tree structure (e.g., national account → regional chains → stores) for pricing and reporting. Prices or rebates can be maintained at a higher node and apply to all customers below it.
Q31. What is a rebate agreement?
Answer: A rebate is a retroactive discount paid to a customer based on sales volume over a period. Rebate agreements define the payer, validity, and condition records; accruals post during billing and settlement happens at period end.
Q32. What is third-party order processing?
Answer: In third-party processing (item category TAS), the ordered goods are delivered directly by the vendor to the customer. The sales order triggers a purchase requisition automatically, and billing to the customer happens after the vendor invoice is received (MIRO).
Q33. What is consignment processing?
Answer: Goods remain the company’s property while stored at the customer’s site (consignment fill-up). The customer is only billed on consignment issue (when they consume the goods) or consignment pick-up (returns).
Q34. What is the difference between a debit memo and a credit memo?
Answer: A credit memo (G2) reduces what the customer owes — used for returns or overbilling. A debit memo (L2) increases what the customer owes — used for underbilling. Both reference the original billing document.
Q35. What is output determination in SD?
Answer: Output determination controls automatic printing, fax, or EDI of documents (order confirmations, delivery notes, invoices). Like pricing, it uses the condition technique: output types, access sequences, and condition records, with processing via NAST.
S/4HANA Changes
Q36. What changed for customer master data in S/4HANA?
Answer: Customers and vendors are now Business Partners (transaction BP) with mandatory Customer-Vendor Integration (CVI). The old transactions XD01/XD02/XD03 and VD01/VD02/VD03 are replaced by BP. The underlying tables (KNA1, KNB1, KNVV) still exist.
Q37. What are the key simplifications in SD under S/4HANA?
Answer: Business Partner is mandatory, the data model is simplified (e.g., VBAP fields moved to other tables, status tables streamlined), foreign trade data moved to International Trade, and SD rebate processing was replaced by settlement management. Fiori apps replace many classic GUI transactions.
Q38. What is the Business Partner approach in S/4HANA SD?
Answer: Instead of separate customer and vendor masters, S/4HANA uses one Business Partner object with roles (e.g., customer, vendor). CVI synchronizes the BP with the classic customer/vendor tables so existing SD processes keep working.
Q39. How does billing integrate with FI?
Answer: When a billing document is released to accounting (VF02), the system posts an accounting document: debit customer receivables (from KNB1 reconciliation account), credit revenue accounts determined by the account assignment (VKOA). This is why SD consultants often coordinate with FI — see our SAP FICO interview questions for the finance perspective.
Q40. What advice would you give a fresher preparing for an SD interview?
Answer: Master the order-to-cash flow end to end, know the key tables (VBAK, VBAP, LIKP, LIPS, VBRK, VBRP, VBFA), understand the condition technique for pricing, and be able to explain copy control and partner determination with examples. Hands-on practice in a sandbox system beats memorizing definitions.
Frequently Asked Questions
Q1. How many questions are in this SAP SD interview guide?
40 real interview questions and answers, covering organizational structure, master data, order-to-cash, pricing, delivery, billing, credit management, and S/4HANA changes — updated for 2026 interviews.
Q2. What is the most frequently asked SAP SD interview question?
“Explain the order-to-cash process” and “Explain the condition technique in pricing” are commonly asked in SD interviews. Know both well, with table names (VBAK, VBAP, KONV) and transaction codes (VA01, VL01N, VF01).
Q3. Are these SAP SD interview questions suitable for freshers?
Yes. The first 25 questions cover fundamentals every fresher should know. Questions 26–40 go deeper for experienced consultants (2+ years), including copy control, item category determination, and S/4HANA simplifications.
Q4. What SAP SD tables should I memorize for interviews?
VBAK, VBAP, VBEP, LIKP, LIPS, VBRK, VBRP, KNA1, KNB1, KNVV, KONV, and VBFA. Know what each stores and the key fields (VBELN, KUNNR, MATNR, NETWR).
Q5. Do interviewers still ask about ECC or only S/4HANA in 2026?
Both. Many companies still run ECC or are mid-migration, so expect questions on classic transactions (VA01, XD01) plus S/4HANA changes (Business Partner, CVI, Fiori). Always mention the S/4HANA angle when answering classic questions.
Conclusion
These 40 SAP SD interview questions cover the full scope of what employers test: process knowledge, configuration concepts, tables, transactions, and S/4HANA awareness. Practice explaining each answer in your own words with a real project example, and walk into your 2026 interview with confidence.