SAP Reference

VBAK

transaction Active

Sales Document: Header Data

Identity

Module: SD · Sales & DistributionType: transparent

What the badges mean

Active

Active and unchanged in S/4HANA.

Deprecated

Still readable today, but no longer SAP's strategic path — plan around it.

Replaced

Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).

Migrating to IBP

Planning scope is moving from APO toward IBP.

Active (StRM) · Replaced (EWM)

Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.

Replaced · Compat View

Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.

Active · Proxy View

Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.

master

Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).

Linked type codes

CLNT — the client key; filter it explicitly and carry it through every join.

NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.

DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.

CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.

LANG — a language key in a text table — one row per language.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Modeling guide

Deliveries & shipments — Did we ship on time, what's still open, how did orders turn into shipments, and can we prove goods actually left?

Used in the library

KPI definitions

K-01OTIF — On Time In Full

K-02Fill Rate

K-07Perfect Order Rate

K-09Lead Time — Order-to-Delivery & Supplier

Dashboard patterns

D-02OTIF / Customer Service

D-03S&OP / Demand Review

D-05Plan vs Actual

Fields

45 fields · 2 key

45 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 45 fields.
Key	Field	Description	Type	Length	References
Primary key	MANDT	Client	CLNT	3	T000
Primary key	VBELN	Sales Document	CHAR	10
	ERDAT	Date on Which Record Was Created	DATS	8
	ERZET	Entry Time	TIMS	6
	ERNAM	Name of Person Who Created the Object	CHAR	12
	ANGDT	Quotation/Inquiry Is Valid From	DATS	8
	BNDDT	Date Until Which Bid/Quotation Is Binding (Valid-To Date)	DATS	8
	AUDAT	Document Date (Date Received/Sent)	DATS	8
	VBTYP	SD Document Category	CHAR	1
	TRVOG	Transaction Group	CHAR	1
	AUART	Sales Document Type	CHAR	4
	AUGRU	Order Reason (Reason for the Business Transaction)	CHAR	3
	GWLDT	Warranty Date	DATS	8
	SUBMI	Collective Number	CHAR	10
	LIFSK	Delivery Block (Document Header)	CHAR	2
	FAKSK	Billing Block in SD Document	CHAR	2
	NETWR	Net Value of the Sales Order in Document Currency	CURR	15,2
	WAERK	SD Document Currency	CUKY	5	TCURC
	VKORG	Sales Organization	CHAR	4	TVKO
	VTWEG	Distribution Channel	CHAR	2	TVTW
	SPART	Division	CHAR	2	TSPA
	VKGRP	Sales Group	CHAR	3
	VKBUR	Sales Office	CHAR	4
	VSBED	Shipping Conditions	CHAR	2
	VDATU	Requested Delivery Date	DATS	8
	VPRGR	Proposed Date Type	CHAR	1
	KALSM	Pricing Procedure in Pricing	CHAR	6
	KNUMV	Number of the Document Condition	CHAR	10
	STWAE	Statistics Currency	CUKY	5	TCURC
	KUNNR	Sold-To Party	CHAR	10	KNA1
	KVGR1	Customer Group 1	CHAR	3
	KVGR2	Customer Group 2	CHAR	3
	KVGR3	Customer Group 3	CHAR	3
	KVGR4	Customer Group 4	CHAR	3
	KVGR5	Customer Group 5	CHAR	3
	KNKLI	Customer's Account Number with Credit Limit Reference	CHAR	10
	KKBER	Credit Control Area	CHAR	4
	CTLPC	Risk Category	CHAR	3
	CMGSTS/4HANA only — this field is not on this table in ECC; the equivalent status lives on VBUK/VBUP there	Overall Status of Credit Checks	CHAR	1
	ABSTKS/4HANA only — this field is not on this table in ECC; the equivalent status lives on VBUK/VBUP there	Rejection Status (All Items)	CHAR	1
	VGBEL	Document Number of the Reference Document	CHAR	10
	OBJNR	Object Number at Header Level	CHAR	22
	BUKRS_VF	Company Code to Be Billed	CHAR	4	T001
	TAXK1	Alternative Tax Classification	CHAR	1
	XBLNR	Reference Document Number	CHAR	16

