💎Mastering SAP SD Tables and Relationships [See The Definitive Guide right now!]

🇧🇷 Ver este post na versão em Português ↗
Welcome!
Por Felipe Lamounier, Minas Gerais, Brazil – powered by 🙂My Easy B.I.

• LinkedIn
• Amazon
• Google
• E-mail
• Imagens
• Twitter
• Facebook

In this article we will identify the tables that are part of the SAP SD module (Sales and Distribution) in the SAP ECC on HANA version.
In addition to listing these tables, their relationships and key fields will be shown. So you will have an overview of the SAP SD structure.

To complement your study, also see the main tables and relationships of the module 📦SAP MM (Material Management)↗

Some of the main points covered in this article:

• List of SAP SD tables (KONV, VBAK, VBEP, LIPK, LIPS, etc…)
• SAP SD tables and fields
• Relationship diagram between SD tables
  • SAP KONV table relationships
  • Relationship of the other SAP SD tables

📑 Index:

Relationships:

SAP SD – Sales and Distribuition – Overview
SAP SD – Tables Mapping
SAP SD – Sales Table
SAP SD – Shipping Tables
SAP SD – Billing Tables
SAP SD – Links to FI Tables
SAP SD – Links to MM Tables

Tables covered:

KONV – Conditions (Transaction Data)
LIKP – SD Document: Delivery Header Data
LIPS – SD document: Delivery: Item data
VBAK – Sales Document: Header Data
VBAP – Sales Document: Item Data
VBBE – Sales Requirements: Individual Records
VBEH – Schedule line history
VBEP – Sales Document: Schedule Line Data
VBFA – Sales Document Flow
VBLB – Sales document: Release order data
VBLK – SD Document: Delivery Note Header
VBPA – Sales Document: Partner
VBRK – Billing Document: Header Data
VBRP – Billing Document: Item Data
VBUK – Sales Document: Header Status and Administrative Data
VBUP – Sales Document: Item Status
VEKP – Handling Unit – Header Table
VEPO – Packing: Handling Unit Item (Contents)
VEPVG – Delivery Due Index

Want to learn more? Access our area 🎓🚀Training&Education↗

First Steps in SAP S/4HANA Sales and Distribution (SD) eBook Kindle

Configuration Guide For SAP Sales and Distribution: Sap SD Configuration Guide Ebook Kindle

📖 Content – Relationships:

SAP SD – Sales and Distribuition – Overview:

SAP SD – Tables Mapping

Sales/Order Document

1. VBAK (Sales Doc: Header):
   • Main fields: Sales doc (VBELN)
   • Relationships:
     • VBBE (Sales Requirements): VBAK-VBELN = VBBE-VBELN
     • VBLB (Release Order Data): VBAK-VBELN = VBLB-VBELN
     • VBPA (Partner Table): VBPA-VBELN = VBAK-VBELN
     • VBAP (Sales Doc: Item Info): VBAK-VBELN = VBAP-VBELN
     • VBKD (Sales Doc: Business Data): VBKD-VBELN = VBAK-VBELN
     • VBUP (Item Status): VBAK-VBELN = VBAP-VBELN
2. VBAP (Sales Doc: Item Info):
   • Main fields: Sales doc (VBELN), Item (POSNR)
   • Relationships:
     • VBPA (Partner Table): VBAP-VBELN = VBPA-VBELN and VBAP-POSNR = VBPA-POSNR
     • VBEP (Sales Doc: Schedule Lines): VBEP-VBELN = VBAP-VBELN and VBEP-POSNR = VBAP-POSNR
     • VBKD (Sales Doc: Business Data): VBAP-VBELN = VBKD-VBELN and VBAP-POSNR = VBKD-POSNR
     • LIPS (Sales Doc: Delivery Items): VBAP-VBELN = LIPS-VGBEL and VBAP-POSNR = LIPS-VGPOS
     • VBUP (Item Status): VBAP-VBELN = VBUP-VBELN and VBAP-POSNR = VBUP-POSNR
3. VBEP (Sales Doc: Schedule Lines):
   • Main fields: Sales doc (VBELN), Item (POSNR), Schedule Line (ETENR)
   • Relationship with VBAP via Sales doc (VBELN) and Item (POSNR).
