SAP SD interview questions

An SAP SD interview tests whether you can design and defend how a company sells. The scenarios follow order-to-cash: the sales structure and the order types, pricing through the condition technique, availability and delivery, the blocks that stop a document, billing and the accounts revenue lands in, and the backlog that has to survive a cutover. Each is asked as a situation with a consequence, and this guide goes through them that way.

How is an SD interview different from a sales quiz?

Because the sales area is the most visible one in a company — the order desk, the warehouse and the accounts receivable team all live in its documents — an SD interviewer can put you in front of a live-sounding problem within minutes. The quiz asks what a sales area is. The interview says: "A distributor sells the same products through its own sales force and through a web shop, with different prices and different delivery promises. Set it up." Then it changes a fact — the web shop now ships from a third-party warehouse — and watches what you change. The functional interview guide has the general shape; the sales content below is what fills it.

Which structure and order-type scenarios get tested?

The distributor above is really a question about the sales organisation, the distribution channel and the division, and whether the second channel deserves its own or only a different price list. Good answers say what each object is for — the legal and reporting unit, the route to the customer, the product line — and name what is expensive to change later. The order-type questions follow: what a sales document type controls, what an item category decides that the document type does not, how schedule lines carry the delivery promise, and how copy control decides what flows from the quotation to the order to the delivery to the invoice. "The business wants a rush order that ships the same day and invoices immediately" is the classic, because the answer is a set of controls rather than a new program.

How does pricing come up?

As the section where the interviewer finds out whether you have built one. "A customer gets a list price, a customer-specific discount, a promotional discount for one month and freight. Show me how the system finds each." The condition technique is the mechanism — a pricing procedure made of condition types, each with an access sequence that searches condition tables from the most specific key to the most general — and the judgment is in the order and the exclusions: which discount wins when two apply, what a manual condition may override, where tax sits. Follow-ups are diagnostic: "The discount is not being found for one customer." The people who have done it answer with the analysis screen and the missing record; the people who have read it answer with a definition.

What do availability, delivery and blocks look like?

"An order confirms a date the warehouse cannot meet. What decided the date?" tests availability checking — the checking rule, what stock and what inbound supply it counts, and how the confirmation lands on the schedule line. Delivery questions walk the document: creation, picking, packing, the goods issue that posts stock out and cost of sales in, and the point at which sales stops owning the process and logistics does. Blocks are asked as operations: a credit block on a customer over limit, a delivery block on an order the finance team is disputing, and who may release each — with the follow-up "and what happens to the customer's other orders while it is blocked", which is the question that shows whether you think in one document or in the flow.

How are billing and the revenue accounts asked?

"Revenue for one product line is landing in the general revenue account." The chain to describe is account determination on the sales side: the customer's and the material's account assignment groups, the condition type, the chart of accounts, and the record that maps the combination to an account. Billing questions add the document itself — billing types, why an invoice splits when the business expected one, collective billing across deliveries, credit and debit memos and the request documents in front of them — and the moment the accounting document is created, which is where the finance interviewer picks up the same scenario. Say who reads the revenue account and why it matters that the split is by product line; that sentence is the difference between configuring and understanding.

What does the document-flow scenario test?

"Here is an invoice the customer disputes. Take me back to what caused it." The interviewer wants you to read the document flow backwards — invoice, delivery, order, quotation, and the contract or the price record behind it — and to say at each step what could have gone wrong there and what would show it. It is the sales version of the debugging narrative every track gets, and it rewards the same thing: a sequence, aloud, that establishes what happened before proposing a fix. Candidates who reach for a correction before they have read the flow are marked down, however correct the correction.

How is the cutover backlog scenario asked?

"We go live at the start of a month with open orders, deliveries in transit and invoices not yet paid. What comes across?" The structure: master data first — customers as business partners with their sales views, materials with theirs, price records — then a decision for each kind of open document. Open orders are usually recreated so that the new system delivers and bills them; deliveries in flight are the hard case, finished in the old system or reloaded at the exact stage they reached; open receivables come across as finance open items, not as invoices. Proof is a reconciliation of the backlog by count and value, signed by the sales lead; the cutover guide shows where in the weekend that load sits.

Which SD scenarios should you rebuild before the interview?

• One sales structure from memory, with the reason for each channel and division and the one you would not create again.
• A pricing procedure you built, condition by condition, including the exclusion that took a week to get right.
• One document flow read backwards, from a real dispute, told as the diagnosis you did.
• The revenue chain from a billing document to its accounts, and the setting on each side that controls it.
• The procurement mirror: the MM interview guide asks the same chain from the buying side, and the umbrella guide names what every track has in common.