top of page

Deep Dive: Key SAP SD Tables Every Consultant Must Know

Updated: 2 days ago


🔹 Introduction


Whether you're a functional consultant trying to debug a blocked invoice or a technical analyst exploring data flow across modules, understanding the database structure of SAP's SD (Sales & Distribution) module is essential.


SAP's design relies on a structured data model that links every business process with its technical foundation. In this article, I break down the most critical SD-related tables - including their business purpose, key fields with descriptions, and real-life lookup scenarios - to help you connect the dots between the front-end and the back-end.


🏗️ Enterprise Structure Tables

Table

Purpose

Key Fields & Descriptions

TVKO

Sales Organizations

VKORG – Sales Org. BUKRS – Company Code

TVKOV

Distribution Channels per Sales Organization

VKORG – Sales Org. VTWEG – Dist. Channel

TVKOS

Divisions per Sales Organization

VKORG – Sales Org. SPART – Division

TVAKZ

Allowed Order Types per Sales Org.

VKORG – Sales Org. AUART – Sales Doc. Type

TVTA

Sales Areas

VKORG – Sales Org. VTWEG – Dist. Channel SPART – Division


📂 Master Data Tables

Table

Purpose

Key Fields & Descriptions

KNA1

General Data in Customer Master

KUNNR – Customer KTOKD – Account Group LAND1 – Country

KNVV

Customer Master Sales Data

KUNNR – Customer VKORG – Sales Org. KALKS – Pricing Procedure

MARA

General Material Data

MATNR – Material Number MTART – Material Type MATKL – Material Group

MVKE

Sales Data for Material

MATNR – Material Number VKORG – Sales Org. KTGRM – Acct Asgnmt Grp.


🧾 Transactional Data Tables

Table

Purpose

Key Fields & Descriptions

VBAK

Sales Document: Header Data

VBELN – Sales Doc. No AUART – Sales Doc. Type KUNNR – Sold-to Party KNUMV – Doc. Condition

VBAP

Sales Document: Item Data

POSNR – Item No MATNR – Material PSTYV – Item Category ARKTX – Description

VBEP

Sales Document: Schedule Line Data

VBELN – Sales Doc. No ETENR – Schedule Line EDATU – Delivery Date BMENG – Confirmed Qty

LIKP

SD Document: Delivery Header Data

VBELN – Delivery No LFART – Delivery Type LFDAT – Delivery Date VSTEL – Shipping Point

LIPS

SD Document: Delivery: Item Data

POSNR – Item No WERKS – Plant LGORT – Stor. Location LFIMG – Delivery Qty

VBRK

Billing Document: Header Data

VBELN – Billing Doc. No FKART – Billing Type FKDAT – Billing Date KUNRG – Payer

VBRP

Billing Document: Item Data

POSNR – Item No FKIMG – Billed Qty NETWR – Net Value MWSKZ – Tax Code


💰 Pricing & Condition Tables

Table

Purpose

Key Fields & Descriptions

KONV

Conditions (Transaction Data)

KNUMV – Doc. Condition KSCHL – Condition Type KBETR – Amount

KONP

Conditions (Item)

KNUMH – Cond. Record No KSCHL – Condition Type KBETR – Amount

A* (e.g., A004)

Material

KSCHL – Condition Type VKORG – Sales Org. MATNR – Material Number


🔄 Document Flow & Status Tables

Table

Purpose

Key Fields & Descriptions

VBFA

Sales Document Flow

VBELV – Preceding Doc. VBELN – Follow-on Doc. VBTYP_* – Doc. Categories

VBUK

Sales Document: Header Status and Administrative Data

GBSTK – Overall Status FKSTK – Billing Status LFSTK – Delivery Status

VBUP

Sales Document: Item Status

GBSTA – Overall Status FKSTA – Billing Status LFSTA – Delivery Status


📚 FI Integration Tables

Table

Purpose

Key Fields & Descriptions

BKPF

Accounting Document Header

BELNR – Doc. Number BUKRS – Company Code BUDAT – Posting Date

BSEG

Accounting Document Segment

KOART – Account Type HKONT – G/L Account WRBTR – Amount


🔎 Practical Lookup Scenarios (Real-Life SAP SD Navigation)


Here are 3 real-life scenarios that you’ll often encounter in support or data analysis — with the step-by-step table trace.


🧭 Scenario 1: From Customer to Billing Document


Goal: Start from customer number, find sales order, delivery, and billing document.

1. VBAK-KUNNR = Customer ➝ Get Sales Order (VBAK-VBELN) 

2. LIPS-VGBEL = Sales Order ➝ Get Delivery (LIPS-VBELN) 

3. VBRP-VGBEL = Delivery ➝ Get Billing Document (VBRP-VBELN)



📦 Scenario 2: From Billing Date to Full Process


Goal: Trace backwards from billing document date.

1. VBRK-FKDAT = Date ➝ Get Billing Doc (VBRK-VBELN) 

2. VBRP ➝ Get Delivery via VBRP-VGBEL 

3. LIPS ➝ Get Sales Order via LIPS-VGBEL

🧾 Scenario 3: From Sales Order to Billed Quantity


Goal: See how much quantity from an order has been billed.

1. VBRP-AUBEL = Sales Order ➝ Get Billing Doc No (VBRP-VBELN) 

2. VBRP-POSNR ➝ Get Quantity Billed (VBRP-FKIMG)




✅ Conclusion


Mastering the technical structure of SAP SD isn’t just for developers — it’s essential for any consultant aiming to troubleshoot faster, build smarter reports, or explain data flow with confidence.


These tables and fields are the backbone of every process from sales order to invoice. Save this reference guide, use it during testing and analysis, and keep sharpening your edge as an SAP professional.



Mahmut Yaka 

SAP SD Consultant



Commentaires


bottom of page