4. VBEH (Schedule Line History):
   • Main fields: Sales doc (VBELN), Item (POSNR), Schedule Line (ETENR)
   • Relationship with VBEP via Sales doc (VBELN) and Item (POSNR).
5. VBKD (Sales Doc: Business Data):
   • Main fields: Sales doc (VBELN), Item (POSNR)
   • Relationship with VBAP via Sales doc (VBELN) and Item (POSNR).
6. VBPA (Partner Table):
   • Main fields: Sales doc (VBELN), Item (POSNR), Partner Function (PARVW)
   • Relationship with VBAP via Sales doc (VBELN) and Item (POSNR).
7. VBUP (Item Status):
   • Main fields: Sales doc (VBELN), Item (POSNR)
   • Relationship with VBAK via Sales doc (VBELN) and VBAP via Sales doc (VBELN) and Item (POSNR).

Shipping/Delivery Document

8. VBLK (SD: Delivery Note Header):
   • Main fields: Delivery Note (VBELN)
   • Relationships:
     • VEPO (SD Doc: Shipping Item content): VEPO-VBELN = LIKP-VBELN and VEPO-VENUM = LIKP-VENUM
     • LIKP (Sales Doc: Delivery Header): LIKP-VBELN = LIPS-VBELN
     • VTTP (Shipment Item): VTTP-VBELN = LIKP-VBELN
9. VEPO (SD Doc: Shipping Item content):
   • Main fields: VBELN, VENUM
   • Relationship with LIKP via VBELN and VENUM.
10. LIKP (Sales Doc: Delivery Header):
    
    * Main fields: VBELN
    
    * Relationship with LIPS via VBELN.
11. VTTP (Shipment Item):
    
    * Main fields: VBELN, TKNUM
    
    * Relationship with LIKP via VBELN.
12. VTTK (Shipment Header):
    
    * Main fields: TKNUM
    
    * Relationship with VTTP via TKNUM.
13. LIPS (Sales Doc: Delivery Items):
    
    * Main fields: VBELN, POSNR
    
    * Relationships:
    • VBAP (Sales Doc: Item Info): LIPS-VGBEL = VBAP-VBELN and LIPS-VGPOS = VBAP-POSNR.
    • VBRP (Billing: Item Data): LIPS-VBELN = VBRP-VGBEL and LIPS-POSNR = VBRP-VGPOS.

Billing Document

14. VBRK (Billing: Header Data):
    
    * Main fields: VBELN
    
    * Relationships:
    • VBRP (Billing: Item Data): VBRK-VBELN = VBRP-VBELN.
    • VKDFS (SD Index: Billing Initiator): VBRK-VBELN = VKDFS-VBELN.
    • NAST (Message Status): VBRK-VBELN = NAST-VBELN.
15. VBRP (Billing: Item Data):
    
    * Main fields: VBELN, POSNR
    
    * Relationships:
    • LIPS (Sales Doc: Delivery Items): VBRP-VGBEL = LIPS-VBELN and VBRP-VGPOS = LIPS-POSNR.
    • VBRK (Billing: Header Data): VBRP-VBELN = VBRK-VBELN.
16. VKDFS (SD Index: Billing Initiator):
    
    * Main fields: VBELN
    
    * Relationship with VBRK via VBELN.
17. NAST (Message Status):
    
    * Main fields: VBELN
    
    * Relationship with VBRK via VBELN.

Indexes

18. VAPMA (SD Index: Order Items by Material):
    • Main fields: VBELN
    • Relationship with VBAK via VBELN.
19. VEVFG (Delivery Due Index):
    • Main fields: VBELN
    • Relationship with VBAK via VBELN.
20. VAKPA (SD Index: Order by Partner Function):
    • Main fields: VBELN
    • Relationship with VBAK via VBELN.
21. VBLB (Release Order Data):
    • Main fields: VBELN
    • Relationship with VBAK via VBELN.
22. VBBE (Sales Requirements):
    • Main fields: VBELN
    • Relationship with VBAK via VBELN.

Additional Tables

23. VBSK (Collective Proc. for Sales Doc Header):
    
    * Main fields: VBELN
    
    * Relationship with VBSS (Collective Proc. Sales Documents) via VBELN.
