VBRK
transaction S/4HANA status: ActiveBilling Document: Header Data
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.
Fields
30 fields · 2 key
30 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | T000 |
| Primary key | VBELN | Billing Document | CHAR | 10 | |
| FKART | Billing Type | CHAR | 4 | ||
| FKTYP | Billing Category | CHAR | 1 | ||
| VBTYP | SD Document Category | CHAR | 1 | ||
| WAERK | SD Document Currency | CUKY | 5 | TCURC | |
| VKORG | Sales Organization | CHAR | 4 | TVKO | |
| VTWEG | Distribution Channel | CHAR | 2 | TVTW | |
| SPART | Division | CHAR | 2 | TSPA | |
| ERNAM | Name of Person Who Created the Object | CHAR | 12 | ||
| ERDAT | Date on Which Record Was Created | DATS | 8 | ||
| ERZET | Entry Time | TIMS | 6 | ||
| BUKRS | Company Code | CHAR | 4 | T001 | |
| GJAHR | Fiscal Year | NUMC | 4 | ||
| FKDAT | Billing Date for Billing Index and Printout | DATS | 8 | ||
| KUNRG | Payer | CHAR | 10 | KNA1 | |
| KUNAG | Sold-To Party | CHAR | 10 | KNA1 | |
| KNUMV | Number of the Document Condition | CHAR | 10 | ||
| NETWR | Net Value in Document Currency | CURR | 15,2 | ||
| MWSBK | Tax Amount in Document Currency | CURR | 13,2 | ||
| BELNR | Accounting Document Number | CHAR | 10 | ||
| XBLNR | Reference Document Number | CHAR | 16 | ||
| STCEG | VAT Registration Number | CHAR | 20 | ||
| INCO1 | Incoterms (Part 1) | CHAR | 3 | ||
| INCO2 | Incoterms (Part 2) | CHAR | 28 | ||
| LAND1 | Country Key | CHAR | 3 | T005 | |
| REGIO | Region | CHAR | 3 | ||
| ZTERM | Terms of Payment Key | CHAR | 4 | T052 | |
| RFBSK | Status for Transfer to Accounting | CHAR | 1 | ||
| BSTNK_VF | Customer Purchase Order Number | CHAR | 35 |
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.
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
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
ON vbrk.VBELN = vbrp.VBELN
Transaction Codes That Use This Table
R read · W write · R/W read + write