Skip to content
SAP Reference

VBAP

transaction S/4HANA status: Active

Sales Document: Item 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.

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

Fields

52 fields · 3 key

The join key is all 3 key fields together — matching on any single one fans out. See composite keys in the quirks guide.

52 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. 52 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3T000
Primary keyVBELNSales DocumentCHAR10VBAK
Primary keyPOSNRSales Document ItemNUMC6
MATNRMaterial NumberCHAR18 / 40MARA
MATWAMaterial EnteredCHAR18
PMATNPricing Reference MaterialCHAR18
CHARGBatch NumberCHAR10
MATKLMaterial GroupCHAR9T023
ARKTXShort Text for Sales Order ItemCHAR40
PSTYVSales Document Item CategoryCHAR4
POSARItem TypeCHAR1
LFRELItem Is Relevant for DeliveryCHAR1
FKRELRelevant for BillingCHAR1
UEPOSHigher-Level Item in BOM StructuresNUMC6
GRPOSAlternative for ItemNUMC6
ABGRUReason for Rejection of Quotations and Sales OrdersCHAR2
NETWRNet Value of the Order Item in Document CurrencyCURR15,2
WAERKSD Document CurrencyCUKY5TCURC
NETPRNet PriceCURR11,2
KPEINCondition Price UnitDEC5
KMEINCondition UnitUNIT3T006
KWMENGCumulative Order Quantity in Sales UnitsQUAN15,3
VRKMESales UnitUNIT3T006
UMVKZNumerator (factor) for Conversion of Sales Qty into SKUDEC5
UMVKNDenominator (divisor) for Conversion of Sales Qty into SKUDEC5
MEINSBase Unit of MeasureUNIT3T006
NTGEWNet Weight of the ItemQUAN15,3
BRGEWGross Weight of the ItemQUAN15,3
GEWEIWeight UnitUNIT3T006
VOLUMVolume of the ItemQUAN15,3
VOLEHVolume UnitUNIT3T006
SPARTDivisionCHAR2TSPA
WERKSPlant (Own or External)CHAR4T001W
LGORTStorage LocationCHAR4T001L
VSTELShipping Point/Receiving PointCHAR4
ROUTERouteCHAR6
STKEYBill of Material OriginCHAR1
STDATBOM DateDATS8
STLNRBill of MaterialCHAR8
OBJNRObject Number at Item LevelCHAR22
PRCTRProfit CenterCHAR10CEPC
MVGR1Material Group 1CHAR3
MVGR2Material Group 2CHAR3
MVGR3Material Group 3CHAR3
MVGR4Material Group 4CHAR3
MVGR5Material Group 5CHAR3
PRODHProduct HierarchyCHAR18
SHKZGReturns ItemCHAR1
SKTOFCash Discount IndicatorCHAR1
KNUMHNumber of Condition Record from Batch DeterminationCHAR10
CMPREItem Credit PriceCURR11,2
KOUPDCondition UpdateCHAR1

Lengths shown as ECC / S/4HANA where the extended material number applies.

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 VBAP 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  : VBAP Sales Document: Item Data
-- Purpose: Column-selected read of VBAP — auto-generated from field metadata
-- Grain  : One row per VBELN + POSNR
-- 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
  l.MANDT  AS "Client",
  l.VBELN  AS "Sales Document",
  l.POSNR  AS "Sales Document Item",
  l.MATNR  AS "Material Number",
  l.MATWA  AS "Material Entered",
  l.PMATN  AS "Pricing Reference Material",
  l.CHARG  AS "Batch Number",
  l.MATKL  AS "Material Group",
  l.ARKTX  AS "Short Text for Sales Order Item",
  l.PSTYV  AS "Sales Document Item Category",
  l.POSAR  AS "Item Type",
  l.LFREL  AS "Item Is Relevant for Delivery",
  l.FKREL  AS "Relevant for Billing",
  l.UEPOS  AS "Higher-Level Item in BOM Structures",
  l.GRPOS  AS "Alternative for Item",
  l.ABGRU  AS "Reason for Rejection of Quotations and Sales Orders",
  l.NETWR  AS "Net Value of the Order Item in Document Currency",
  l.WAERK  AS "SD Document Currency",
  l.NETPR  AS "Net Price",
  l.KPEIN  AS "Condition Price Unit",
  l.KMEIN  AS "Condition Unit",
  l.KWMENG AS "Cumulative Order Quantity in Sales Units",
  l.VRKME  AS "Sales Unit",
  l.UMVKZ  AS "Numerator (factor) for Conversion of Sales Qty into SKU",
  l.UMVKN  AS "Denominator (divisor) for Conversion of Sales Qty into SKU",
  l.MEINS  AS "Base Unit of Measure",
  l.NTGEW  AS "Net Weight of the Item",
  l.BRGEW  AS "Gross Weight of the Item",
  l.GEWEI  AS "Weight Unit",
  l.VOLUM  AS "Volume of the Item",
  l.VOLEH  AS "Volume Unit",
  l.SPART  AS "Division",
  l.WERKS  AS "Plant (Own or External)",
  l.LGORT  AS "Storage Location",
  l.VSTEL  AS "Shipping Point/Receiving Point",
  l.ROUTE  AS "Route",
  l.STKEY  AS "Bill of Material Origin",
  l.STDAT  AS "BOM Date",
  l.STLNR  AS "Bill of Material",
  l.OBJNR  AS "Object Number at Item Level"
  -- … plus 12 more columns — full list in the Fields section above
FROM <catalog>.<schema>.vbap l
WHERE
  l.MANDT = '<MANDT>'
ORDER BY l.VBELN;

Verified August 2026

More query patterns: VA01 VA02 VA03

Released CDS views over this table

Released SAP standard VDM views that read over VBAP. 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
  • VBAPMARAforeign key · N:1
    ON vbap.MATNR = mara.MATNR
  • VBAPT001Wforeign key · N:1
    ON vbap.WERKS = t001w.WERKS
  • VBAPVBEPheader item · 1:N
    ON vbap.VBELN = vbep.VBELN

Transaction Codes That Use This Table

More Sales & Distribution tables