24. VBSS (Collective Proc. Sales Documents):
    
    * Main fields: VBELN
    
    * Relationship with VBSK (Collective Proc. for Sales Doc Header) via VBELN.

Condition

25. KONV (Condition Table):
    
    * Main fields: KNUMV
    
    * Relationship with VBRK via KNUMV.

SAP SD – Sales Table

1. VAKDF (SD Index: Billing Initiator):
   • Main fields: Billing Cat (FKTTYP), Sales Org (VKORG), Billing Date (FKDAT), Customer (KUNNR), Billing Type (FKART), Country (LAND1), Sales doc (VBELN)
   • Relationship with VBAK via Sales doc (VBELN).
2. VAPMA (SD Index: Order Items by Material):
   • Main fields: Material No (MATNR), Sales Org (VKORG), Trans Group (TVOG), Document Date (AUDAT), Distribution Channel (VTWEG), Division (SPART), Document Type (AUART), Sold-to-Party (KUNNR), Sales Office (VKBUR), Customer PO No (BSTNK), User Name (ERNAM), Sales Order (VBELN), Item (POSNR)
   • Relationship with VBAK via Sales doc (VBELN).
3. VAKPA (SD Index: Order by Partner Function):
   • Main fields: Partner No (KUNDE), Partner Function (PARVW), Sales Org (VKORG), Trans Group (TVOG), Document Date (AUDAT), Sales Office (VKBUR), Distribution Channel (VTWEG), Division (SPART), Document Type (AUART), Customer PO No (BSTNK), Sold-to-Party (KUNNR), User Name (ERNAM), Sales doc (VBELN)
   • Relationship with VBAK via Sales doc (VBELN).
4. VBAK (Sales Document: Header):
   • Main fields: Sales doc (VBELN)
   • Relationship with multiple tables::
     • VBAP (Sales Document: Item Info) via Sales doc (VBELN).
     • VBFA (Sales Document Flow) via Sales doc (VBELN).
     • VBUP (Item Status) via Sales doc (VBELN).
     • VBPA (Sales Document: Partner) via Sales doc (VBELN).
     • VBKD (Sales Document: Business Data) via Sales doc (VBELN).
     • VBEP (Sales Document: Schedule Lines) via Sales doc (VBELN).
     • VBEH (Schedule Line History) via Sales doc (VBELN).
     • VBUK (Header Status) via Sales doc (VBELN).
5. VBAP (Sales Document: Item Info):
   • Main fields: Sales doc (VBELN), Item (POSNR)
   • Relationship with:
     • VBPA (Sales Document: Partner) via Sales doc (VBELN) and Item (POSNR).
     • VBKD (Sales Document: Business Data) via Sales doc (VBELN) and Item (POSNR).
     • VBEP (Sales Document: Schedule Lines) via Sales doc (VBELN) and Item (POSNR).
     • VBEH (Schedule Line History) via Sales doc (VBELN) and Item (POSNR).
     • VBUP (Item Status) via Sales doc (VBELN) and Item (POSNR).
6. VBEP (Sales Document: Schedule Lines):
   • Main fields: Sales doc (VBELN), Item (POSNR), Schedule Line (ETENR)
   • Relationship with VBAP via Sales doc (VBELN) and Item (POSNR).
7. VBEH (Schedule Line History):
   • Main fields: Sales doc (VBELN), Item (POSNR), Schedule Line (ETENR)
   • Relationship with VBEP via Sales doc (VBELN) and Item (POSNR).
8. VBUP (Item Status):
   • Main fields: Sales doc (VBELN), Item (POSNR)
   • Relationship with VBAK via Sales doc (VBELN) and VBAP via Sales doc (VBELN) and Item (POSNR).
9. VBPA (Sales Document: Partner):
   • Main fields: Sales doc (VBELN), Item (POSNR), Partner Function (PARVW)
   • Relationship with VBAP via Sales doc (VBELN) and Item (POSNR).
10. VBKD (Sales Document: Business Data):
    
    * Main fields: Sales doc (VBELN), Item (POSNR)
    
    * Relationship with VBAP via Sales doc (VBELN) and Item (POSNR).
