# SAP SD Tables Reference: Sales, Delivery and Billing Tables > Source: https://netray.co/tools/sap-sd-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Lookup of the main SAP SD tables with their key fields and what changed in S/4HANA. Search, then export to Excel or PDF. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP SD consultant - ABAP developer - SAP functional analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Description **Key:** desc **Type:** text #### Key fields **Key:** keys **Type:** text #### Area **Key:** area **Type:** text #### S/4HANA note **Key:** s4 **Type:** text **Rows:** **Table:** VBAK **Desc:** Sales document: header data **Keys:** VBELN **Area:** Sales **S4:** Absorbs header status fields formerly in VBUK **Table:** VBAP **Desc:** Sales document: item data **Keys:** VBELN, POSNR **Area:** Sales **S4:** Absorbs item status fields formerly in VBUP **Table:** VBEP **Desc:** Sales document: schedule line data **Keys:** VBELN, POSNR, ETENR **Area:** Sales **S4:** Unchanged key structure **Table:** VBKD **Desc:** Sales document: business data (payment terms, incoterms, PO data) **Keys:** VBELN, POSNR **Area:** Sales **S4:** Header row has POSNR 000000 **Table:** VBPA **Desc:** Sales document: partner **Keys:** VBELN, POSNR, PARVW **Area:** Sales **S4:** Header partners have POSNR 000000 **Table:** VBFA **Desc:** Sales document flow **Keys:** VBELV, POSNV, VBELN, POSNN, VBTYP_N **Area:** Document flow **S4:** Still the main document flow table **Table:** VBUK **Desc:** Sales document: header status and administrative data **Keys:** VBELN **Area:** Status **S4:** Obsolete in S/4HANA, status moved into VBAK, LIKP and VBRK **Table:** VBUP **Desc:** Sales document: item status **Keys:** VBELN, POSNR **Area:** Status **S4:** Obsolete in S/4HANA, status moved into VBAP, LIPS and VBRP **Table:** VBBE **Desc:** Sales requirements: individual records **Keys:** VBELN, POSNR, ETENR and others **Area:** Availability **S4:** Check ATP and MRP changes for your release **Table:** LIKP **Desc:** SD document: delivery header data **Keys:** VBELN **Area:** Delivery **S4:** Holds header status fields in S/4HANA **Table:** LIPS **Desc:** SD document: delivery item data **Keys:** VBELN, POSNR **Area:** Delivery **S4:** Holds item status fields in S/4HANA **Table:** VBRK **Desc:** Billing document: header data **Keys:** VBELN **Area:** Billing **S4:** Holds header status fields in S/4HANA **Table:** VBRP **Desc:** Billing document: item data **Keys:** VBELN, POSNR **Area:** Billing **S4:** Unchanged key structure **Table:** KONV **Desc:** Conditions (transaction data): pricing results per document **Keys:** KNUMV, KPOSN, STUNR, ZAEHK **Area:** Pricing **S4:** Replaced by PRCD_ELEMENTS in S/4HANA **Table:** PRCD_ELEMENTS **Desc:** Pricing elements: document conditions **Keys:** KNUMV, KPOSN, STUNR, ZAEHK **Area:** Pricing **S4:** S/4HANA replacement for KONV **Table:** KONH **Desc:** Conditions: header (condition records) **Keys:** KNUMH **Area:** Pricing **S4:** Unchanged **Table:** KONP **Desc:** Conditions: items (rates and scales) **Keys:** KNUMH, KOPOS **Area:** Pricing **S4:** Unchanged **Table:** T685 **Desc:** Conditions: types **Keys:** KVEWE, KAPPL, KSCHL **Area:** Pricing config **S4:** Customizing table **Table:** T683 **Desc:** Pricing procedures **Keys:** KVEWE, KAPPL, KALSM **Area:** Pricing config **S4:** Customizing table **Table:** KNA1 **Desc:** General data in customer master **Keys:** KUNNR **Area:** Customer **S4:** Business Partner is the leading object, KNA1 is still populated **Table:** KNB1 **Desc:** Customer master: company code data **Keys:** KUNNR, BUKRS **Area:** Customer **S4:** Populated through Business Partner **Table:** KNVV **Desc:** Customer master: sales data **Keys:** KUNNR, VKORG, VTWEG, SPART **Area:** Customer **S4:** Populated through Business Partner **Table:** KNVP **Desc:** Customer master: partner functions **Keys:** KUNNR, VKORG, VTWEG, SPART, PARVW, PARZA **Area:** Customer **S4:** Populated through Business Partner **Table:** MVKE **Desc:** Material master: sales data **Keys:** MATNR, VKORG, VTWEG **Area:** Material **S4:** Unchanged **Table:** TVAK **Desc:** Sales document types **Keys:** AUART **Area:** Sales config **S4:** Customizing table behind VOV8 **Table:** TVAP **Desc:** Sales document: item categories **Keys:** PSTYV **Area:** Sales config **S4:** Customizing table behind VOV7 **Table:** TVLK **Desc:** Delivery types **Keys:** LFART **Area:** Delivery config **S4:** Customizing table **Table:** TVFK **Desc:** Billing types **Keys:** FKART **Area:** Billing config **S4:** Customizing table **Table:** TVKO **Desc:** Organizational unit: sales organizations **Keys:** VKORG **Area:** Org structure **S4:** Customizing table **Table:** TVKOV **Desc:** Organizational unit: distribution channels per sales organization **Keys:** VKORG, VTWEG **Area:** Org structure **S4:** Customizing table **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use this table list **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### Which table has the sales order header in SAP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap sd tables list, vbak vbap tables, sap sales order tables, sap sd table names, likp lips table, vbrk vbrp table, sap sd tables in s4hana, sap document flow table vbfa --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json