SAP SD (Sales and Distribution) handles the order-to-cash process. These SAP SD interview questions cover sales documents, organisational structure and master data for freshers, then pricing, copy control, credit management, account determination and integration for experienced SD consultants.
30 questions · Updated
Fundamentals, definitions and simple scenarios. Good for freshers and warm-ups.
An inquiry and quotation (optional) lead to a sales order (VA01), then an outbound delivery (VL01N) with picking, packing and post goods issue, which reduces stock and posts cost of goods sold. Then billing (VF01) creates the invoice and posts revenue and the customer receivable to FI, and finally the customer payment is received and cleared in FI.
Sales organisation (responsible for selling and its liability), distribution channel (how products reach customers, such as retail, wholesale or online), division (a product line), and the sales area, which is the combination of the three.
Sales offices and sales groups represent internal structure.
On the shipping side, plants and shipping points are used.
The customer master, now a Business Partner in S/4HANA, with general, company code and sales area data, and partner functions such as sold-to, ship-to, bill-to and payer. The material master sales views, pricing condition records, the customer-material info record and output records are also key master data.
IN (inquiry), QT (quotation), OR (standard order, TA in German), CS (cash sale), RO (rush order), CR (credit memo request), DR (debit memo request), RE (returns), KB to KE (consignment orders) and contracts such as WK1 and WK2. The document type controls numbering, required fields, pricing, delivery and billing relevance and the item categories used.
VA01, VA02 and VA03 (create, change and display sales orders), VA21 (quotation), VL01N and VL02N (outbound delivery and post goods issue), VF01 and VF04 (billing and billing due list), VK11 (condition records), VD51 (customer-material info record), BP (business partner in S/4HANA), VKM3 (release blocked orders), VA05 (list of sales orders) and VF31 (output from billing).
A shipping point is the location that processes outbound deliveries, such as a dispatch dock.
It is determined automatically in the sales order from the delivering plant, the shipping condition from the customer master or sales document type, and the loading group from the material master.
It can be changed manually if several shipping points are allowed.
The availability check (ATP, available to promise) confirms whether the ordered quantity can be delivered on the requested date, considering stock, planned receipts and existing commitments according to the checking group and checking rule.
If stock is not available, the system proposes a later date or partial delivery.
In S/4HANA, advanced ATP adds product allocation and back-order processing.
Partner determination assigns business partners to sales documents in their roles: sold-to party (places the order), ship-to party (receives the goods), bill-to party (receives the invoice) and payer (pays). Partners are proposed from the customer master, and partner determination procedures control which partner functions are mandatory and changeable for each document type.
An incompletion procedure lists fields that must be filled in a sales document, such as purchase order number, payment terms or shipping conditions.
If required data is missing, the document is saved as incomplete and can be blocked for delivery or billing according to the status group.
The incompletion log (VA02) shows what is missing.
F2 (standard invoice), F1 (order-related invoice), G2 (credit memo), L2 (debit memo), RE (credit for returns), S1 (cancellation of an invoice), BV (cash sale) and IV (intercompany billing). The billing type controls number ranges, account determination, output and whether the document posts to accounting.
Output determination decides when and how documents such as order confirmations, delivery notes and invoices are sent: printed, emailed as PDF or sent through EDI.
In ECC this uses condition records for output types such as RD00 for invoices; in S/4HANA, BRF+-based output management determines output types, channels and forms.
VF31 processes invoice output in bulk.
Applied problems, trade-offs and questions about your own projects.
SD pricing uses the condition technique.
The pricing procedure (such as RVAA01) is determined from the sales area, the customer pricing procedure and the document pricing procedure.
It lists condition types such as PR00 base price, K004 or K007 discounts, freight and taxes.
Each condition type has an access sequence that searches condition tables, from most to least specific, for valid condition records.
Copy control defines how data is copied from one document to the next, for example from quotation to sales order, sales order to delivery, or delivery to invoice. It is configured between document types (VTAA, VTLA, VTFL and so on) with copying requirements, data transfer routines and item category settings, which control whether pricing is copied or redetermined.
The item category controls how an item behaves in a sales document: whether it is priced, relevant for delivery or billing, and so on.
It is determined from the sales document type, the item category group in the material master and usage.
TAN is a standard item, TANN a free item.
Schedule line categories control delivery dates and whether MRP and stock movement happen, with movement type 601 for goods issue.
Credit management sets a credit limit for each customer and checks orders and deliveries against their exposure (open orders, deliveries, invoices and receivables).
Orders over the limit or with overdue items can be blocked for review and released by a credit controller.
In S/4HANA, SAP Credit Management (FIN-FSCM-CR) replaces the older credit control area approach, with credit scoring and risk classes.
A route defines the path and transit time from a shipping point to the customer and is used for delivery scheduling.
It is determined from the departure zone of the shipping point, the shipping condition, the transportation group of the material and the transportation zone of the ship-to party, and can also consider weight.
Transit and loading times feed into the delivery date calculation.
Transfer of requirements passes the demand from sales orders to materials planning, so MRP knows what is needed and when.
It is controlled by the schedule line category and the requirements type and class, determined from the strategy group or item category.
It lets production and purchasing plan to meet confirmed customer orders.
Free goods are configured with free goods determination using the condition technique.
Inclusive free goods are included in the ordered quantity (buy 10, pay for 9), while exclusive free goods are added as a separate item with item category TANN and no charge (buy 10, get 1 extra).
Free goods records are maintained with VBN1.
Rebates are discounts paid retrospectively to customers based on sales volume over a period.
In ECC, rebate agreements (VBO1) with condition records accrue rebate amounts with each invoice and are settled with credit memos.
In S/4HANA, rebate processing is replaced by settlement management with condition contracts, which handle accruals and settlements more flexibly.
A sales bill of materials lets one sellable material represent a set of components, such as a computer package.
Processing can be at header level, where pricing and inventory are handled on the main item (item category group ERLA), or at item level, where components are priced and delivered individually (item category group LUMF).
The BOM components explode automatically in the sales order.
When a sales organisation sells goods delivered from a plant belonging to another company code, the delivering company code ships the goods and two billing documents are created: the customer invoice from the selling company code and an intercompany invoice (IV) from the delivering company code to the selling company code, priced with intercompany conditions such as PI01.
Variant configuration handles products with many options, such as cars, furniture or computers, without creating a material for every combination. A configurable material uses characteristics and values (colour, engine, size), dependencies and constraints ensure valid combinations, and the configuration drives pricing with variant conditions and selects components in the bill of materials and routing for production.
System design, deep internals, leadership and tough follow-ups.
When billing is posted, the GL accounts are found through transaction VKOA using the condition technique: the chart of accounts, sales organisation, customer account assignment group, material account assignment group and account key (such as ERL for revenue, ERS for discounts and MWS for output tax). Missing settings here are a common reason for a billing document failing to post to accounting.
Returns (RE order, returns delivery and credit memo), credit and debit memo requests, consignment (fill-up, issue, pick-up and return), third-party sales where the vendor ships directly to the customer, make-to-order production, cash sales and rush orders, free-of-charge deliveries, rebate agreements, and intercompany sales between company codes with internal billing.
With MM through availability checks, stock and goods issue; with FI through billing, revenue and receivables, plus credit management; with CO through profitability analysis (CO-PA) when billing documents are posted; with PP for make-to-order and planning; and with logistics execution (shipping and warehouse management). An SD consultant must understand these flows to debug issues that cross modules.
Customers became Business Partners, status tables VBUK and VBUP were removed with status fields moved to the document tables, rebates moved to settlement management, credit management moved to SAP Credit Management, foreign trade moved to SAP Global Trade Services, output management uses BRF+, and advanced ATP and Fiori apps replaced many classic transactions.
Check the accounting status of the billing document and the error log in VF02 or the list of blocked billing documents (VFX3).
Common causes are missing revenue account determination in VKOA, missing or wrong customer or material account assignment groups, closed posting periods, missing cost centres or profit centres, and tax code problems.
After correcting the cause, release the document to accounting.
Open the item conditions and use the pricing analysis to see which condition types were found and which condition records were used, step by step through the access sequence. Check whether the right pricing procedure was determined, whether condition records exist and are valid for the date and key combination, whether manual changes were made, and whether pricing was copied or redetermined through copy control.
Businesses above the turnover threshold must report B2B invoices to the Invoice Registration Portal and receive an Invoice Reference Number and signed QR code before sending the invoice.
SAP supports this with Document and Reporting Compliance (eDocument), connecting through SAP integration services or GST Suvidha Providers.
The IRN and QR code are stored with the billing document and printed on the invoice, and e-way bills can be generated too.
Advanced available-to-promise adds product allocation to share scarce stock between customers, regions or channels, back-order processing to reassign confirmed quantities based on priorities when supply changes, alternative-based confirmation to check other plants, and release for delivery to manage confirmations before deliveries are created. It helps companies make reliable promises when supply is limited.
See all SAP & CRM Consultant interview questions, covering SAP FICO, SAP MM, SAP SD, SAP ABAP, Salesforce and more.