11. VBFA (Sales Document Flow):
    
    * Main fields: Preceding Sales Doc (VBELV), Preceding Item (POSNV), Subsequent Sales Doc (VBELN), Subsequent Item (POSNN), Document Cat (VBTYP_N)
    
    * Relationship with VBAK via Sales doc (VBELN).
12. VBUK (Header Status):
    
    * Main fields: Sales doc (VBELN)
    
    * Relationship with VBAK via Sales doc (VBELN).
13. STXH (STXD SAPscript text file header):
    
    * Main fields: Texts (TDOBJECT), Text Name (TDNAME), Text Id (TDID), Language (TDSPRAS)
    
    * Relationship with STXL (STXD SAPscript text file lines) via Texts (TDOBJECT) and Text Name (TDNAME).
14. STXL (STXD SAPscript text file lines):
    
    * Main fields: RELID, Texts (TDOBJECT), Text Name (TDNAME), Text Id (TDID), Language (TDSPRAS), SRTF2
    
    * Relationship with STXH via Texts (TDOBJECT) and Text Name (TDNAME).

In addition to these direct relationships, there is an important connection with the LIPS shipping table, where:

• LIPS-VGBEL is related to VBAP-VBELN
• LIPS-VGPOS is related to VBAP-POSNR

SAP SD – Shipping Tables

SAP SD – Shipment Tables

1. VTTP (Shipment Item):
   • Main fields: Delivery Doc Number (VBELN), Shipment Number (TKNUM), Shipment Item (TPNUM)
   • Relationships:
     • VTTK (Shipment Header): VTTP-TKNUM = VTTK-TKNUM
     • LIKP (Sales Doc: Delivery Header): VTTP-VBELN = LIKP-VBELN
2. VTTK (Shipment Header):
   • Main fields: Shipment Number (TKNUM)
   • Relationship with VTTP (Shipment Item) via TKNUM.
3. VTFA (Shipment Doc. Flow):
   • Main fields: Shipment Number (TKNUM), Preceding Doc. (VBELV)
   • Relationship with VTTK (Shipment Header) via TKNUM.
4. VBLK (SD: Delivery Note Header):
   • Main fields: Delivery Document Number (VBELN)
   • Relationship with LIKP (Sales Doc: Delivery Header) via VBELN.
5. LIKP (Sales Doc: Delivery Header):
   • Main fields: Delivery Document Number (VBELN)
   • Relationships:
     • VBLK (SD: Delivery Note Header) via VBELN.
     • LIPS (Sales Doc: Delivery Items) via VBELN.
     • VTTP (Shipment Item) via VBELN.
6. LIPS (Sales Doc: Delivery Items):
   • Main fields: Delivery Document Number (VBELN), Item (POSNR)
   • Relationships:
     • VBAP (Sales Doc: Item Info): LIPS-VGBEL = VBAP-VBELN and LIPS-VGPOS = VBAP-POSNR.
     • LIKP (Sales Doc: Delivery Header) via VBELN.
     • VEPO (SD Doc: Shipping Item content): VEPO-VBELN = LIPS-VBELN and VEPO-POSNR = LIPS-POSNR.
     • VBRP (Billing: Item Data): VBRP-VGBEL = LIPS-VBELN and VBRP-VGPOS = LIPS-POSNR.
7. VEPO (SD Doc: Shipping Item content):
   • Main fields: Delivery Document Number (VBELN), Delivery Item (POSNR), Shipping Unit Number (VENUM), Shipping Unit Item (VEPOPOS)
   • Relationships:
     • LIPS (Sales Doc: Delivery Items) via VBELN and POSNR.
     • VEKP (SD Doc: Shipping Unit Header): VEPO-VENUM = VEKP-VENUM.
8. VEKP (SD Doc: Shipping Unit Header):
   • Main fields: Shipping Unit Number (VENUM)
   • Relationship with VEPO (SD Doc: Shipping Item content) via VENUM.
9. VBUP (Item Status):
   • Main fields: Delivery doc (VBELN), Item (POSNR)
   • Relationship with LIKP (Sales Doc: Delivery Header) via VBELN and with LIPS (Sales Doc: Delivery Items) via VBELN and POSNR.
