Skip to content
SAP Reference

VBRK

transaction S/4HANA status: Active

Billing Document: Header Data

Identity
What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: 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.
Used in the library
KPI definitions
Dashboard patterns

Fields

30 fields · 2 key

30 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. 30 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3T000
Primary keyVBELNBilling DocumentCHAR10
FKARTBilling TypeCHAR4
FKTYPBilling CategoryCHAR1
VBTYPSD Document CategoryCHAR1
WAERKSD Document CurrencyCUKY5TCURC
VKORGSales OrganizationCHAR4TVKO
VTWEGDistribution ChannelCHAR2TVTW
SPARTDivisionCHAR2TSPA
ERNAMName of Person Who Created the ObjectCHAR12
ERDATDate on Which Record Was CreatedDATS8
ERZETEntry TimeTIMS6
BUKRSCompany CodeCHAR4T001
GJAHRFiscal YearNUMC4
FKDATBilling Date for Billing Index and PrintoutDATS8
KUNRGPayerCHAR10KNA1
KUNAGSold-To PartyCHAR10KNA1
KNUMVNumber of the Document ConditionCHAR10
NETWRNet Value in Document CurrencyCURR15,2
MWSBKTax Amount in Document CurrencyCURR13,2
BELNRAccounting Document NumberCHAR10
XBLNRReference Document NumberCHAR16
STCEGVAT Registration NumberCHAR20
INCO1Incoterms (Part 1)CHAR3
INCO2Incoterms (Part 2)CHAR28
LAND1Country KeyCHAR3T005
REGIORegionCHAR3
ZTERMTerms of Payment KeyCHAR4T052
RFBSKStatus for Transfer to AccountingCHAR1
BSTNK_VFCustomer Purchase Order NumberCHAR35

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 VBRK on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

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

-- ============================================================
-- Table  : VBRK Billing Document: Header Data
-- Purpose: Column-selected read of VBRK — 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 "Billing Document",
  h.FKART    AS "Billing Type",
  h.FKTYP    AS "Billing Category",
  h.VBTYP    AS "SD Document Category",
  h.WAERK    AS "SD Document Currency",
  h.VKORG    AS "Sales Organization",
  h.VTWEG    AS "Distribution Channel",
  h.SPART    AS "Division",
  h.ERNAM    AS "Name of Person Who Created the Object",
  h.ERDAT    AS "Date on Which Record Was Created",
  h.ERZET    AS "Entry Time",
  h.BUKRS    AS "Company Code",
  h.GJAHR    AS "Fiscal Year",
  h.FKDAT    AS "Billing Date for Billing Index and Printout",
  h.KUNRG    AS "Payer",
  h.KUNAG    AS "Sold-To Party",
  h.KNUMV    AS "Number of the Document Condition",
  h.NETWR    AS "Net Value in Document Currency",
  h.MWSBK    AS "Tax Amount in Document Currency",
  h.BELNR    AS "Accounting Document Number",
  h.XBLNR    AS "Reference Document Number",
  h.STCEG    AS "VAT Registration Number",
  h.INCO1    AS "Incoterms (Part 1)",
  h.INCO2    AS "Incoterms (Part 2)",
  h.LAND1    AS "Country Key",
  h.REGIO    AS "Region",
  h.ZTERM    AS "Terms of Payment Key",
  h.RFBSK    AS "Status for Transfer to Accounting",
  h.BSTNK_VF AS "Customer Purchase Order Number"
FROM <catalog>.<schema>.vbrk h
WHERE
  h.MANDT = '<MANDT>'
ORDER BY h.VBELN;

Verified August 2026

More query patterns: VF01 VF02 VF03

Released CDS views over this table

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

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • VBRKVBRPheader item · 1:N
    ON vbrk.VBELN = vbrp.VBELN

Transaction Codes That Use This Table

More Sales & Distribution tables