SAP tables · LessonBy Ravi M, SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels
VBAP
VBAP is a key SAP table in SD (Sales). It stores sales document items, the line-level data (materials, quantities, values) of sales orders and related documents.
Quick answer
VBAP holds sales line detail, materials, quantities, values, and is central to sales reporting.
Key takeaways
- The key is VBELN + POSNR, one row per order line.
- VBELN, sales document (key).
- POSNR, item number (key).
- Watch out: Reading tables directly instead of using CDS/reports where appropriate.
What it stores
It stores sales document items, the line-level data (materials, quantities, values) of sales orders and related documents.
Key fields
- VBELN, sales document (key).
- POSNR, item number (key).
- MATNR, material.
- KWMENG, order quantity.
- NETWR, net value.
Keys and relationships
The key is VBELN + POSNR, one row per order line. It links to the header (VBAK) via VBELN and to schedule lines (VBEP) and document flow (VBFA).
Working with it
VBAP holds sales line detail, materials, quantities, values, and is central to sales reporting. Join with VBAK on VBELN for full orders. View its structure in SE11 and its data (with authorization) in SE16N.
Common pitfalls
- Reading tables directly instead of using CDS/reports where appropriate.
- Ignoring header/item relationships.
- Performance: querying large tables without indexed selection.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of VBAP?
Frequently asked questions
What does VBAP stand for in SAP?
VBAP is a key SAP table in SD (Sales). It stores sales document items, the line-level data (materials, quantities, values) of sales orders and related documents.
Which fields matter most in VBAP?
The key is VBELN + POSNR, one row per order line.
What is worth remembering about VBAP in practice?
VBAP holds sales line detail, materials, quantities, values, and is central to sales reporting.
What tends to go wrong with VBAP?
Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.