10. VBFA (Sales Document Flow):
    
    * Main fields: Preceding Sales Doc (VBELV), Preceding Item (POSNV), Subsequent Sales Doc (VBELN), Subsequent Item (POSNN), Document Cat (VBTYP_N)
    
    * Relationship with LIPS (Sales Doc: Delivery Items) via VBELN.
11. VBUK (Header Status):
    
    * Main fields: Delivery doc (VBELN)
    
    * Relationship with LIKP (Sales Doc: Delivery Header) via VBELN.

Relationship Summary

• VTTP is related to VTTK and LIKP.
• VTTK is related to VTTP.
• VTFA is related to VTTK.
• VBLK is related to LIKP.
• LIKP is related to VBLK, LIPS, VTTP, and VBUK.
• LIPS is related to VBAP, LIKP, VEPO, VBFA, and VBRP.
• VEPO is related to LIPS and VEKP.
• VEKP is related to VEPO.
• VBUP is related to LIKP and LIPS.
• VBFA is related to LIPS.
• VBUK is related to LIKP.

SAP SD – Billing Tables

SAP SD – Billing Tables

1. VBRK (Billing: Header Data):
   • Main fields: Billing doc (VBELN)
   • Relationships:
     • VBRP (Billing: Item Data): VBRK-VBELN = VBRP-VBELN.
     • VKDFS (SD Index: Billing Initiator): VBRK-VBELN = VKDFS-VBELN.
     • NAST (Billing: Header Data): VBRK-VBELN = NAST-OBJKY.
     • VBSS (Collective Processing: Sales Documents): VBRK-VBELN = VBSS-VBELN.
2. VBRP (Billing: Item Data):
   • Main fields: Billing doc (VBELN), Item (POSNR)
   • Relationships:
     • LIPS (Sales Doc: Delivery Items): VBRP-VGBEL = LIPS-VBELN and VBRP-VGPOS = LIPS-POSNR.
     • VBRK (Billing: Header Data) via Billing doc (VBELN).
3. VKDFS (SD Index: Billing Initiator):
   • Main fields: Billing Cat (FKTTYP), Sales Org (VKORG), Billing Date (FKDAT), Customer (KUNNR), Billing Type (FKART), Country (LAND1), Sales doc (VBELN)
   • Relationship with VBRK via Sales doc (VBELN).
4. VBSK (Collective Processing for a Sales Document Header):
   • Main fields: Grouped Delivery (SAMMG)
   • Relationship with VBSS (Collective Processing: Sales Documents) via SAMMG.
5. VBSS (Collective Processing: Sales Documents):
   • Main fields: Grouped Delivery (SAMMG), Sales doc (VBELN)
   • Relationship with VBSK via SAMMG.
6. NAST (Billing: Header Data):
   • Main fields: Application (KAPPL), Object (OBJKY), Output Type (KSCHL), Language (SPRAS), Mess Partner (PARNR), Partner Func (PARVW), Date (ERDAT), Time (ERUHR)
   • Relationship with VBRK (Billing: Header Data) via Object (OBJKY).
7. VBPA (Sales Index: Bills by Partner Functions):
   • Main fields: Partner No (KUNDE), Partner Function (PARVW), Sales Org (VKORG), Billing Date (FKDAT), Distribution Channel (VTWEG), Billing Type (FKART), Payer (KUNNR), Sold-to-Party (KUNNR), SD Doc Cat (VBTYP), User Name (ERNAM), Billing Doc (VBELN)
   • Relationship with VBRK (Billing: Header Data) via Billing Doc (VBELN).
8. VRPMA (SD Index: Billing Items per Material):
   • Main fields: Material No (MATNR), Sales Org (VKORG), Billing Date (FKDAT), Distribution Channel (VTWEG), Billing Type (FKART), Payer (KUNNR), Sold-to-Party (KUNNR), SD Doc Cat (VBTYP), User Name (ERNAM), Billing Doc (VBELN), Item (POSNR)
   • Relationship with VBRP (Billing: Item Data) via Billing Doc (VBELN) and Item (POSNR).
9. VBUK (Header Status):
   • Main fields: Sales doc (VBELN)
   • Relationship with VBRK (Billing: Header Data) via Sales doc (VBELN).