Fields marked S/4 arrived on this table with S/4HANA’s VBUK/VBUP status-field move. In ECC the equivalent status lives on VBUK/VBUP, not here.

Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading VBAK on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

CatalogSchemaClient (MANDT)

3 parameters not filled: <catalog>, <schema>, <MANDT>

-- ============================================================
-- Table  : VBAK Sales Document: Header Data
-- Purpose: Column-selected read of VBAK — auto-generated from field metadata
-- Grain  : One row per VBELN
-- Notes  : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  h.MANDT AS "Client",
  h.VBELN AS "Sales Document",
  h.ERDAT AS "Date on Which Record Was Created",
  h.ERZET AS "Entry Time",
  h.ERNAM AS "Name of Person Who Created the Object",
  h.ANGDT AS "Quotation/Inquiry Is Valid From",
  h.BNDDT AS "Date Until Which Bid/Quotation Is Binding (Valid-To Date)",
  h.AUDAT AS "Document Date (Date Received/Sent)",
  h.VBTYP AS "SD Document Category",
  h.TRVOG AS "Transaction Group",
  h.AUART AS "Sales Document Type",
  h.AUGRU AS "Order Reason (Reason for the Business Transaction)",
  h.GWLDT AS "Warranty Date",
  h.SUBMI AS "Collective Number",
  h.LIFSK AS "Delivery Block (Document Header)",
  h.FAKSK AS "Billing Block in SD Document",
  h.NETWR AS "Net Value of the Sales Order in Document Currency",
  h.WAERK AS "SD Document Currency",
  h.VKORG AS "Sales Organization",
  h.VTWEG AS "Distribution Channel",
  h.SPART AS "Division",
  h.VKGRP AS "Sales Group",
  h.VKBUR AS "Sales Office",
  h.VSBED AS "Shipping Conditions",
  h.VDATU AS "Requested Delivery Date",
  h.VPRGR AS "Proposed Date Type",
  h.KALSM AS "Pricing Procedure in Pricing",
  h.KNUMV AS "Number of the Document Condition",
  h.STWAE AS "Statistics Currency",
  h.KUNNR AS "Sold-To Party",
  h.KVGR1 AS "Customer Group 1",
  h.KVGR2 AS "Customer Group 2",
  h.KVGR3 AS "Customer Group 3",
  h.KVGR4 AS "Customer Group 4",
  h.KVGR5 AS "Customer Group 5",
  h.KNKLI AS "Customer's Account Number with Credit Limit Reference",
  h.KKBER AS "Credit Control Area",
  h.CTLPC AS "Risk Category",
  h.CMGST AS "Overall Status of Credit Checks",
  h.ABSTK AS "Rejection Status (All Items)"
  -- … plus 5 more columns — full list in the Fields section above
FROM <catalog>.<schema>.vbak h
WHERE
  h.MANDT = '<MANDT>'
ORDER BY h.VBELN;

Verified August 2026

More query patterns: VA01 VA02 VA03

Released CDS views over this table

Released SAP standard VDM views that read over VBAK. Prefer these over classic-table reads on S/4HANA where available.

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

VBAKVBAPheader item · 1:N
ON vbak.VBELN = vbap.VBELN
VBAKKNA1foreign key · N:1
ON vbak.KUNNR = kna1.KUNNR
LIPSVBAKforeign key · N:1
ON lips.VGBEL = vbak.VBELN
VBAKTVKOforeign key · N:1
ON vbak.VKORG = tvko.VKORG
VBAKVBPAforeign key · 1:N
ON vbak.VBELN = vbpa.VBELN
VBAKVBKDforeign key · 1:N
ON vbak.VBELN = vbkd.VBELN

Transaction Codes That Use This Table

R read · W write · R/W read + write