SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP SD Tables Reference: Sales, Delivery and Billing Tables

SAP SD stores a sales process across many tables, and picking the right one saves hours in reports, ABAP selects and data migration. This lookup lists the core sales, delivery, billing, pricing and customer tables with their key fields and the S/4HANA differences.

Download:

Table	Description	Key fields	Area	S/4HANA note
VBAK	Sales document: header data	VBELN	Sales	Absorbs header status fields formerly in VBUK
VBAP	Sales document: item data	VBELN, POSNR	Sales	Absorbs item status fields formerly in VBUP
VBEP	Sales document: schedule line data	VBELN, POSNR, ETENR	Sales	Unchanged key structure
VBKD	Sales document: business data (payment terms, incoterms, PO data)	VBELN, POSNR	Sales	Header row has POSNR 000000
VBPA	Sales document: partner	VBELN, POSNR, PARVW	Sales	Header partners have POSNR 000000
VBFA	Sales document flow	VBELV, POSNV, VBELN, POSNN, VBTYP_N	Document flow	Still the main document flow table
VBUK	Sales document: header status and administrative data	VBELN	Status	Obsolete in S/4HANA, status moved into VBAK, LIKP and VBRK
VBUP	Sales document: item status	VBELN, POSNR	Status	Obsolete in S/4HANA, status moved into VBAP, LIPS and VBRP
VBBE	Sales requirements: individual records	VBELN, POSNR, ETENR and others	Availability	Check ATP and MRP changes for your release
LIKP	SD document: delivery header data	VBELN	Delivery	Holds header status fields in S/4HANA
LIPS	SD document: delivery item data	VBELN, POSNR	Delivery	Holds item status fields in S/4HANA
VBRK	Billing document: header data	VBELN	Billing	Holds header status fields in S/4HANA
VBRP	Billing document: item data	VBELN, POSNR	Billing	Unchanged key structure
KONV	Conditions (transaction data): pricing results per document	KNUMV, KPOSN, STUNR, ZAEHK	Pricing	Replaced by PRCD_ELEMENTS in S/4HANA
PRCD_ELEMENTS	Pricing elements: document conditions	KNUMV, KPOSN, STUNR, ZAEHK	Pricing	S/4HANA replacement for KONV
KONH	Conditions: header (condition records)	KNUMH	Pricing	Unchanged
KONP	Conditions: items (rates and scales)	KNUMH, KOPOS	Pricing	Unchanged
T685	Conditions: types	KVEWE, KAPPL, KSCHL	Pricing config	Customizing table
T683	Pricing procedures	KVEWE, KAPPL, KALSM	Pricing config	Customizing table
KNA1	General data in customer master	KUNNR	Customer	Business Partner is the leading object, KNA1 is still populated
KNB1	Customer master: company code data	KUNNR, BUKRS	Customer	Populated through Business Partner
KNVV	Customer master: sales data	KUNNR, VKORG, VTWEG, SPART	Customer	Populated through Business Partner
KNVP	Customer master: partner functions	KUNNR, VKORG, VTWEG, SPART, PARVW, PARZA	Customer	Populated through Business Partner
MVKE	Material master: sales data	MATNR, VKORG, VTWEG	Material	Unchanged
TVAK	Sales document types	AUART	Sales config	Customizing table behind VOV8
TVAP	Sales document: item categories	PSTYV	Sales config	Customizing table behind VOV7
TVLK	Delivery types	LFART	Delivery config	Customizing table
TVFK	Billing types	FKART	Billing config	Customizing table
TVKO	Organizational unit: sales organizations	VKORG	Org structure	Customizing table
TVKOV	Organizational unit: distribution channels per sales organization	VKORG, VTWEG	Org structure	Customizing table

Always confirm field names in SE11 or SE16N on your own system and release. S/4HANA simplification items change status and pricing tables, so check the Simplification List for your target release.

Ask your SAP data in plain language

Optional: a short call on putting a read-only natural language layer over your SAP SD tables.

Optional. The tool and every export work without this. No spam.

How to use this table list

Type a table name or a word such as delivery, status or pricing into the search box to filter the rows. Use the key fields column to build joins correctly: item tables share VBELN with the header and add POSNR, and VBPA and VBKD can hold both header and item rows. Export the filtered result to Excel to paste into a technical specification or a data mapping sheet.

Header and item tables join on VBELN
VBFA links preceding and subsequent documents
Config tables (TVAK, TVAP, TVLK, TVFK) hold the types you set up in IMG

Document structure behind the tables

A standard order to cash flow creates a sales order (VBAK, VBAP, VBEP), an outbound delivery (LIKP, LIPS) and a billing document (VBRK, VBRP). Each new document references its predecessor, and every link is stored in VBFA with a document category in VBTYP_N, for example C for order, J for delivery and M for invoice. Pricing is stored per document in KONV on ECC and in PRCD_ELEMENTS on S/4HANA, keyed by the document condition number KNUMV in the header.

What changed in S/4HANA

Two changes cause most broken custom code. First, the status tables VBUK and VBUP are no longer the source of truth, the status fields now sit in the header and item tables of each document. Second, KONV is replaced by PRCD_ELEMENTS. Customer master data is created through Business Partner, although KNA1, KNVV and related tables are still filled for compatibility. Run the custom code check before you rely on any old select.

Frequently Asked Questions

Which table has the sales order header in SAP?

VBAK holds the sales document header and VBAP holds the items. Schedule lines are in VBEP, business data such as payment terms and incoterms is in VBKD, and partners are in VBPA. All of them are keyed by the sales document number VBELN.

How do I find the delivery created for a sales order?

Read VBFA with the sales order number as VBELV and filter VBTYP_N for the delivery category J. The VBELN returned is the outbound delivery, which you can then read in LIKP and LIPS. Transaction VA03 also shows it under Document Flow.

Where did VBUK go in S/4HANA?

In S/4HANA the status fields from VBUK and VBUP were moved into the header and item tables of the documents, such as VBAK, VBAP, LIKP, LIPS, VBRK and VBRP. Custom code that reads VBUK needs to be adapted for your release.

Where are pricing conditions stored for a sales order?

On ECC the conditions of a document are in KONV. On S/4HANA they are in PRCD_ELEMENTS. The master condition records that drive pricing are in KONH (header) and KONP (rates and scales), under the condition tables named A followed by a number.

If you need these tables queried in plain language instead of writing selects, Netray can put a read-only natural language layer over your SAP data. Ask for a short review of your use case.

Talk to an Expert Explore More Free Tools