10. VBUP (Sales Document: Item Status):
    
    * Main fields: Sales doc (VBELN), Item (POSNR)
    
    * Relationship with VBRP (Billing: Item Data) via Sales doc (VBELN) and Item (POSNR).
11. VBFA (Sales Document Flow):
    
    * Main fields: Preceding Sales Doc (VBELV), Preceding Item (POSNV), Subsequent Sales Doc (VBELN), Subsequent Item (POSNN), Document Cat (VBTYP_N)
    
    * Relationship with VBRP (Billing: Item Data) via Subsequent Sales Doc (VBELN).

Summary of Relationships

• VBRK is related to VBRP, VKDFS, NAST, and VBSS.
• VBRP is related to LIPS, VBRK, and VBFA.
• VKDFS is related to VBRK.
• VBSK is related to VBSS.
• VBSS is related to VBSK and VBRK.
• NAST is related to VBRK.
• VBPA is related to VBRK.
• VRPMA is related to VBRP.
• VBUK is related to VBRK.
• VBUP is related to VBRP.
• VBFA is related to VBRP.

SAP SD – Links to FI Tables

SAP SD – Links to FI Tables

Customer Master Data

1. KNA1 (General Data in Customer Master):
   • Main fields: Customer No (KUNNR)
   • Relationships:
     • KNVV (Customer Master Sales Data) via Customer No (KUNNR).
     • KNVP (Customer Master Partner Functions) via Customer No (KUNNR).
     • KNVD (Customer Master Record Sales Request Form) via Customer No (KUNNR).
     • KNB1 (Customer Master: Company Code) via Customer No (KUNNR).

Sales Area Data

2. KNVP (Customer Master Partner Functions):
   • Main fields: Customer No (KUNNR), Sales Org (VKORG), Distribution Ch (VTWEG), Division (SPART), Partner Function (PARVW), Partner Counter (PARZA)
   • Relationships:
     • KNA1 (General Data in Customer Master) via Customer No (KUNNR).
3. KNVV (Customer Master Sales Data):
   • Main fields: Customer No (KUNNR), Sales Org (VKORG), Distribution Ch (VTWEG), Division (SPART)
   • Relationships:
     • KNA1 (General Data in Customer Master) via Customer No (KUNNR).
4. KNVD (Customer Master Record Sales Request Form):
   • Main fields: Customer No (KUNNR), Sales Org (VKORG), Distribution Ch (VTWEG), Division (SPART), Output Type
   • Relationships:
     • KNA1 (General Data in Customer Master) via Customer No (KUNNR).

Company Code Data

5. KNB1 (Customer Master: Company Code):
   • Main fields: Customer No (KUNNR), Company Code (BUKRS)
   • Relationships:
     • KNA1 (General Data in Customer Master) via Customer No (KUNNR).
     • KNB5 (Customer Master: Dunning Data) via Customer No (KUNNR) and Company Code (BUKRS).
6. KNB5 (Customer Master: Dunning Data):
   • Main fields: Customer No (KUNNR), Company Code (BUKRS), Dunning Area (MABER)
   • Relationship with KNB1 (Customer Master: Company Code) via Customer No (KUNNR) and Company Code (BUKRS).

Summary of Relationships

markdown

• KNA1 (General Data in Customer Master) is related to:
  • KNVV (Customer Master Sales Data)
  • KNVP (Customer Master Partner Functions)
  • KNVD (Customer Master Record Sales Request Form)
  • KNB1 (Customer Master: Company Code)
• KNVV (Customer Master Sales Data) is related to KNA1 via Customer No (KUNNR).
• KNVP (Customer Master Partner Functions) is related to KNA1 via Customer No (KUNNR).
• KNVD (Customer Master Record Sales Request Form) is related to KNA1 via Customer No (KUNNR).
• KNB1 (Customer Master: Company Code) is related to:
  • KNA1 (General Data in Customer Master) via Customer No (KUNNR).
  • KNB5 (Customer Master: Dunning Data) via Customer No (KUNNR) and Company Code (BUKRS).
• KNB5 (Customer Master: Dunning Data) is related to KNB1 via Customer No (KUNNR) and Company Code (BUKRS).

SAP SD – Links to MM Tables

SAP SD – Links to MM Tables

Material Master Data

1. MARA (Material Master: General Data):

