3.1 Sales Document Header Architecture and Customizing Sales Document Types

Sales Document Header Architecture and Customizing Sales Document Types

Quick Summary: In SAP S/4HANA Sales, every commercial transaction is captured as a sales document structured across three levels: Header (table VBAK), Item (table VBAP), and Schedule Line (table VBEP). The sales document type, configured in transaction VOV8, dictates overall processing, number ranges, credit check triggers, immediate delivery behavior, and default billing document assignment.

---

The Three-Tier Sales Document Structure

To manage commercial transactions, SAP S/4HANA organizes sales documents into a three-tier hierarchical data model. Each tier serves a specific business purpose, stores distinct functional data, and links to specialized database tables.

1. Header Level (Table VBAK)

The header contains data that is valid for the entire sales document without exception. Key header attributes include:

• Sold-to Party & Partner Functions: The ordering customer, ship-to location, bill-to payer, and contact persons.
• Pricing & Currency: Header pricing conditions, customer currency, document exchange rate, and overall pricing date.
• Sales Area Assignment: The combination of Sales Organization, Distribution Channel, and Division defining the commercial organizational channel.
• Administrative & Control Data: Document creation date, created-by user, delivery blocks, and billing blocks.

Architectural Simplification in SAP S/4HANA

In classic SAP ERP Central Component (SAP ECC), document processing status was segregated into standalone status tables: VBUK (header status) and VBUP (item status). In SAP S/4HANA, this architecture was eliminated to reduce table locks, simplify database design, and accelerate analytical reporting. Header status fields—such as overall processing status (GBSTK), overall delivery status (LFSTK), and overall billing status (FKSTK)—are now embedded directly into the header table VBAK. Similarly, item-level statuses reside directly within table VBAP.

2. Item Level (Table VBAP)

The item tier represents individual products, materials, or services ordered by the customer. Multiple items can exist beneath a single header. Item-level data includes:

• Material Identification: Material number, customer material number (from the Customer-Material Information Record), and material description.
• Item Category: The core control element determining pricing relevance, delivery relevance, billing relevance, and procurement behavior.
• Quantities & Values: Ordered target quantity, base unit of measure, net price, condition values, and line cost.
• Plant & Storage Location: The delivering plant and storage location assigned for shipping fulfillment.

3. Schedule Line Level (Table VBEP)

While the item level defines what and how much the customer wants, schedule lines define when and in what increments delivery will take place. Schedule lines exist only for items requiring delivery or inventory tracking (services and non-delivery items may not require schedule lines). Schedule line data includes:

• Delivery Dates: Requested delivery date, confirmed delivery date, and material availability date.
• Quantities: Requested quantity, confirmed quantity (derived from the Availability Check / ATP), and delivered quantity.
• Schedule Line Category: Controls requirement transfer to Material Requirements Planning (MRP), inventory reservations, and goods movement types (such as movement type 601 for standard goods issue).

---

Customizing Sales Document Types (Transaction VOV8)

Configuration of sales document types is executed in transaction VOV8 (Customizing menu path: SPRO -> SAP Reference IMG -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Header -> Define Sales Document Types). The sales document type is a 4-character alphanumeric identifier (such as OR for Standard Order, QT for Quotation, or CS for Cash Sale) that controls how the SAP system creates, validates, and processes sales transactions.

SPRO Path:
└── Sales and Distribution
    └── Sales
        └── Sales Documents
            └── Sales Document Header
                └── Define Sales Document Types (Transaction VOV8)

1. SD Document Category (Field TVAK-VBTYP)

The SD Document Category is the most critical technical attribute of a sales document type. It informs the underlying ABAP application layer and database views how the transaction behaves. Standard categories include:

• C — Sales Order (standard customer order)
• A — Inquiry (non-binding customer inquiry)
• B — Quotation (binding offer)
• H — Returns (customer returns order)
• K — Credit Memo Request
• L — Debit Memo Request
• E — Scheduling Agreement
• G — Contract

The document category dictates which subsequent business transactions are permissible and how document statistics are posted to the Logistics Information System and S/4HANA embedded analytics.

2. Number Systems and Number Range Assignment

