SD Sales Documents Part 1: Document Structure and Document Categories

📌 KEY POINTS
✅ Every sales document has three levels: header (VBAK), item (VBAP) and schedule line (VBEP) — each controlled by its own configuration key (document type, item category, schedule line category).
✅ The document category (VBTYP) says what kind of document it is: inquiry, quotation, order, contract, scheduling agreement, returns, credit/debit memo request.
✅ Presales documents (inquiry, quotation) create no requirements and no postings; orders create requirements for delivery and billing.
✅ Outline agreements (contracts, scheduling agreements) are fulfilled by release orders or delivery schedules.
⚠️ Choosing the wrong document category (e.g. using a standard order for returns) breaks the logistics and billing flow — the category, not the name, decides behavior.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Document structure and document categories
Part 2: Sales document type configuration (VOV8)
Part 3: Referencing, document flow and completion
Part 4: Incompletion, status and blocks
Part 5: Architecting sales document landscapes — governance and S/4HANA migration

━━━━━━━━━━━━━━━━━━━━
▶ 1. HEADER, ITEM, SCHEDULE LINE

• Header: customer, sales area, document type, dates, header partners, header pricing.
• Item: material, quantity, item category, plant, item pricing.
• Schedule line: delivery dates and confirmed quantities from availability check.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PRESALES DOCUMENTS

• Inquiry (IN): customer asks for information; tracked for lost-sales analysis.
• Quotation (QT): binding offer with validity dates; converted to orders by reference.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ORDERS

• Standard order (OR): delivery- and billing-relevant.
• Rush order (SO): delivery created on save; cash sale (CS): invoice printed immediately.
• Free-of-charge delivery (FD): delivery without billing.

━━━━━━━━━━━━━━━━━━━━
▶ 4. OUTLINE AGREEMENTS

• Quantity contract (CQ) and value contract (WK1/WK2): released by release orders.
• Scheduling agreement (DS/LZ): delivery schedules with dates and quantities over time.
• Master contracts group contracts.

━━━━━━━━━━━━━━━━━━━━
▶ 5. COMPLAINTS

• Returns (RE): goods back via returns delivery, credit via billing.
• Credit memo request (CR), debit memo request (DR): financial corrections, billed without delivery.
• Invoice correction request (RK): corrects billed quantities or prices.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Create a quotation with VA21.
2. Create an order with reference to it (VA01 > Create with Reference).
3. Look at header, item and schedule line tabs.
4. Check document flow from quotation to order.

✅ CHECKPOINT: you can name the document category and the three levels of any sales document you open.

A medical-device distributor handled customer complaints about damaged goods by creating standard orders with negative pricing conditions. Finance could not reconcile these "orders", returned goods never went back into stock, and revenue reports were distorted. The team introduced proper complaint documents: returns (RE) with returns delivery and inspection for physical returns, and credit memo requests (CR) with billing block and approval for price-only corrections. Credit notes became traceable in document flow and complaint KPIs were reportable by reason.

• Using standard orders with manual price changes instead of returns or credit memo requests.
• Treating inquiries and quotations as if they created requirements.
• Confusing document type (a name, e.g. ZOR) with document category (behavior).
• Using contracts where scheduling agreements fit (or vice versa).
• Looking for status in VBUK/VBUP in S/4HANA.

• Map every business process to the right document category first.
• Use presales documents to track lost business (rejection reasons).
• Use complaint documents for every correction — never manual workarounds.
• Keep the number of custom document types small (Part 5).
• Use document flow to explain any document's history.

Questions: "What levels does a sales document have?", "Difference between inquiry and quotation?", "Contract vs scheduling agreement?"
Strong answer: header/item/schedule line (VBAK/VBAP/VBEP) with their control keys; document categories across presales, orders, outline agreements and complaints; presales create no requirements; contracts are fulfilled by release orders, scheduling agreements by delivery schedules. Mentions VBUK/VBUP merge into VBAK/VBAP in S/4HANA.