• Main fields: Material No (MATNR)
• Relationships:
  • MARC (Material Master: C Segment) via Material No (MATNR).
  • MVKE (Material Master: Sales Data) via Material No (MATNR).
  • MAKT (Material Descriptions) via Material No (MATNR).
  • MARM (Units of Measure) via Material No (MATNR).

Sales Data

2. MARC (Material Master: C Segment):
   • Main fields: Material No (MATNR), Plant (WERKS)
   • Relationship with MARA (Material Master: General Data) via Material No (MATNR).
3. MVKE (Material Master: Sales Data):
   • Main fields: Material No (MATNR), Sales Org (VKORG), Distribution Chan (VTWEG), Product Hierarchy (PRODH)
   • Relationships:
     • MARA (Material Master: General Data) via Material No (MATNR).
     • T179 (Materials: Product Hierarchies) via Product Hierarchy (PRODH).
4. MLAN (Tax Classification: Material):
   • Main fields: Material No (MATNR), Country (ALAND)
   • Relationship with MARA (Material Master: General Data) via Material No (MATNR).
5. T179 (Materials: Product Hierarchies):
   • Main fields: Product Hierarchy (PRODH)
   • Relationship with MVKE (Material Master: Sales Data) via Product Hierarchy (PRODH).

Basic Data

6. MAKT (Material Descriptions):
   • Main fields: Material No (MATNR), Language (SPRAS)
   • Relationship with MARA (Material Master: General Data) via Material No (MATNR).
7. MARM (Units of Measure):
   • Main fields: Material No (MATNR), UOM (MEINH)
   • Relationship with MARA (Material Master: General Data) via Material No (MATNR).

Sales Text Data

8. STXH (STXD SAPscript text file header):
   • Main fields: Texts (TDOBJECT), Text Name (TDNAME), Text Id (TDID), Language (TDSPRAS)
   • Relationship with STXL (STXD SAPscript text file lines) via Texts (TDOBJECT) and Text Name (TDNAME).
9. STXL (STXD SAPscript text file lines):
   • Main fields: RELID, Texts (TDOBJECT), Text Name (TDNAME), Text Id (TDID), Language (TDSPRAS), SRTF2
   • Relationship with STXH (STXD SAPscript text file header) via Texts (TDOBJECT) and Text Name (TDNAME).

Summary of Relationships

• MARA (Material Master: General Data) is related to:
  • MARC (Material Master: C Segment)
  • MVKE (Material Master: Sales Data)
  • MAKT (Material Descriptions)
  • MARM (Units of Measure)
• MARC (Material Master: C Segment) is related to MARA via Material No (MATNR).
• MVKE (Material Master: Sales Data) is related to MARA via Material No (MATNR) and to T179 via Product Hierarchy (PRODH).
• MLAN (Tax Classification: Material) is related to MARA via Material No (MATNR).
• T179 (Materials: Product Hierarchies) is related to MVKE via Product Hierarchy (PRODH).
• MAKT (Material Descriptions) is related to MARA via Material No (MATNR).
• MARM (Units of Measure) is related to MARA via Material No (MATNR).
• STXH (STXD SAPscript text file header) is related to STXL via Texts (TDOBJECT) and Text Name (TDNAME).
• STXL (STXD SAPscript text file lines) is related to STXH via Texts (TDOBJECT) and Text Name (TDNAME).

📖 Content – Tables covered:

KONV – Conditions (Transaction Data)

Keys:
KNUMV – Number of the document condition
KPOSN – Condition item number
STUNR – Step number
ZAEHK – Condition counter

LIKP – SD Document: Delivery Header Data

Key:
VBELN – Delivery

LIPS – SD document: Delivery: Item data

Keys:
VBELN – Delivery
POSNR – Delivery Item

VBAK – Sales Document: Header Data

Key:
VBELN – Sales Document

VBAP – Sales Document: Item Data

Keys:
VBELN – Sales Document
POSNR – Sales Document Item

VBBE – Sales Requirements: Individual Records

Keys:
VBELN – Sales Document
POSNR – Sales Document Item
ETENR – Schedule Line Number

VBEH – Schedule line history

Keys:
VBELN – Sales Document
POSNR – Sales Document Item
ETENR – Schedule Line Number
ABRLI – Internal delivery schedule number
ABART – Rel. Type

