Sales Documents

Lessons in this topic

• SD Sales Documents Part 1: Document Structure and Document CategoriesHow SAP sales documents are built (header, item, schedule line) and which document categories exist across the sales cycle: inquiry, quotation, standard order, contracts, scheduling agreements, returns, free-of-charge deliveries and credit/debit memo requests.
• SD Sales Documents Part 2: Sales Document Type Configuration (VOV8)Configure a sales document type in VOV8: document category, number ranges, reference and division checks, credit and ATP-related groups, default delivery and billing types, blocks, date proposals, contract data, incompletion procedure and pricing procedure key, plus restricting document types to sales areas.
• SD Sales Documents Part 3: Referencing, Document Flow and CompletionHow sales documents are created with reference and linked: create with reference, what is copied, document flow (VBFA), referenced quantities and completion rules for quotations and contracts, rejection reasons, and how to read the flow when troubleshooting — as the bridge to the Copy Control topic.
• SD Sales Documents Part 5: Architecting Sales Document Landscapes — Governance and S/4HANA MigrationArchitect's view of sales document design: a small canonical set of document types, when a new type is justified, naming and numbering conventions, dependency management across copy control, pricing and output, and how to simplify legacy document type proliferation during an S/4HANA migration.
• SD Sales Documents Part 4: Incompletion, Status and Document BlocksKeep sales documents clean and controlled: incompletion procedures and status groups that stop delivery or billing of incomplete documents, the incompletion log, document status fields, user status profiles, and delivery, billing and credit blocks at header, item and schedule line level.

Interview questions covered

• A make-to-order sales order item is saved successfully despite missing an MTO-critical field—the requested ship-to plant override needed for correct production order determination—and the production order later pulls the wrong plant. How would you diagnose why the incompletion procedure did not catch this, and how would you correct it?
• You need to design a free-of-charge delivery process for promotional samples that must still consume ATP and update requirements planning, but must not create billing documents. What architecture would you propose?
• What is the business purpose of the Inquiry document type (IN) in the SAP sales cycle, and does it create any commitments in MM or affect stock?
• In a Make-to-Order (MTO) scenario, how would you configure the incompletion procedure for a Quotation to ensure that critical MTO-relevant fields like the requested delivery date and configuration data are captured before the quotation can be released for order creation?
• What is material (product) substitution in SD order processing, and how is it configured to work within specific sales document types?
• When configuring number ranges for a new sales document type that must be visible in a Fiori app for order creation, what configuration steps and constraints must be validated?
• In a make-to-order scenario integrating with production, how do sales-related blocks (delivery block, billing block) interact with the incompletion procedure to prevent premature downstream processing?
• As a lead architect, walk through how you would design and govern incompletion procedure assignment across inquiry, quotation, and sales order document types in a lead-to-order cycle, including how status groups differentiate fields that block saving versus fields that only block subsequent processing (like delivery or billing).
• You are designing the global sales document type strategy for a multi-country S/4HANA rollout that must support standard orders across both make-to-stock and make-to-order flows without proliferating document types per country. What architectural approach would you take?
• Walk through the end-to-end process design for configuring scheduling agreements with forecast and JIT delivery schedules feeding MM/PP, including the document type control settings that differentiate forecast versus JIT delivery schedules and how these affect requirements transfer timing.
• From an end-to-end design perspective, how do Quantity Contracts and Value Contracts differ in document type configuration, and what governs how release orders are created and tracked against them?
• What is the purpose of a delivery block versus a billing block on a sales order, and at what levels can each be set?
• A customer contract for annual pricing agreements is being created, but users report the system won't let them save without a valid end date and target quantity. How would you analyze and address this using the incompletion procedure?
• After go-live, a large share of orders is blocked every morning due to incompletion. Business says the fields are "nice to have". How do you redesign incompletion and blocking?
• A sales order item does not appear in the delivery due list (VL10) although the order is saved. How do you investigate systematically?
• A retailer asks for a new order type ZOR2 that differs from ZOR only in the invoice form layout. How do you respond and what would a correct setup look like?
• A distribution company complains that orders created from quotations lose the negotiated prices, and some quotations remain open after conversion. How do you analyse it?
• A consumer goods company running a multi-country S/4HANA template ends up with 40 order types after three waves. Global reporting and support suffer. How do you bring the landscape back under control?

Related topics

Interview questions on this topic

• SAP SD / O2C Sales Documents interview questions
• SAP SD / O2C interview questions