This guide lists the most important SAP SD tables, grouped by functional area — sales documents, deliveries, billing, customer master data, pricing, and document flow. For each table you will find what it stores and the key fields you will query most often with SE16N or SE11.
Why SAP SD Tables Matter
SAP SD follows the classic order-to-cash process: a customer places an order, the warehouse delivers the goods, and finance bills the customer. Each step writes data into specific tables:
- Sales documents → VBAK (header), VBAP (item)
- Deliveries → LIKP (header), LIPS (item)
- Billing documents → VBRK (header), VBRP (item)
The header/item split is a pattern you will see everywhere in SAP. The header table holds document-level data (customer, dates, totals) while the item table holds line-level data (material, quantity, plant). They are joined on the document number field VBELN.
Sales Document Tables
Sales documents include inquiries, quotations, sales orders, and contracts. These are the core SAP SD tables for everything created with transactions like VA01, VA02, and VA03.
| Table | Description |
|---|---|
| VBAK | Sales document header data (order number, customer, sales area, dates, net value) |
| VBAP | Sales document item data (material, quantity, plant, storage location, item net value) |
| VBEP | Sales document schedule line data (confirmed quantities and delivery dates per item) |
| VBKD | Sales document business data (incoterms, payment terms, account assignment per item) |
| VBPA | Sales document partner data (sold-to, ship-to, bill-to, payer partner functions) |
| VBUK | Sales document header status (overall delivery status, billing status, credit status) |
| VBUP | Sales document item status (delivery and billing status per line item) |
Key fields in VBAK: VBELN (document number), AUART (document type, e.g. OR for standard order), VKORG (sales organization), VTWEG (distribution channel), SPART (division), KUNNR (sold-to party), ERDAT (creation date), NETWR (net value), WAERK (currency).
Key fields in VBAP: VBELN, POSNR (item number), MATNR (material), KWMENG (order quantity), NETWR (item net value), WERKS (plant), LGORT (storage location), ABGRU (reason for rejection).
Tip: VBEP is where you find schedule line details — the confirmed quantity (BMENG) and confirmed delivery date. If a user asks “when is my order confirmed for delivery?”, VBEP has the answer.
Delivery Tables
Once a sales order is ready to ship, a delivery document is created (VL01N). Delivery tables track picking, packing, and goods issue.
| Table | Description |
|---|---|
| LIKP | Delivery header data (delivery number, delivery type, shipping point, goods issue date) |
| LIPS | Delivery item data (material, delivery quantity, batch, plant, storage location) |
| VTTK | Shipment header data (shipment number, transportation planning point, route) |
| VTTP | Shipment item data (deliveries assigned to a shipment, stages) |
| VBUK / VBUP | Delivery header and item status tables (shared with sales documents) |
Key fields in LIKP: VBELN (delivery number), LFART (delivery type, e.g. LF for outbound delivery), VSTEL (shipping point), WADAT (goods issue date), KUNNR (ship-to party).
Key fields in LIPS: VBELN, POSNR, MATNR, LFIMG (actual delivery quantity), LGORT, WERKS, VGBEL/VGPOS (reference to the preceding sales document and item).
Billing Tables
Billing documents (invoices, credit memos, debit memos) are created with VF01 and stored in VBRK/VBRP. These tables are also heavily used by FI consultants, since billing triggers accounting entries in BKPF/BSEG.
| Table | Description |
|---|---|
| VBRK | Billing document header (billing type, billing date, payer, net value) |
| VBRP | Billing document item (material, billed quantity, item net value, reference to order/delivery) |
| VBUK / VBUP | Billing header and item status (shared status tables) |
Key fields in VBRK: VBELN (billing document number), FKART (billing type, e.g. F2 for invoice), FKDAT (billing date), KUNAG (sold-to), KUNRG (payer), NETWR, WAERK.
Key fields in VBRP: VBELN, POSNR, FKIMG (billed quantity), NETWR, MATNR, VGBEL/VGPOS (preceding document), AUBEL/AUPOS (original sales order and item).
If you are preparing for interviews, our list of SAP FICO interview questions covers the finance side of this billing integration in depth.
Customer Master Tables
Customer master data is organized in three levels — general data, company code data, and sales area data — which is why you need three tables to get the full picture.
| Table | Description |
|---|---|
| KNA1 | Customer master general data (name, address, country, customer account group) |
| KNB1 | Customer master company code data (reconciliation account, payment terms) |
| KNVV | Customer master sales area data (sales office, sales group, customer group, shipping conditions) |
| KNVP | Customer master partner functions (ship-to, bill-to, payer assignments) |
| KNVI | Customer master tax indicators (tax classifications per country) |
Key fields in KNA1: KUNNR (customer number), NAME1, ORT01 (city), PSTLZ (postal code), LAND1 (country), REGIO (region), KTOKD (account group).
Key fields in KNVV: KUNNR, VKORG, VTWEG, SPART, KDGRP (customer group), BZIRK (sales district), VKGRP (sales group), VKBUR (sales office).
Note for S/4HANA: customer master maintenance moved to the Business Partner (transaction BP) with Customer-Vendor Integration (CVI). The underlying tables KNA1, KNB1, and KNVV still exist and are still the tables you query.
Pricing Condition Tables
Pricing in SAP SD uses the condition technique, and condition data lives in these tables:
| Table | Description |
|---|---|
| KONV | Conditions from the document (actual prices, discounts, taxes on a sales document) |
| KONP | Condition items (condition record details: amount, validity dates) |
| KONH | Condition headers (condition record headers for master condition data) |
Key fields in KONV: KNUMV (document condition number), KPOSN (condition item), KSCHL (condition type, e.g. PR00 for price), KBETR (rate), KWERT (condition value).
KONV is the table you query when someone asks “what price and discounts were applied on this order?” — join it to VBAK on KNUMV.
Document Flow Table
| Table | Description |
|---|---|
| VBFA | Sales document flow (links every preceding and subsequent document: order → delivery → invoice) |
Key fields: VBELV/POSNV (preceding document and item), VBELN/POSNN (subsequent document and item), VBTYP_V/VBTYP_N (document categories). VBFA is how the document flow view in VA03 is built — one query here shows you the entire order-to-cash chain.
Organizational Structure Tables
| Table | Description |
|---|---|
| TVKO | Sales organizations |
| TVTW | Distribution channels |
| TSPA | Divisions |
| TVTA | Sales areas (combination of sales org, distribution channel, division) |
| T001W | Plants |
| TVST | Shipping points |
How to Explore These Tables
- SE16N — display table contents; filter by VBELN, KUNNR, or ERDAT. Always set a maximum number of hits to avoid performance issues.
- SE11 — view a table’s structure, field names, data elements, and technical settings.
- ST05 — SQL trace, useful to see exactly which tables a transaction reads.
Related reading: if you work with procurement data too, our complete SAP MM tables list follows the same header/item pattern for purchase orders and material documents.
Frequently Asked Questions
Q1. What is the main header table for sales orders in SAP SD?
VBAK is the sales document header table. It stores the document number (VBELN), document type (AUART), customer (KUNNR), sales area (VKORG/VTWEG/SPART), and net value (NETWR) for inquiries, quotations, orders, and contracts.
Q2. What is the difference between VBAK and VBAP?
VBAK holds header-level data (one row per sales document), while VBAP holds item-level data (one row per line item). They are linked by the document number field VBELN. A single VBAK row typically has multiple VBAP rows.
Q3. Which table stores delivery data in SAP SD?
LIKP is the delivery header table and LIPS is the delivery item table, joined on the delivery number (VBELN). LIKP holds the delivery type (LFART), shipping point (VSTEL), and goods issue date (WADAT); LIPS holds material, quantity (LFIMG), and batch details.
Q4. Which SAP SD tables store billing/invoice data?
VBRK (billing header) and VBRP (billing item). VBRK contains the billing type (FKART), billing date (FKDAT), and payer (KUNRG); VBRP contains the billed quantity (FKIMG) and references back to the delivery and sales order.
Q5. How do I find the full document flow from order to invoice?
Use table VBFA. Query it with the sales order number in VBELV to see all subsequent documents (deliveries in VBELN with their item numbers in POSNN), then follow the chain from delivery to billing document.
Q6. Which tables hold customer master data in SAP?
KNA1 (general data), KNB1 (company code data), and KNVV (sales area data), all keyed by the customer number KUNNR. In S/4HANA, customers are maintained via Business Partner (BP), but these tables remain the storage layer.
Conclusion
These are the SAP SD tables you will use in most of your daily work: VBAK/VBAP for orders, LIKP/LIPS for deliveries, VBRK/VBRP for billing, KNA1/KNB1/KNVV for customers, KONV for pricing, and VBFA for document flow. Learn the key fields listed above, practice joining them in SE16N, and you will be able to answer almost any “where is this data stored?” question in an SD project or interview.