VBEP – Sales Document: Schedule Line Data

Keys:
VBELN – Sales Document
POSNR – Sales Document Item
ETENR – Schedule Line Number

VBFA – Sales Document Flow

Keys:
VBELV – Preceding sales and distribution document
POSNV – Preceding item of an SD document
VBELN – Subsequent sales and distribution document
POSNN – Subsequent item of an SD document
VBTYP_N – Document category of subsequent document

VBLB – Sales document: Release order data

Keys:
VBELN – Sales Document
POSNR – Sales Document Item
ABRLI – Internal delivery schedule number
ABART – Rel. Type

VBLK – SD Document: Delivery Note Header

Key:
VBELN – Delivery

VBPA – Sales Document: Partner

Keys:
VBELN – Sales and Distribution Document Number
POSNR – Item number of the SD document
PARVW – Partner Function

VBRK – Billing Document: Header Data

Key:
VBELN – Billing Document

VBRP – Billing Document: Item Data

Keys:
VBELN – Billing Document
POSNR – Billing item

VBUK – Sales Document: Header Status and Administrative Data

Key:
VBELN – Sales and Distribution Document Number

VBUP – Sales Document: Item Status

Key:
VBELN – Sales and Distribution Document Number
POSNR – Item number of the SD document

VEKP – Handling Unit – Header Table

Key:
VENUM – Internal Handling Unit Number

VEPO – Packing: Handling Unit Item (Contents)

Keys:
VENUM – Internal Handling Unit Number
VEPOS – Handling Unit Item

VEPVG – Delivery Due Index

Keys:
VSTEL – Shipping Point/Receiving Point
LEDAT – Delivery Creation Date
LPRIO – Delivery Priority
ROUTE – Route
SPDNR – Forwarding agent
WADAT – Goods Issue Date
KUNWE – Ship-To Party
VBELN – Sales and Distribution Document Number
LIFSP – Delivery block for header or schedule line

✅ Conclusion:

In this article you saw the tables of the SAP SD module (Sales and Distribution). Mainly you got to know how they interact with each other in the system knowing the relationship between the tables. All key fields were also shown.
Use this article as a guide for the SAP SD module and whenever you have questions, come back here to make your life easier!

Keywords: SD tables; List of SAP SD tables; SAP SD; SAP ECC SD; Relationship between SAP SD tables; KONV; LIKP; LIPS; VBAK; VBAP; VBBE; VBEH; VBEP; VBFA; VBLB; VBLK; VBPA; VBRK; VBRP; VBUK; VBUP; VEKP; VEPO; VEPVG; sap conditions table; sap sd academy; sap sd mm; sap konv table relationships; Mastering SAP SD Tables and Relationships (ECC on HANA); sap sd tables connectivity

Did you like the content? Want to get more tips? Subscribe ↗ for free!

Follow on social media:

• Twitter
• Facebook
• Instagram
• LinkedIn

• 
  How to Find Deleted VTTK Transport in SAP ECC
  por felipelamounier
  Bem Vindo! | Welcome! By Felipe Lamounier, Minas Gerais, Brasil🇧🇷 – powered by 🙂My Easy B.I. 📑 Table of Contents: Introduction In this post, we will learn how to identify which transports were deleted in SAP ECC. We will also see how this data is removed from the VTTK table over a specific period. InContinuar lendo “How to Find Deleted VTTK Transport in SAP ECC”
• 
  How to identify SAP BW Process Chains with Recurring Errors
  por felipelamounier
  This post by Felipe Lamounier focuses on identifying recurring errors in Process Chains (RSPC) within SAP BW over a 65-day period. It provides a structured approach to filter and analyze execution logs, aimed at improving resource management and system efficiency by addressing improperly executed chains. The analysis concludes with recommendations for maintaining or removing chains based on error frequency.
• 
  How to Retrieve SAP Table Metadata Efficiently
  por felipelamounier
  This post by Felipe Lamounier provides a guide on efficiently retrieving metadata from SAP table fields using transaction SE16 and the DD03M view. Key elements include data element, data type, field length, and descriptions. Additionally, the post lists important SAP system tables, enhancing understanding of SAP metadata extraction.