π SAP SD (Sales & Distribution) interview guide
Master the Order-to-Cash cycle, pricing procedure, copy control and account determination, plus the S/4HANA changes every SD interview now includes.
Order-to-CashPricingATPCredit MgmtBilling
SAP Sales and Distribution (SD) runs the Order-to-Cash (O2C) process: from enquiry and quotation through sales order, delivery, goods issue and billing to the customer payment. SD is one of the most common SAP interview topics because it touches pricing, logistics and finance at once.
π Jump to the scored SD test
What is SAP SD?
SD covers pre-sales, sales order processing, availability and credit checks, shipping, billing and the handover to Finance. In S/4HANA it is part of Sales in the LoB Sales and Order Management, working with SAP Credit Management, advanced ATP, Settlement Management and Revenue Accounting.
Key scenarios you should know: standard order (OR), rush order and cash sales, consignment (fill-up, issue, pick-up, return), third-party and individual purchase orders, returns, credit and debit memos, scheduling agreements and contracts, and intercompany sales.
End-to-end process: Order-to-Cash (O2C)
“Explain the Order-to-Cash cycle” is the most common SD question. Name the document at each step, what is copied, and what posts in FI.
- Enquiry & quotation
VA11 / VA21
Pre-sales documents record customer interest and binding offers with validity dates. They are copied into the order. - Create sales order
VA01 Β· Type OR
The order captures sold-to and ship-to parties, materials, quantities and dates. Partner, item category and schedule line determination happen automatically. - Pricing & ATP
Pricing proc Β· ATP
The pricing procedure computes price, discounts, freight and tax through condition technique. ATP confirms quantity and delivery dates. - Credit check
UKM_BP Β· VKM1
SAP Credit Management checks exposure against the credit limit. Blocked orders go to a credit controller for release. - Create delivery
VL01N / VL10B
The outbound delivery is created from due orders by shipping point, with route and dates from delivery scheduling. - Pick & pack
EWM / WM Β· Packing
Warehouse tasks pick the goods, then the goods are packed into handling units. - Post goods issue
VL02N Β· Mvt 601
PGI reduces stock, posts cost of goods sold in FI and updates document flow. Ownership transfers to the customer. - Billing
VF01 / VF04
The invoice is created from the delivery (or from the order for services). Copy control and billing type decide what is copied. - Post revenue to FI
VKOA Β· Acct determination
Revenue, discount and tax accounts are determined automatically and the accounting document posts to the customer account. - Output & e-invoice
BRF+ output mgmt
Invoices are output via print, email, EDI or e-invoicing channels such as GST e-invoice in India. - Customer payment
F-28 / Bank stmt
The incoming payment clears open items in FI-AR. Dunning handles overdue invoices. - Returns & credit memo
RE / CR Β· VA01
Returns orders, return deliveries (mvt 651) and credit memos handle complaints, and the cycle feeds analytics.
Organizational structure & master data
Organizational structure
Sales organisation
Assigned to exactly one company code. Many sales orgs can share one company code.
Distribution channel and division
Combined with the sales org to form a sales area, which is assigned to sales offices.
Plant assignment
Plants are assigned to sales org and distribution channel combinations to allow delivery from that plant.
Shipping point
Assigned to plants. Determined from shipping condition, loading group and plant.
Sales office and sales group
Optional units for sales responsibility.
Credit segment
In SAP Credit Management, credit limits are controlled per credit segment assigned to the credit control area.
Master data
Business Partner (BP)
In S/4HANA, customers are created through BP with roles (FLCU00 for FI, FLCU01 for sales). Partner functions: SP, SH, BP, PY.
Material master sales views
Sales org 1 and 2 and Sales: General/Plant, with item category group, delivering plant, loading group and tax classification.
Condition records (VK11)
Prices, discounts, surcharges and freight maintained per access sequence key combination.
Customer-material info record (VD51)
Maps the customer material number to your material number.
Credit master data
Credit limit, risk class and check rule per credit segment (UKM_BP).
Output condition records
Determine when and how documents like order confirmations and invoices are sent.
Key T-codes & Fiori apps
Interviewers often ask you to name the transaction or app for a step. You do not need to memorise hundreds, but you should know these confidently.
| T-code / App | What it does |
|---|---|
| VA01 / VA02 / VA03 | Create / change / display sales order |
| VA11 / VA21 | Create enquiry / quotation |
| VA41 | Create contract |
| VL01N / VL02N | Create / change outbound delivery (PGI) |
| VL10B | Delivery due list |
| VF01 / VF04 / VF11 | Create billing / billing due list / cancel billing |
| VK11 / VK12 | Create / change condition records |
| V/08 | Maintain pricing procedure |
| OVKK | Pricing procedure determination |
| VTAA / VTLA / VTFL | Copy control (order to order / delivery / billing) |
| VKOA | Revenue account determination |
| UKM_BP / UKM_CASE | Credit management master data / credit cases |
| BP | Maintain Business Partner (customer) |
| Fiori: Create Sales Orders, Manage Sales Orders, Sales Order Fulfillment Issues | Modern sales and fulfilment apps |
What changed in S/4HANA
- Business Partner is mandatory: customer master transactions (XD01, VD01) redirect to BP, with Customer-Vendor Integration (CVI).
- SAP Credit Management (FSCM) replaces classic SD credit management (FD32): credit segments, scoring and credit cases.
- Simplified data model: status tables VBUK and VBUP are removed (statuses move into VBAK, VBAP, LIKP and LIPS), and document flow VBFA is streamlined.
- Settlement Management with condition contracts replaces classic SD rebate agreements.
- Advanced ATP (aATP) brings product allocation, backorder processing and alternative-plant confirmation.
- Output Management with BRF+ is the default, alongside NAST-based output for compatibility.
- SD analytics move from LIS (VIS tables) to embedded analytics with CDS views and Fiori apps.
Integration points
| With | How it integrates |
|---|---|
| FI | PGI posts COGS. Billing posts revenue, tax and the customer receivable through VKOA account determination. Payments clear in FI-AR. |
| MM | Third-party orders create PRs to vendors. Stock availability, batches and consignment special stock. |
| PP | Make-to-order: sales order requirements drive MRP and production with sales order stock (E). |
| CO-PA | Billing values and costs flow into margin analysis by customer, product and region. |
| LE / EWM | Delivery, picking, packing, transport and goods issue processing. |
| PS | Customer projects link sales orders to billing WBS elements with billing plans. |
| Credit Management | Credit exposure from orders, deliveries and open invoices checked against limits. |
Interview questions & answers
Tap a question to see a model answer. They are grouped from fundamentals to scenario-based questions that senior panels love.
π’ Fundamentals
Explain the Order-to-Cash cycle. Beginner
Enquiry (VA11) and quotation (VA21) are optional. Then: sales order (VA01) with pricing, ATP and credit check, outbound delivery (VL01N), picking and packing, post goods issue (mvt 601, which posts COGS), billing (VF01, which posts revenue and the receivable), and finally the customer payment in FI-AR. Returns and credit memos handle exceptions.
What is a sales area? Beginner
The combination of sales organisation, distribution channel and division. Customer sales data, pricing and many controls are maintained per sales area.
What is the condition technique? Beginner
The method SAP uses for pricing, output, text and other determinations. A pricing procedure holds condition types in sequence. Each condition type has an access sequence that searches condition tables (key combinations) for condition records from most specific to most general.
How is the pricing procedure determined? Beginner
In OVKK by sales area + document pricing procedure (from the sales document type) + customer pricing procedure (from the customer master sales area data).
What is copy control? Beginner
Settings that define how data is copied from a source document to a target document: VTAA (order to order), VTLA (order to delivery) and VTFL (delivery or order to billing). It controls header, item and schedule line copying, requirements, data transfer routines and pricing type.
How is the item category determined? Beginner
From the sales document type + item category group (material master) + usage + higher-level item category in VOV4. Examples: TAN (standard), TAS (third-party), TANN (free of charge), KBN/KEN (consignment fill-up / issue).
What happens at post goods issue? Beginner
Stock is reduced (mvt 601), an FI document posts COGS against the inventory account, the delivery status is updated, and the item becomes relevant for billing.
π‘ Intermediate
Explain the third-party sales process. Intermediate
The order item with item category TAS automatically creates a purchase requisition. Purchasing converts it to a PO to the vendor, who ships directly to the customer. You post a statistical GR (optional) and the vendor invoice (MIRO), then bill the customer based on the invoice receipt or order quantity, depending on copy control and the billing relevance of TAS.
Explain the consignment process. Intermediate
Fill-up (KB): stock moves to customer consignment stock (special stock W), still owned by you. Issue (KE): the customer uses the stock, ownership transfers and you bill. Pick-up (KA): stock returns to you. Returns (KR): the customer returns consumed goods, which go back into consignment stock with a credit memo.
How does revenue account determination work? Intermediate
VKOA uses condition technique with account keys from the pricing procedure (ERL revenue, ERS discounts, ERF freight, MWS tax) combined with the chart of accounts, sales org, customer account assignment group and material account assignment group to find the G/L account.
What is the difference between the requirement and the alternative calculation type in pricing? Intermediate
A requirement is a routine that decides whether a condition is applied at all, for example only if the item is relevant for pricing. An alternative calculation type replaces the standard calculation formula, and an alternative base value changes the base the condition is calculated on.
What changed in credit management in S/4HANA? Intermediate
Classic SD credit management (FD32, credit control area checks) is replaced by SAP Credit Management: credit segments, BP credit profiles (UKM_BP), scoring rules, documented credit decisions and credit cases. The order still blocks when the check fails, and release is through UKM_MY_DCDS or VKM1.
How does intercompany sales work? Intermediate
Sales org A sells goods delivered from plant B of another company code. The customer is billed by company A (invoice F2). Company B bills company A internally with an intercompany invoice (IV), using condition PI01 for the transfer price. The internal customer represents company A in company B.
π΄ Scenario & design
A customer complains that a discount is not appearing on the order. How do you troubleshoot? Scenario
Open the pricing analysis on the item (condition tab β Analysis). Check whether the condition type is in the procedure, whether the access sequence found a valid record for the key and date, any requirement routine blocking it, and exclusion groups. Then check the validity of the condition record (VK13) and the master data fields used in the key.
Orders are getting blocked for credit even for good customers. What would you check? Scenario
The credit segment and limit on BP (UKM_BP), the check rule, exposure including open orders and deliveries, the risk class, any overdue items check, and the item category’s credit activation. Consider automatic limit calculation based on scoring and adjust check rules per risk class.
How would you design returns for damaged goods? Scenario
Returns order (RE) with an order reason. A return delivery (LR, mvt 651) posts into blocked stock. Inspect through QM or manually, then transfer to unrestricted or scrap. Create the credit memo from the returns order with a billing block until inspection is done. In S/4HANA, consider Advanced Returns Management for refund control and logistics follow-up.
The business needs volume rebates. What do you propose in S/4HANA? Scenario
Settlement Management with condition contracts (such as customer rebate contracts). Define eligible customers and materials, rebate conditions and accrual conditions, and periodic or final settlement creating credit memos. Business volume is calculated from billing documents through CDS views.
How would you implement GST e-invoicing for Indian sales? Scenario
Use SAP Document and Reporting Compliance (eDocument framework). Billing creates an eDocument, which is submitted to the IRP via an integration (often SAP Integration Suite or a GSP). The IRN and QR code return and print on the invoice. Handle cancellation within the allowed window, and handle e-way bills for deliveries.
How do you handle make-to-order sales? Scenario
The item category (such as TAW) with a requirement type for MTO creates sales order stock (special stock E). MRP plans production against the order. A production order receipt goes to sales order stock, and delivery and PGI issue from it. Results analysis or settlement may be used on the sales order item for costing.
What testing would you plan for an SD rollout to a new country? Scenario
Unit tests for org structure, pricing and tax. Integration tests across the full O2C chain with FI postings, outputs and legal invoices. Country-specific cases: tax codes, e-invoicing, number ranges, currencies and language. Data migration rehearsals for BP, open orders and condition records. Cutover testing and user acceptance.
Solution architect view
Key SD design decisions:
- Enterprise structure: the number of sales orgs (legal and pricing autonomy), distribution channels and divisions. Too many sales areas multiplies master data maintenance.
- Document types and item categories: keep a lean standard set and extend only for genuine process differences.
- Pricing strategy: pricing procedure design, condition tables by access level, and integration with SAP CPQ or a pricing engine if needed.
- Credit and risk: SAP Credit Management rules, credit segments and scoring.
- Fulfilment: aATP, EWM integration and transportation management.
- Compliance: e-invoicing (DRC), tax engines, and revenue accounting (IFRS 15) through RAR where needed.
- Front-office integration: SAP Sales Cloud / CX, e-commerce and EDI for order intake via Integration Suite.
Typical deliverables: O2C process design, pricing design workbook, output and form catalogue, interface specifications (EDI, CRM, tax), and data migration design for BP, conditions and open orders.
Test yourself: scored SD quiz
Interview tips
π‘ How to stand out
- Narrate O2C with documents, T-codes and FI postings at PGI and billing.
- Practise explaining condition technique with a real pricing procedure example.
- Know at least four special processes: third-party, consignment, intercompany, returns.
- Mention S/4HANA changes: BP, Credit Management, condition contracts, aATP, simplified tables.
- For architect roles, talk about how you reduced sales areas or document types to simplify the design.
Keep preparing: π― SAP Interview Prep hub & combined mock test Β· All SAP interview guides Β· ERP Software
