SAP SD Tables List: Complete Database Reference
For SAP S/4HANA & ECC · 61+ tables across 10 functional areas · Updated for 2026
The complete SAP SD tables reference — every important database table a Sales & Distribution consultant needs to know, from sales document headers (VBAK) and items (VBAP) all the way through delivery, billing, pricing condition records, and credit master data.
Each section flags what changed in S/4HANA — VBUK/VBUP merged into VBAK/VBAP, KONV replaced by PRCD_ELEMENTS, classic credit (KNKK) replaced by FSCM Credit (UKMBP_CMS_SGM), and the Business Partner framework (BUT000) leading customer creation. Bookmark this page — it's the only SD tables reference you'll need.
Quick Jump
Sales Document Tables
Header, item, partner, and document-flow tables for sales orders, quotations, contracts, and scheduling agreements. The backbone of every SD process.
| Table | Description & Key Fields |
|---|---|
| VBAK | Sales Document — Header Data (one row per sales order/quotation/contract)Key fields: VBELN (Sales Doc), AUART (Doc Type), VKORG, VTWEG, SPART, KUNNR (Sold-to) |
| VBAP | Sales Document — Item DataKey fields: VBELN, POSNR (Item), MATNR, KWMENG (Order Qty), NETWR (Net Value), WERKS, LGORT |
| VBKD | Sales Document — Business Data (payment terms, Inco-terms, currency at item level)Key fields: VBELN, POSNR, ZTERM, INCO1, INCO2, BSTKD (Cust PO), KURSK |
| VBPA | Sales Document — Partner Functions (sold-to, ship-to, bill-to, payer)Key fields: VBELN, POSNR, PARVW (Partner Fn), KUNNR, PERNR |
| VBEP | Sales Document — Schedule Lines (delivery dates and confirmed quantities)Key fields: VBELN, POSNR, ETENR, EDATU, WMENG, BMENG |
| VBKD (Conditions linkage via KONV/PRCD_ELEMENTS) | Pricing record references — see Pricing Tables section below |
| VBFA | Sales Document Flow — links predecessor and successor documents (Order → Delivery → Invoice). Critical for status, copy control, and reporting.Key fields: VBELV (Predecessor), VBELN (Successor), VBTYP_V, VBTYP_N, RFMNG |
| VBUK | Sales Document — Header Status (delivery status, billing status, credit status)Key fields: VBELN, GBSTK, LFSTK, FKSTK, CMGST⚠ In S/4HANA, VBUK is merged into VBAK — status fields now live directly on VBAK. Compatibility view exists for legacy code, but new development should read VBAK. |
| VBUP | Sales Document — Item StatusKey fields: VBELN, POSNR, GBSTA, LFSTA, FKSTA⚠ In S/4HANA, VBUP is merged into VBAP — status fields now live on VBAP. |
| VEDA | Contract Data (validity period, cancellation rules) — used for VA41 contractsKey fields: VBELN, VPOSN, VBEGDAT, VENDDAT |
Delivery Tables
Outbound delivery documents covering picking, packing, goods issue, and shipping logistics.
| Table | Description & Key Fields |
|---|---|
| LIKP | Delivery Document — Header (one row per outbound/inbound delivery)Key fields: VBELN (Delivery), LFART, VSTEL (Shipping Point), KUNNR, WADAT_IST (GI Date) |
| LIPS | Delivery Document — Item (links back to sales order via VGBEL/VGPOS)Key fields: VBELN, POSNR, MATNR, LFIMG (Delivery Qty), VGBEL (Ref Order), VGPOS, WERKS, LGORT |
| VTTK | Shipment Document — Header (used when LE-TRA / Transport Mgmt is active)Key fields: TKNUM (Shipment), SHTYP, ROUTE, VSART |
| VTTP | Shipment Document — Item (links shipments to deliveries)Key fields: TKNUM, TPNUM, VBELN (Delivery) |
| VEKP | Handling Unit — Header (packing data)Key fields: VENUM, VHILM (Packing Material), BRGEW, NTGEW |
| VEPO | Handling Unit — Item (contents inside an HU)Key fields: VENUM, VEPOS, VBELN, POSNR, MATNR, VEMNG |
Billing Tables
Billing document tables — invoices, credit memos, debit memos, and pro-forma billing. The bridge from SD into FI accounting.
| Table | Description & Key Fields |
|---|---|
| VBRK | Billing Document — Header (one row per invoice/credit memo/debit memo)Key fields: VBELN (Billing Doc), FKART, FKDAT, KUNAG (Payer), NETWR, WAERK, BUKRS |
| VBRP | Billing Document — ItemKey fields: VBELN, POSNR, MATNR, FKIMG (Billed Qty), NETWR, AUBEL (Ref Order), VGBEL (Ref Delivery) |
| VBRL | Billing Plan / Rebate — Settlement Document (used for rebate agreements and milestone billing) |
Customer Master Tables
Customer master in ECC. In S/4HANA all customers must be created through the Business Partner (BP) framework, which writes through to these legacy tables for compatibility.
| Table | Description & Key Fields |
|---|---|
| KNA1 | Customer Master — General Data (name, address, country, search terms)Key fields: KUNNR, NAME1, LAND1, ORT01, PSTLZ, STRAS |
| KNB1 | Customer Master — Company Code Data (recon account, payment terms, dunning)Key fields: KUNNR, BUKRS, AKONT (Recon Acct), ZTERM, MAHNA |
| KNVV | Customer Master — Sales Area Data (price group, customer group, delivery priority, payment terms at sales-area level)Key fields: KUNNR, VKORG, VTWEG, SPART, KDGRP, KONDA, ZTERM |
| KNVP | Customer Master — Partner Functions (default sold-to / ship-to / bill-to / payer per sales area)Key fields: KUNNR, VKORG, VTWEG, SPART, PARVW, KUNN2 |
| KNVK | Customer Master — Contact PersonsKey fields: PARNR, KUNNR, NAME1 |
| KNVI | Customer Master — Tax IndicatorsKey fields: KUNNR, ALAND, TATYP, TAXKD |
| BUT000 | Business Partner — General Data (master table for the BP framework)Key fields: PARTNER, PARTNER_GUID, TYPE, BU_GROUP⚠ In S/4HANA, BUT000 is the leading customer-creation table. KNA1/KNB1/KNVV are populated via CVI synchronisation when BP is saved with role FLCU00/FLCU01. |
Material Master Tables (SD Views)
Material master tables relevant to Sales & Distribution — basic data, plant data, storage, and sales-org-specific data.
| Table | Description & Key Fields |
|---|---|
| MARA | Material Master — General Data (material number, type, group, base UoM)Key fields: MATNR, MTART, MATKL, MEINS, BRGEW, NTGEW |
| MARC | Material Master — Plant Data (MRP type, availability check, loading group)Key fields: MATNR, WERKS, DISMM, MTVFP, LADGR, TRAGR |
| MARD | Material Master — Storage Location Data (stock per storage location)Key fields: MATNR, WERKS, LGORT, LABST, INSME |
| MVKE | Material Master — Sales Data (sales org / distribution channel specific — item category group, account assignment group, tax classification)Key fields: MATNR, VKORG, VTWEG, MVGR1, KONDM, KTGRM |
| MAKT | Material Master — Material Descriptions (per language)Key fields: MATNR, SPRAS, MAKTX |
Pricing & Condition Technique Tables
The condition technique storage layer — condition records, condition types, access sequences, and the document-level condition records that get copied onto orders and invoices.
| Table | Description & Key Fields |
|---|---|
| KONV | Conditions — Document-level pricing records (one row per condition line on a sales order, delivery, or billing document)Key fields: KNUMV (Doc Cond #), KPOSN, KSCHL (Cond Type), KBETR, KWERT⚠ In S/4HANA, KONV is replaced by PRCD_ELEMENTS. New custom code must read PRCD_ELEMENTS; KONV becomes a compatibility view in some releases. |
| PRCD_ELEMENTS | S/4HANA replacement for KONV — document-level condition records under the new pricing data model.Key fields: KNUMV, KPOSN, KSCHL, KBETR, KWERT |
| KONH | Conditions — Master Data Header (condition record header — created via VK11)Key fields: KNUMH, KSCHL, KAPPL |
| KONP | Conditions — Master Data Item (rate, scale base, validity)Key fields: KNUMH, KOPOS, KBETR, KONWA, KMEIN |
| A001 – A999 | Condition Tables — one transparent table per access sequence key combination (e.g. A005 = Customer/Material). Stored as KNUMH pointers into KONH/KONP.Key fields: KAPPL, KSCHL, plus the key fields of that access (KUNNR, MATNR, etc.) |
| T683 | Pricing Procedures — Header (definition of each pricing procedure, e.g. RVAA01)Key fields: KVEWE, KAPPL, KALSM |
| T683S | Pricing Procedures — Steps (the lines you see in V/08 — condition types, from/to, sub-total, requirement, alt calc)Key fields: KVEWE, KAPPL, KALSM, STUNR, ZAEHK, KSCHL, KFKIV |
| T685 | Condition Types (master configuration of each KSCHL — calculation type, plus/minus, scales)Key fields: KAPPL, KSCHL, KRECH, KOAID |
| T682 | Access Sequences — HeaderKey fields: KVEWE, KOZGF |
| T682I | Access Sequences — Accesses (the order in which condition tables A001–A999 are searched)Key fields: KVEWE, KOZGF, KOLNR, KOTABNR |
Credit Management Tables
Credit master and exposure tables. Major architectural change in S/4HANA: classic credit management (FI-AR-CR with KNKK / FD32) is replaced by SAP Credit Management (FIN-FSCM-CR) using business partner credit segments.
| Table | Description & Key Fields |
|---|---|
| KNKK | Customer Master — Credit Control Area Data (credit limit, risk category, exposure)Key fields: KUNNR, KKBER, KLIMK, CTLPC, SBGRP⚠ Classic credit management table. In S/4HANA, FSCM Credit is mandatory and KNKK is read-only (kept for compatibility). Use UKMBP_CMS_SGM for the new credit master. |
| UKMBP_CMS_SGM | FSCM Credit Management — Credit Segment data per BP (credit limit, risk class, validity). The S/4HANA replacement for KNKK.Key fields: PARTNER, CREDIT_SGMT, CREDIT_LIMIT, RISK_CLASS, VALID_DATE |
| UKMBP_CMS | FSCM Credit — BP-level credit profile (rules, scoring, blocking reasons)Key fields: PARTNER, RISK_CLASS, CHECK_RULE, BLOCKED |
| S066 / S067 | LIS Info Structures — Open orders and open deliveries used for classic credit exposure (FD32). |
Output Determination Tables
Tables behind output determination — message records, condition records for output, and program/form assignments. Note: for new output, S/4HANA introduces BRF+ based output management which uses different tables (FNDOM_*).
| Table | Description & Key Fields |
|---|---|
| NAST | Message / Output Status Records (one row per output triggered on a document)Key fields: KAPPL, OBJKY, KSCHL, NACHA, VSTAT, VSZTP |
| TNAPR | Output Programs and Forms (assigns SAPscript / Smartform / driver program per condition type)Key fields: KSCHL, NACHA, PGNAM, FONAM |
Sales Org Structure & Configuration Tables
Enterprise structure for SD — sales organisations, distribution channels, divisions, and their assignments to company codes and plants.
| Table | Description & Key Fields |
|---|---|
| TVKO | Sales OrganisationsKey fields: VKORG, BUKRS, VKOLV, ADRNR |
| TVTW | Distribution ChannelsKey fields: VTWEG, BEZEI |
| TSPA | DivisionsKey fields: SPART, VTEXT |
| TVTA | Sales Area Assignments — VKORG/VTWEG/SPART → company code and credit control area |
| TVKBZ | Sales Office Master |
| TVKGR | Sales Group Master |
| TVAK | Sales Document Types (OR, RE, CR, DR — header config from VOV8)Key fields: AUART, VBTYP, NUMKI, NUMKE, KALSM |
| TVAP | Sales Document Item Categories (TAN, TANN, REN — config from VOV7)Key fields: PSTYV, FKREL, PRSFD, VWPOS |
| TVEP | Sales Document Schedule Line Categories (CP, CN, CV — config from VOV6)Key fields: ETTYP, BWART, PRREG, MTVFP |
| TVLK | Delivery Document Types (LF, NL, RL — config from 0VLK)Key fields: LFART, VBTYP, NUMKI, NUMKE |
| TVFK | Billing Document Types (F2, G2, L2, RE — config from VOFA)Key fields: FKART, VBTYP, NUMKI, KALSM |
FI Integration & Account Determination Tables
Where SD revenue postings get translated into G/L accounts. Account determination tables linked to VKOA configuration.
| Table | Description & Key Fields |
|---|---|
| C001 – C005 | Account Determination Condition Tables (e.g. C001 = AppGrp/Cust AcctAssGrp/Mat AcctAssGrp)Key fields: KAPPL, KOSTL, KTOPL, KVSL1 |
| KOMV / KOMP / KOMK | Pricing communication structures (used at runtime — not transparent tables, but referenced in user-exits and routines) |
| BKPF / BSEG | FI accounting documents created by SD billing release-to-accounting (one BKPF + multiple BSEG per invoice posting)Key fields: BUKRS, BELNR, GJAHR, AWKEY (= VBELN of invoice) |
Frequently Asked Questions
What is the difference between VBAK, VBAP, and VBKD?
VBAK stores the sales document header (one row per order). VBAP stores the items (one row per line item). VBKD stores business data such as payment terms, Incoterms, and customer PO references — it can exist at both header and item level, with header rows having POSNR = 000000.
What replaced KONV in S/4HANA?
KONV (document conditions) is replaced by PRCD_ELEMENTS in S/4HANA. The new table holds the same conceptual data (KNUMV, KPOSN, KSCHL, KBETR, KWERT) under the simplified pricing data model. KONV remains as a compatibility view in some releases, but new ABAP development should read PRCD_ELEMENTS directly.
Are VBUK and VBUP still used in S/4HANA?
No. VBUK and VBUP are merged into VBAK and VBAP respectively in S/4HANA. The status fields (GBSTK, LFSTK, FKSTK, etc.) now live directly on the header/item table. SAP provides compatibility views for old code, but new development should read VBAK/VBAP for status.
What is the difference between KNVV and KNVP?
KNVV stores the customer master sales-area data — sales-org-specific attributes like price group, customer pricing procedure, delivery priority, and incoterms defaults. KNVP stores the partner functions (which sold-to / ship-to / bill-to / payer is defaulted on orders for that customer in that sales area).
Where does pricing actually live — KONV, KONP, or A001-A999?
The condition records you create in VK11 are stored in KONH (header) and KONP (item). The "A" tables (A001 to A999) are key-combination tables that point to KNUMH in KONH/KONP. Once a condition is found and copied onto a sales order or invoice, the document-level result is written to KONV (or PRCD_ELEMENTS in S/4HANA) keyed by KNUMV.
How do I trace a sales order from creation to invoice using these tables?
Start with VBAK (order header), join VBAP (items), then use VBFA (document flow) where VBELV = your order to find successor deliveries (LIKP/LIPS) and invoices (VBRK/VBRP). VBFA is the master-detail navigator across the whole O2C cycle. VBUK/VBUP (or VBAK/VBAP in S/4) give you the current status at any point.
Which table stores sales order header data in SAP SD?
VBAK is the table that stores sales order header data in SAP SD. It contains one row per sales document (order, quotation, contract, scheduling agreement) with key fields VBELN (Sales Document Number), AUART (Document Type), VKORG (Sales Organisation), VTWEG (Distribution Channel), SPART (Division), and KUNNR (Sold-to Party). VBAK is the same in both ECC and S/4HANA, with status fields (GBSTK, LFSTK, FKSTK) added to it in S/4HANA via the merge of VBUK.
What table stores billing document data in SAP SD?
Billing documents are stored across two tables: VBRK (header — one row per invoice / credit memo / debit memo) and VBRP (items). VBRK contains VBELN (Billing Document), FKART (Billing Type), FKDAT (Billing Date), KUNAG (Payer), NETWR (Net Value), and BUKRS (Company Code). VBRP contains the line items including FKIMG (Billed Quantity), MATNR (Material), and reference fields AUBEL (back to sales order) and VGBEL (back to delivery).
What is the difference between KONV, KONH, and KONP?
KONH and KONP store master pricing condition records — KONH is the header (created via VK11) and KONP holds the items (rate, validity period, scale base). KONV stores document-level conditions — when a sales order or invoice is priced, the resolved condition values are written to KONV keyed by KNUMV (the document condition number). In SAP S/4HANA, KONV is replaced by PRCD_ELEMENTS, but KONH and KONP remain unchanged.
How do A001-A999 tables work in SAP SD pricing?
A001 through A999 are condition tables — one transparent table per access in the access sequence. For example, A005 might store pricing condition records by Customer / Material combination. Each row in an A-table contains the key fields (e.g. VKORG, KUNNR, MATNR) plus a pointer KNUMH that links to the master condition record in KONH and KONP. The access sequence (configured in V/07) defines the order in which the system searches A-tables until it finds a match.
What replaced KNKK in S/4HANA for credit management?
In SAP S/4HANA, the classic credit master table KNKK (linked to FD32 / classic credit management) is replaced by FSCM Credit Management tables. The primary table is UKMBP_CMS_SGM, which stores credit segment data per Business Partner (credit limit, risk class, validity dates, credit exposure). KNKK still exists in S/4HANA in compatibility mode but is read-only — all new credit master data must be maintained via FSCM (UKM_BP).
How does VBFA help trace document flow in SAP SD?
VBFA is the document flow table — it links predecessor and successor documents across the Order-to-Cash cycle. Key fields are VBELV (predecessor document), POSNV (predecessor item), VBELN (successor document), POSNN (successor item), VBTYP_V/VBTYP_N (document categories), and RFMNG (referenced quantity). To trace a sales order forward: query VBFA where VBELV = order number to find deliveries; query again where VBELV = delivery number to find invoices. This is the standard navigation pattern for all SD reporting and status checks.
Beyond tables — master SAP SD end-to-end.
Tables are where the data lives. Inside The SD Vault you'll find the configuration logic that drives those tables, the FI integration that connects them, and 230+ interview questions that test whether you actually understand them.
Get Lifetime Access →Also see our SAP SD T-Codes Reference, Pricing Procedure Guide, and Interview Questions.