Each sales document type must be assigned number range intervals to govern document identification:

• Internal Number Assignment (NUMKI): When a user or electronic interface saves a document without entering an explicit number, the system automatically assigns the next available sequential number from the internal interval.
• External Number Assignment (NUMKE): Allows users or incoming interfaces (such as legacy POS systems, e-commerce storefronts, or EDI 850 feeds) to supply an alphanumeric or predefined numeric document number upon creation.

Configuring separate intervals ensures strict chronological tracking, satisfies financial auditing mandates, and prevents numbering collisions between manual orders and automated interfaces.

---

General Control Parameters in VOV8

The sales document type configuration contains a comprehensive array of functional switches:

Reference Mandatory

Controls whether a document can be created standalone or if it requires a predecessor document:

• Blank: No reference required; the document can be entered freely.
• A: With reference to an inquiry.
• B: With reference to a quotation.
• C: With reference to a sales order.
• G: With reference to a contract.
• M: With reference to a billing document (used, for example, for credit memo requests created from an invoice).

If a user attempts to create a document type with an active mandatory reference flag in transaction VA01 without providing a valid predecessor document, the system halts execution with a dialog error.

Item Division and Check Division

A sales organization and distribution channel may be paired with several divisions, while each document header carries one division. Two settings decide what happens at item level:

• Item division (indicator): if set, the item takes the division of its material master record; if not set, the header division is copied to all items.
• Check division: decides the reaction when the material's division differs from the header division:
  • Blank: no check.
  • 1: the system issues a warning dialog but lets you continue.
  • 2: the system issues an error and the item cannot be entered.

Credit Management Parameters

In transaction VOV8, two fields connect the document type to credit control:

• Check credit limit: decides whether and how a credit check runs for this document type (blank means no check; in SAP S/4HANA the value for SAP Credit Management is used when credit management is active).
• Credit group: classifies the transaction for the credit check rules; standard groups distinguish sales orders, deliveries, and goods issue.

---

Shipping and Fulfillment Controls

Sales document type customizing defines how the document integrates into the shipping pipeline:

Immediate Delivery

Under standard order processing, an outbound delivery is created asynchronously via transaction VL01N or batch delivery run VL10A after order capture. When immediate delivery is activated in the sales document type:

• Saving the sales order immediately and automatically creates an outbound delivery document in the background.
• If inventory is unconfirmed or master data errors exist, the delivery creation is aborted or placed into an incompletion status.
• This control is the foundational mechanism behind rush orders (document type RO, internal key SO) and cash sales (document type CS, internal key BV).

Default Delivery Block

A delivery block configured at the document type level causes every new order of this type to be placed on delivery hold automatically. Delivery blocks are deployed for:

• Mandatory legal or export compliance screenings.
• Engineering change order reviews.
• High-risk accounts requiring supervisory sign-off prior to picking.

Shipping Condition in the Document Type

Normally, shipping conditions (such as standard ground, overnight express, or customer pickup) are derived from the Sold-to party customer master. Configuring a shipping condition directly in transaction VOV8 overrides the customer master default, guaranteeing that all orders of this document type inherit the designated shipping speed regardless of who places the order.

---

Billing Controls and Invoicing Defaults

The sales document type contains configuration switches that direct subsequent billing creation:

Delivery-Related Billing Type

Specifies the default billing document type used when invoices are generated from outbound deliveries. For standard sales orders, this is typically configured as F2 (Invoice). When an operator runs billing creation (transaction VF01) or executes the collective billing background run (VF04), the system proposes this billing type.

Order-Related Billing Type

Specifies the default billing document type used when invoices are created directly from the sales document without an intermediate delivery. This occurs in service orders, software licenses, third-party drop-ship processing, or credit/debit memo requests. For credit memo requests, the order-related billing type is G2 (Credit Memo); for debit memo requests, it is L2 (Debit Memo). Cash sales also use order-related billing.

Default Billing Block

A default billing block can be assigned to sales document types that require managerial clearance before billing. For example, in Credit Memo Requests (document type CR), setting a default billing block (standard block 08 - Check credit memo) ensures that financial credits cannot be posted to customer accounting without explicit authorization.