Sales Documents
SD / O2Cintermediate

SD Sales Documents Part 2: Sales Document Type Configuration (VOV8)

Key takeaway

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.

Explanation

📌 KEY POINTS
✅ VOV8 (table TVAK) holds the header-level control of a sales document: category, numbering, checks, follow-on document types, blocks, dates and procedures.

✅ Delivery type and billing type in VOV8 define the follow-on documents (e.g. OR → LF delivery → F2 invoice).

✅ Document pricing procedure key (with customer pricing procedure and sales area) determines the pricing procedure.

✅ Always copy a standard type (OR → ZOR) — copying also copies dependent settings like copy control and item category assignments when using the copy function.

⚠️ Changing settings on a document type in use (e.g. number range, category) affects every open and future document of that type.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 1 showed the document categories. Now we configure a document type.

━━━━━━━━━━━━━━━━━━━━
▶ 1. NUMBER SYSTEMS AND CATEGORY

  • Document category (A, B, C, G, H, K…).
  • Internal and external number range (VN01).
  • Item number increment (10) and sub-item increment.

━━━━━━━━━━━━━━━━━━━━
▶ 2. GENERAL CONTROL

  • Reference mandatory (e.g. order must reference a quotation).
  • Check division: dialog/error if item division differs from header.
  • Read info record, check customer PO number, enter PO number.
  • Credit group (credit check), screen sequence group, transaction group.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SHIPPING AND BILLING

  • Delivery type (LF, LR for returns) and default delivery block.
  • Shipping conditions override (otherwise from customer).
  • Delivery-related and order-related billing type (F2, G2, RE), default billing block.
  • Immediate delivery (rush order), cash sale behavior.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DATES AND CONTRACTS

  • Lead time in days, proposed delivery date, propose PO date.
  • Contract profile, validity periods, billing plan type for contracts.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PROCEDURES AND RESTRICTIONS

  • Incompletion procedure (assigned via VUA2).
  • Document pricing procedure key for pricing determination (OVKK).
  • Assignment to sales areas (OVAZ) — restrict which sales areas may use the type.
  • Output determination procedure/output type via output management settings.

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

  1. Copy OR to ZOR in VOV8.
  2. Set number range, reference and division checks.
  3. Set delivery type, billing type, blocks and date proposals.
  4. Assign incompletion procedure and document pricing procedure key.
  5. Restrict to sales areas, maintain copy control and item category assignment (Copy Control / Item Category topics).

✅ CHECKPOINT: an order of ZOR gets its number from the correct range, creates an LF delivery and an F2 invoice.

Code example

ABAP Code
===== STEP 1: sales document type (SPRO > Sales and Distribution > Sales > Sales Documents >             Sales Document Header > Define Sales Document Types)  (VOV8)  table TVAKField                       | ZOR exampleDocument category           | C (order)No. range int./ext.         | 01 / 02   (VN01)Item no. increment          | 10Reference mandatory         | –  (or B = with reference to quotation)Check division              | 1 = dialogCredit group                | 01Delivery type / block       | LF / –Billing type deliv.-related | F2      Order-related billing F2Billing block               | –Lead time in days           | 2Doc. pricing procedure      | A ===== STEP 2: related assignments =====Number ranges for sales documents                           VN01Assign incompletion procedure to sales document types      VUA2Pricing procedure determination (sales area + doc. + cust.) OVKKAssign sales area to sales document types                  OVAZItem category assignment                                     VOV4 (Item Category topic)Copy control order → order / quotation → order             VTAA (Copy Control topic) ===== STEP 3: test =====VA01 ZOR → save → VL01N (LF) → VF01 (F2) → check document flow

Real project scenario

A client created ZOR by simply creating a new entry in VOV8 instead of using the copy function. The document type worked for order entry, but orders created with reference to quotations failed ("copying not possible"), and items had no item category. The copy function would have copied copy control and item category assignments from OR. The team deleted ZOR, recreated it with the copy function, then adjusted only the differing fields. They also added a VOV8 change checklist: number range, VUA2, OVKK, OVAZ, VOV4, VTAA and output.

Common mistakes

  • Creating document types from scratch instead of copying a standard type.
  • Forgetting VOV4 item category assignment or VTAA copy control for the new type.
  • Changing the number range of a type that is in use without planning.
  • Missing document pricing procedure key, so the wrong pricing procedure is found.
  • Setting default billing blocks without a release process.

Best practices

  • Always copy a standard document type with the copy function.
  • Maintain a checklist of dependent settings per document type.
  • Restrict custom types to the sales areas that need them (OVAZ).
  • Use default blocks only with a clear release owner.
  • Document why each custom type exists.

Interview angle

Questions: "Which settings do you maintain in VOV8?", "How is the delivery and billing type of an order determined?", "What must be done after creating a new document type?"
Strong answer: category, number ranges, reference and division checks, credit group, delivery type, billing type, blocks, dates, contract data; incompletion via VUA2, pricing via document pricing procedure key and OVKK, sales area restriction OVAZ, plus VOV4 item category assignment and VTAA copy control. Copy from a standard type.

Practice this lesson

Quick check

1. Which transaction defines sales document types?

2. Where is the default delivery type (e.g. LF) of a sales order determined?

3. A new document type ZOR was created as a new entry in VOV8 instead of with the copy function. Orders with reference to quotations fail and items get no item category. Why?

Interview questions

1. 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?

Answer it in your own words first, then compare.

2. 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?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics