SAP SD interview questions and answers

1. Explain the order-to-cash cycle.

What it tests: Whether you can connect the steps and documents.

Inquiry and quotation where used, sales order, availability check, delivery, picking and packing, post goods issue, billing, posting to accounting, and payment from the customer. Mention the documents created at each step and that post goods issue reduces stock and posts cost of goods sold.

Then describe the flow on a project you know: which steps were automated, where orders were blocked, and who in the business owned each step.

2. What is a sales area?

What it tests: Organisational structure basics that pricing and master data depend on.

A sales area is the combination of sales organisation, distribution channel and division. Customer master sales data, pricing and many document settings depend on it.

Explain how the sales areas were designed on a project you know, and why: for example separate distribution channels for distributors and direct customers, with different pricing.

3. What is copy control?

What it tests: How documents are created from preceding documents.

Copy control defines how data moves from one document to the next, for example from quotation to order, order to delivery and delivery to billing. It is maintained at header, item and, where relevant, schedule line level, with copying requirements and data transfer routines.

Give an example of a copy control change you made or tested, such as copying the purchase order number from the order to the invoice, and how you checked it.

4. What is the incompletion log?

What it tests: Understanding of document checks and how they block later steps.

It lists required fields that are missing in a sales document, and can block subsequent steps such as delivery or billing until the data is complete. Explain an example where an incomplete order stopped a delivery.

5. What is the role of the customer master, and what is stored at each level?

What it tests: Master data knowledge that every sales process depends on.

The customer, a business partner in S/4HANA, holds general data such as name and address, company code data such as the reconciliation account and payment terms for finance, and sales area data such as pricing, shipping and billing settings. Partner functions, for example sold-to, ship-to, bill-to and payer, define who plays which role in a transaction.

Explain one issue you saw from missing or wrong customer data and how it was traced.

6. What is the difference between a standard order, a rush order and a cash sale?

What it tests: Awareness of sales document types and how they change the flow.

A standard order follows the normal delivery and billing flow. A rush order creates the delivery when the order is saved, with billing later. A cash sale creates the delivery when the order is saved and produces an invoice for immediate payment.

1. Explain pricing procedure determination and the condition technique.

What it tests: The core of SD configuration.

The pricing procedure is determined by the sales area, the document pricing procedure on the document type and the customer pricing procedure on the customer master. The condition technique then uses condition types, access sequences and condition tables to find condition records.

Describe a pricing requirement you configured, such as a customer-specific discount with validity dates, and how you tested it.

2. How is the item category determined?

What it tests: Determination logic for different scenarios.

From the sales document type, the item category group in the material master, the usage, and the item category of the higher-level item where there is one. Give an example such as free goods or a bill of materials, where the higher-level item matters.

3. How does revenue account determination work?

What it tests: Integration with finance, and how you trace a billing posting problem.

Configured in VKOA, it typically uses the chart of accounts, sales organisation, account assignment group of the customer and of the material, and the account key from the pricing procedure, such as ERL for revenue.

Describe an error where billing did not release to accounting, and how you found the missing determination.

4. How does the availability check work in a sales order?

What it tests: Whether you can explain confirmed quantities and dates to the business.

The availability check uses the checking group from the material master and the checking rule from the transaction to decide which stock and receipts count, and whether replenishment lead time is included. The schedule line shows the confirmed quantity and date. In S/4HANA, advanced available-to-promise adds options such as product allocation and backorder processing.

Describe a confirmation problem you investigated, such as orders confirmed too late because lead times or the checking scope were wrong.

5. How did you set up credit management?

What it tests: Risk control in order-to-cash and its integration with finance.

Explain credit segments and limits, risk classes, the checks performed at order, delivery or goods issue, and how blocked orders are reviewed and released. In S/4HANA this is SAP Credit Management, with the business partner holding credit data and a credit analyst releasing blocked documents.

Say how the checks were agreed with finance and how many blocks the sales team could tolerate before the process was adjusted.

6. Explain the consignment processes in SD.

What it tests: Knowledge of special business processes and the documents each step creates.

Customer consignment has four steps: consignment fill-up, consignment issue when the customer uses the goods, consignment pick-up when stock comes back, and consignment return when the customer returns goods already billed. Say which steps create billing.

Fill-up and pick-up do not create customer billing; issue and return do. Describe how stock was monitored at customer sites in your project and how the business reconciled it.

7. How do third-party and intercompany sales work?

What it tests: Cross-module and cross-company flows.

In third-party sales, the order item creates a purchase requisition and the supplier delivers directly to the customer. In intercompany sales, one company sells and another delivers, with an intercompany invoice between them. Mention the settings that make each work.

For third-party, the item category and schedule line category create the requisition and the supplier invoice drives billing quantities. For intercompany, the delivering plant is assigned to the selling sales organisation and an internal customer represents the selling company. Describe the flow you supported and how the two companies reconciled.

1. What changes for sales in S/4HANA?

What it tests: Whether your knowledge is current, and what changes for users and data.

Customers are business partners. Credit management moves to SAP Credit Management. Rebate processing is replaced by settlement management with condition contracts. Output management can use the new framework based on BRF+. Fiori apps change how users monitor orders and billing.

Say which of these you delivered, and the migration impact on open documents.

2. How would you design order-to-cash for a business with several channels?

What it tests: Design judgement, and whether you start from the business rather than the system.

Start with the business: channels, pricing policies, fulfilment models and reporting. Then the design: sales organisations and distribution channels, document types, pricing strategy and credit control. Show that you would keep the design as simple as the business allows.

Explain the trade-off you made on a real project between a richer structure and simpler maintenance, and how the decision held up after go-live.

3. How do you approach migration of open sales documents and customer data?

What it tests: Whether you have owned cutover and reconciliation, not only configuration.

Cover deciding which open orders to migrate or close, mapping customer data to business partners, reconciling open items with finance, and testing the end-to-end flow on migrated data before go-live.

4. How do you handle returns and credit memos in your design?

What it tests: End-to-end thinking across sales, logistics and finance.

Cover the returns order, the returns delivery and goods receipt with the right stock type, inspection where quality is involved, and the credit memo with or without a credit memo request. Explain how approvals and blocks protect against unjustified credits, and how the flow is reported to finance.

Describe how your design handled a real returns scenario, such as damaged goods or wrong deliveries.

5. Tell me about a time a requirement could not be met in standard.

What it tests: Judgement on enhancements versus process change.

Explain the requirement, the options you considered, including changing the process instead of the system, the decision and the result. Interviewers value consultants who protect the standard where they can.