Home About Blog Contact SAP HTML SQL Python AI
📋 SAP ABAP Reference · 2026–27

SAP All Tables List: Complete Reference Guide to Every SAP Module Table Every Professional Must Know

2026–27 Guide Pramod Behera 20 min read SAP ABAP · All Modules

The IN SAP S/4 HANA and ECC All Tables List is one of the most important reference resources for any SAP professional — whether you are a developer (coder) writing ABAP reports, a functional consultant configuring modules, a basis administrator monitoring the system, or a business analyst End User extracting data for reporting. SAP ERP is built on a huge relational database containing thousands of tables that store every part of business data from material masters and sales orders to financial postings and human resource (HR) records. Knowing which table stores what data, what its key fields are, and which module it belongs to is a core skill that separates average SAP users from expert consultants. In this comprehensive SAP All Tables List guide, we cover every major module — MM, SD, FI, CO, HR, PP, WM, PM, and PS — with table names, full descriptions, and key fields so you can find exactly the data you need in SE11 or SE16.

🗄️

Thousands of Tables

SAP ECC 6.0 / S/4HANA contains over 90,000 database tables across all modules and components.

🔍

SE11 — View Any Table

Use transaction SE11 to view table structure, fields, keys and foreign key relationships in any SAP system.

📊

SE16 — Browse Data

Use SE16 or SE16N to browse live table data, filter by key fields and export results for analysis.

💡

Quick Tip: In any SAP screen, press F1 on any field then click the Technical Information button to instantly find which table and field stores that data. This is the fastest way to discover table names while working in SAP transactions.

🛠️ How to Find and Use SAP Tables

Before plunging into the SAP All Tables List, it is important to understand how to actually access and work with these tables inside an SAP system. SAP provides several standard transactions specifically designed for working with database tables.

Transaction SE11 — ABAP Dictionary

SE11 is the ABAP Data Dictionary. It is the primary tool for viewing table metadata structure, fields, data types, key fields, foreign key relationships, and technical settings. Every SAP table in this list can be viewed in SE11. Simply enter the table name and press the Display button. You will see every field, its data type, length, and whether it is part of the primary key. SE11 also shows which tables a field references through foreign keys — this is how you understand table relationships and navigate between tables.

Transaction SE16 and SE16N — Table Browser

SE16 and its improved version SE16N allow you to browse live data stored inside any SAP table. Enter the table name, apply filters on key fields, and execute to retrieve rows of data. SE16N is recommended as it gives a more flexible interface with the ability to enter filter conditions on any field. Both transactions are read-only they cannot be used to change data — making them safe tools for data analysis and investigation.

Transaction SE16H — Table Analysis

SE16H is an enhanced version available in S/4HANA that supports joins, grouping, and aggregation directly from the browser interface. It is particularly useful for quickly analysing large datasets without writing ABAP code.

ABAP — Read a table in code
"Example: Select all records from MARA for a specific material
SELECT *
  FROM mara
  INTO TABLE @lt_mara
  WHERE matnr = @lv_matnr.
SE11 — Structure
SE16N — Live Data
SE16H — Analysis
F1 → Technical Info
ABAP SELECT

📦 SAP MM Tables List — Materials Management

SAP Materials Management (MM) handles procurement, inventory management, and material master data. MM is one of the most table-rich modules in SAP because it manages the full lifecycle of materials from procurement through to stock management and invoice verification. The most important tables in SAP MM are MARA, MARC, MARD, MAKT, EKKO, EKPO, MSEG, and MKPF.

Material Master Tables

The material master in SAP is split across many tables, each storing a different organisational level of material data. MARA stores general data valid across all plants. MARC stores plant-specific data. MARD stores storage location stock quantities. This split design allows SAP to handle materials across thousands of plants and warehouses efficiently.

SAP MM — Material Master Tables
TableDescriptionKey FieldsImportant Fields
MARAGeneral Material Data — valid across all organisational levelsMATNRMTART (type), MATKL (group), MEINS (base UOM), BRGEW (weight)
MARCPlant Data for Material — plant-specific settingsMATNR + WERKSDISMM (MRP type), DZEIT (in-house production time), MINBE (reorder point)
MARDStorage Location Stock Data stock per storage locationMATNR + WERKS + LGORTLABST (unrestricted stock), EINME (restricted stock), SPEME (blocked stock)
MAKTMaterial Descriptions — text in multiple languagesMATNR + SPRASMAKTX (short text), MAKTG (upper case text)
MARMUnits of Measure for Material — alternate UOMMATNR + MEINHUMREZ (numerator), UMREN (denominator), BRGEW (gross weight per UOM)
MVKEMaterial Data for Sales OrganisationMATNR + VKORG + VTWEGMTPOS (item category group), KONDM (material pricing group)
MBEWMaterial Valuation — price and value data per plantMATNR + BWKEYVERPR (moving average price), STPRS (standard price), LBKUM (total valuated stock)
MLANTax Classification of MaterialMATNR + ALANDTAXM1 through TAXM9 (tax indicator per country)

Purchasing Tables (MM-PUR)

Purchasing tables in SAP MM store all procurement document data — purchase requisitions, purchase orders, contracts, and scheduling agreements. EKKO and EKPO are the most frequently used tables in the entire MM module. Every purchase order created in ME21N is stored in EKKO (header) and EKPO (items).

SAP MM — Purchasing Document Tables
TableDescriptionKey FieldsImportant Fields
EKKOPurchasing Document Header — PO, contract, scheduling agreementEBELNBSART (doc type), LIFNR (vendor), EKGRP (purchasing group), BEDAT (PO date)
EKPOPurchasing Document Item — line items of all PO typesEBELN + EBELPMATNR (material), MENGE (quantity), NETPR (net price), WERKS (plant), LGORT (storage loc)
EKKNAccount Assignment in Purchasing — cost centre / GL assignment per PO itemEBELN + EBELP + ZEKKNKOSTL (cost centre), SAKTO (G/L account), AUFNR (order)
EKETScheduling Agreement Schedule LinesEBELN + EBELP + ETENREINDT (delivery date), MENGE (scheduled qty), WEMNG (goods receipt qty)
EBANPurchase Requisition — header and item combinedBANFN + BNFPOMATNR, MENGE, WERKS, AFNAM (requisitioner), EKGRP, BADAT (creation date)
EKBEHistory per Purchasing Document — GR and IR history per PO itemEBELN + EBELP + VGABE + GJAHR + BELNR + BUZEIVGABE (transaction type), MENGE (qty), DMBTR (amount in local currency)
LFA1Vendor Master — General DataLIFNRNAME1 (name), LAND1 (country), ORT01 (city), SPRAS (language)
LFB1Vendor Master — Company Code DataLIFNR + BUKRSAKONT (reconciliation account), ZTERM (payment terms), ZWELS (payment methods)

Inventory Management Tables (MM-IM)

SAP MM — Inventory and Goods Movement Tables
TableDescriptionKey FieldsImportant Fields
MKPFHeader: Material Document — goods movement headerMBLNR + MJAHRBLDAT (document date), BUDAT (posting date), USNAM (user), TCODE
MSEGDocument Segment: Material — goods movement line itemsMBLNR + MJAHR + ZEILEMATNR, WERKS, LGORT, BWART (movement type), MENGE, DMBTR (value)
MCHBBatch Stocks — stock per batch per storage locationMATNR + WERKS + LGORT + CHARGCLABS (unrestricted), CEINM (restricted use), CSPEM (blocked stock)
MCH1Batches (if batch management active) — master record per batchMATNR + CHARGZUSTD (batch status), VFDAT (expiry date), HSDAT (production date)

🛒 SAP SD Tables List — Sales and Distribution

SAP Sales and Distribution (SD) manages the entire order-to-cash process — from customer master and sales order creation through delivery, billing, and payment. The SD module uses an elegant header-item table structure across all its document types. Understanding that VBAK and VBAP work together for sales orders, LIKP and LIPS for deliveries, and VBRK and VBRP for billing documents is the foundation of SD data navigation.

SAP SD — Customer Master Tables
TableDescriptionKey FieldsImportant Fields
KNA1Customer Master — General Data (valid across company codes)KUNNRNAME1, LAND1 (country), ORT01 (city), SPRAS, ADRNR (address number)
KNB1Customer Master — Company Code DataKUNNR + BUKRSAKONT (reconciliation account), ZTERM (payment terms), ZWELS (payment method)
KNVVCustomer Master — Sales Area DataKUNNR + VKORG + VTWEG + SPARTKDGRP (customer group), KONDA (price group), BZIRK (sales district), VKBUR (sales office)
KNVPCustomer Master — Partner FunctionsKUNNR + VKORG + VTWEG + SPART + PARVW + PARZAKUNN2 (partner number), PARVW (partner function: SP, SH, BP, PY)
ADRCAddresses — centralised address storage for all business partnersADDRNUMBER + DATE_FROMNAME1, STREET, CITY1, POST_CODE1, COUNTRY, REGION
SAP SD — Sales Document Tables
TableDescriptionKey FieldsImportant Fields
VBAKSales Document: Header Data — one row per sales order/quotation/contractVBELNAUART (order type), KUNNR (sold-to), VKORG (sales org), AUDAT (order date), NETWR (net value)
VBAPSales Document: Item Data — one row per line itemVBELN + POSNRMATNR, KWMENG (order qty), NETPR (net price), WERKS, LGORT, PSTYV (item category)
VBEPSales Document: Schedule Line Data — delivery dates and quantitiesVBELN + POSNR + ETENREDATU (delivery date), WMENG (confirmed qty), BMENG (assessed qty)
VBPASales Document: Partner — all partners per document (sold-to, ship-to, etc.)VBELN + POSNR + PARVWKUNNR (partner number), PARVW (partner function)
VBUKSales Document: Header Status and Administrative DataVBELNGBSTK (overall status), LFSTK (delivery status), FKSTK (billing status)
VBUPSales Document: Item StatusVBELN + POSNRGBSTA (overall item status), LFSTA (delivery status), FKSTA (billing status)
SAP SD — Delivery and Billing Tables
TableDescriptionKey FieldsImportant Fields
LIKPSD Document: Delivery Header DataVBELNKUNNR (ship-to), LFART (delivery type), WADAT (planned GI date), VSTEL (shipping point)
LIPSSD Document: Delivery Item DataVBELN + POSNRMATNR, LGMNG (delivery qty), WERKS, LGORT, VGBEL (ref sales order number)
VBRKBilling Document: Header DataVBELNFKART (billing type), KUNRG (payer), FKDAT (billing date), NETWR (net value), WAERK (currency)
VBRPBilling Document: Item DataVBELN + POSNRMATNR, FKIMG (billed qty), NETWR (net value), AUBEL (ref sales order), VGBEL (ref delivery)
VBFASales Document Flow — links all SD documents in the order-to-cash chainVBELV + POSNV + VBELN + POSNN + VBTYP_NVBTYP_N (doc category: J=delivery, M=invoice), RFMNG (referenced qty)
🔗

Key SD Document Flow: Sales Order (VBAK/VBAP) → Delivery (LIKP/LIPS) → Billing (VBRK/VBRP). The table VBFA links all three document types together. Always use VBFA to trace the complete document chain for any sales order number.

💰 SAP FI Tables List — Financial Accounting

SAP Financial Accounting (FI) is the backbone of the SAP system, storing all financial transactions, general ledger postings, accounts payable, accounts receivable, and asset accounting data. The FI module uses a cluster table structure — BKPF stores document headers and BSEG stores line items. Every financial posting in SAP creates exactly one BKPF record and at least two BSEG records (debit and credit). Understanding this structure is fundamental for any FI report or ABAP program.

SAP FI — Core Accounting Document Tables
TableDescriptionKey FieldsImportant Fields
BKPFAccounting Document Header — one row per financial documentBUKRS + BELNR + GJAHRBLART (doc type), BUDAT (posting date), BLDAT (doc date), USNAM (user), WAERS (currency)
BSEGAccounting Document Segment — line items (cluster table, read via BSIS/BSAS)BUKRS + BELNR + GJAHR + BUZEIHKONT (G/L account), DMBTR (amount), SHKZG (Dr/Cr indicator), KOSTL, KUNNR, LIFNR
BSISAccounting: Secondary Index for G/L Accounts (Open Items)BUKRS + HKONT + GJAHR + BELNR + BUZEIDMBTR (amount), BUDAT, AUGDT (clearing date — blank if open)
BSASAccounting: Secondary Index for G/L Accounts (Cleared Items)BUKRS + HKONT + GJAHR + BELNR + BUZEIDMBTR, BUDAT, AUGDT (clearing date — filled when cleared)
BSIDAccounting: Secondary Index for Customers (Open Items)BUKRS + KUNNR + GJAHR + BELNR + BUZEIDMBTR, BUDAT, ZFBDT (baseline date), ZTERM (payment terms)
BSADAccounting: Secondary Index for Customers (Cleared Items)BUKRS + KUNNR + GJAHR + BELNR + BUZEIDMBTR, AUGDT (clearing date), AUGBL (clearing document)
BSIKAccounting: Secondary Index for Vendors (Open Items)BUKRS + LIFNR + GJAHR + BELNR + BUZEIDMBTR, BUDAT, ZFBDT, ZTERM
BSAKAccounting: Secondary Index for Vendors (Cleared Items)BUKRS + LIFNR + GJAHR + BELNR + BUZEIDMBTR, AUGDT, AUGBL
SAP FI — General Ledger and Master Data Tables
TableDescriptionKey FieldsImportant Fields
SKA1G/L Account Master (Chart of Accounts) — chart level dataKTOPL + SAKNRKTOKS (account group), XBILK (balance sheet account flag), TXT50 (description)
SKB1G/L Account Master (Company Code) — company code level settingsBUKRS + SAKNRWAERS (currency), XOPVW (open item management), XSALH (line item display)
SKATG/L Account Master Record Description (Text)SPRAS + KTOPL + SAKNRTXT20 (short text), TXT50 (long text)
T001Company Codes — master record for all company codesBUKRSBUTXT (company name), LAND1 (country), WAERS (currency), KTOPL (chart of accounts)
FAGLFLEXAGeneral Ledger: Actual Line Items (New GL, S/4HANA)RLDNR + RBUKRS + GJAHR + BELNR + DOCLNRACCT (account), HSL (amount in local currency), PRCTR (profit centre)

📊 SAP CO Tables List — Controlling

SAP Controlling (CO) handles internal cost accounting, cost centre management, profit centre accounting, internal orders, and profitability analysis. CO tables are tightly integrated with FI — every FI posting that carries a cost object creates a corresponding CO line item. The key CO tables are COSS and COSP for cost totals, COEP for line items, and CSKS for cost centre master data.

SAP CO — Cost Centre and Internal Order Tables
TableDescriptionKey FieldsImportant Fields
CSKSCost Centre Master Data — one row per cost centre per controlling areaKOKRS + KOSTL + DATBIKOSAR (cost centre category), VERAK (person responsible), ABTEI (department)
CSKTCost Centre Texts — descriptions in multiple languagesSPRAS + KOKRS + KOSTL + DATBIKTEXT (name), LTEXT (long text)
CSKACost Elements (Chart of Accounts) — primary and secondary cost elementsKTOPL + KSTARKTOKS (cost element group), KATYP (cost element category)
COEPCO Object: Line Items (by Period) — actual CO postingsKOKRS + BELNR + BUZEIKOSTL, KSTAR (cost element), WKGBTR (value in controlling area currency)
COSSCO Object: Cost Totals for Internal PostingsOBJNR + LEDNR + VERSN + GJAHR + KSTAR + VRGNGWKG001–WKG016 (period values 1–16)
COSPCO Object: Cost Totals for External PostingsOBJNR + LEDNR + VERSN + GJAHR + KSTAR + VRGNGWKG001–WKG016 (period values 1–16)
AUFKOrder Master Data — internal ordersAUFNRAUART (order type), BUKRS, KOSTV (responsible cost centre), OBJNR
PRPSWBS Element Master Data — project work breakdown structurePSPNRPOSID (WBS element ID), STUFE (level), PKOKR (controlling area)

SAP HR Tables List — Human Resources

SAP Human Resources (HR / HCM) uses a unique infotype-based data model that is very different from other SAP modules. Instead of individual tables for each data type, HR uses a standard set of tables (PA0001, PA0002, PA0006, etc.) where the number in the table name corresponds to the infotype number. Each infotype stores a specific category of employee data with time-based validity periods. This design allows SAP HR to maintain a complete historical record of all employee data changes over time.

SAP HR — Core Personnel Administration Tables (PA Infotypes)
TableInfotypeDescriptionKey Fields
PA0000IT 0000Actions — hiring, transfer, termination eventsPERNR + BEGDA + ENDDA + SUBTY
PA0001IT 0001Organisational Assignment — position, job, org unit, cost centrePERNR + BEGDA + ENDDA
PA0002IT 0002Personal Data — name, date of birth, nationality, genderPERNR + BEGDA + ENDDA
PA0006IT 0006Addresses — home address, emergency contact addressPERNR + BEGDA + ENDDA + SUBTY
PA0007IT 0007Planned Working Time — work schedule, part-time factorPERNR + BEGDA + ENDDA
PA0008IT 0008Basic Pay — pay grade, pay scale level, salary amountPERNR + BEGDA + ENDDA
PA0009IT 0009Bank Details — employee bank account for payroll paymentPERNR + BEGDA + ENDDA + SUBTY
PA0014IT 0014Recurring Payments and Deductions — allowances, deductionsPERNR + BEGDA + ENDDA + SUBTY + SEQNR
PA0105IT 0105Communication — SAP user ID, email address, phone numberPERNR + BEGDA + ENDDA + SUBTY
SAP HR — Organisational Management Tables
TableDescriptionKey FieldsImportant Fields
HRP1000Infotype 1000 — Object names for org units, positions, jobsPLVAR + OTYPE + OBJID + ISTAT + BEGDA + ENDDASTEXT (short text / name of the object)
HRP1001Infotype 1001 — Relationships between org objectsPLVAR + OTYPE + OBJID + RSIGN + RELAT + ISTAT + BEGDA + ENDDA + SUBTYSOBID (related object ID), OTYPE (object type: O=org unit, S=position, P=person)
T527XOrganisational Units — master recordWERKSName and administrative data for org units

🏭 SAP PP Tables List — Production Planning

SAP Production Planning (PP) manages the manufacturing process — from bills of materials and routings through to production orders, capacity planning, and goods issue/receipt. PP is tightly linked to MM (for material requirements and goods movements) and CO (for order cost settlement). The most critical PP tables are STKO and STPO for bills of materials, PLKO and PLPO for routings, and AUFK with AFKO for production orders.

SAP PP — Bill of Materials, Routing and Production Order Tables
TableDescriptionKey FieldsImportant Fields
STKOBOM Header — one row per bill of materialsSTLNR + STLALMATNR (parent material), WERKS, STLST (BOM status), DATUV (valid from)
STPOBOM Item — one row per component in the BOMSTLNR + STLKNIDNRK (component material), MENGE (quantity), MEINS, POSTP (item category)
MASTMaterial to BOM Link — links a material to its BOMMATNR + WERKS + STLANSTLNR (BOM number), STLAL (alternative), STLAN (BOM usage)
PLKORouting Header — task list header for work centres and operationsPLNTY + PLNNR + PLNALMATNR, WERKS, PLNST (status), DATUV (valid from)
PLPORouting Operation — one row per operation in the routingPLNTY + PLNNR + PLNAL + PLNFL + VORNRARBID (work centre), LTXA1 (operation text), VGW01–VGW06 (standard values)
AFKOProduction Order Header DataAUFNRMATNR, GAMNG (order qty), GSTRS (scheduled start), GLTRP (scheduled finish), FTRMI (actual finish)
AFPOProduction Order Item — components assigned to the production orderAUFNR + POSNRMATNR (component), BDMNG (required qty), ENTNR (reservation number)
CRHDWork Centre Header — master data for work centres and capacityOBJIDARBPL (work centre ID), WERKS, VERWE (usage), KAPID (capacity category)

SAP WM Tables List — Warehouse Management

SAP Warehouse Management (WM) manages the physical movement of goods within a warehouse — putaway, picking, transfer orders, and bin management. WM works below the MM inventory management layer, adding bin-level granularity to stock management. In S/4HANA, WM has been replaced by the new Extended Warehouse Management (EWM) module, but classic WM tables are still widely used in ECC systems.

SAP WM — Warehouse Management Tables
TableDescriptionKey FieldsImportant Fields
LGPLAStorage Bin — master record for each bin in the warehouseLGNUM + LGTYP + LGPLALPTYP (bin type), SKZUE (putaway blocked), SKZUA (removal blocked)
LGPLOStorage Bin — quant link (bin to stock quantity)LGNUM + LGTYP + LGPLALinks bins to their current stock quants
LQUAQuants — actual stock quantities at bin levelLGNUM + LQNUMMATNR, WERKS, LGTYP, LGPLA, VERME (available stock), EINME (restricted)
LTBKTransfer Order Header — warehouse movement instructionLGNUM + TANUMTBNUM (transfer order number), TRART (transfer order type), BDATU (date)
LTBPTransfer Order Item — line items of the transfer orderLGNUM + TANUM + TAPOSMATNR, WERKS, NLTYP (dest storage type), NLPLA (dest bin), ANFME (qty requested)
T300Warehouse Number Definition — master record for warehousesLGNUMLGBEZ (warehouse description), WERKS, LGORT

🔧 SAP PM and PS Tables List

SAP Plant Maintenance (PM) manages equipment, maintenance orders, and preventive maintenance plans for physical assets. SAP Project System (PS) handles project planning, budgeting, and execution using work breakdown structures (WBS elements) and networks. Both modules use the internal order framework (AUFK) as their core document type alongside module-specific master data tables.

SAP PM — Plant Maintenance Key Tables
TableDescriptionKey FieldsImportant Fields
EQUIEquipment Master Data — physical assets and machinesEQUNREQTYP (equipment category), MATNR, SERNR (serial number), GEWRK (work centre), INBDT (install date)
EQUZEquipment Usage Period — installation / removal historyEQUNR + DATBITPLNR (functional location), IEQUI (installation indicator), DATAB (valid from date)
IFLOTFunctional Location — hierarchical structure of plant locationsTPLNRTPLKZ (structure indicator), EQKLA (equipment category), ADRNR (address)
AUFKOrder Master Data — maintenance orders (also used in CO and PP)AUFNRAUART (order type), QMNUM (notification), TPLNR (functional location), EQUNR (equipment)
QMELQuality Notification / PM Notification HeaderQMNUMQMART (notification type), EQUNR, TPLNR, QMDAT (notification date), PRIOK (priority)
SAP PS — Project System Key Tables
TableDescriptionKey FieldsImportant Fields
PROJProject Definition — master record for each projectPSPIDPOST1 (project description), VERNR (project manager), PLFAZ (planned start), PLSEZ (planned finish)
PRPSWBS Element Master Data — work breakdown structure elementsPSPNRPOSID (WBS ID), STUFE (level), PKOKR (controlling area), PBUKR (company code)
PRTEProject: Date Segment of WBS Element — planned/actual datesPSPNRPLFAZ (planned start), PLSEZ (planned finish), ISTAT (system status)
NETZNetwork Header — project network (activity network)AUFNRPSPEL (WBS element), VERNR (person responsible), GSTRS (scheduled start)

SAP Configuration and Customising Tables

Beyond transactional tables, SAP contains hundreds of configuration tables (also called Customising tables or T-tables) that control system behaviour. These tables are maintained via the IMG (Implementation Guide) using transaction SPRO. Knowing these tables is essential for consultants who need to understand why the system behaves in a certain way or who need to transport configuration between systems.

SAP — Key Configuration T-Tables (Cross-Module)
TableDescriptionModule
T001Company Codes — all company code definitionsFI
T001WPlants / Branches — all plant definitionsMM
T001LStorage Locations — all storage locations per plantMM
TVKOSales Organisations — all sales org definitionsSD
TVTWDistribution Channels — all distribution channel definitionsSD
TVTASales Area — combination of sales org, dist channel, divisionSD
T023Material Groups — all material group definitionsMM
T134Material Types — all material type definitions (ROH, FERT, HALB, etc.)MM
TVAKSales Document Types — all sales order type definitions (OR, ZOR, etc.)SD
T003Document Types — FI document type definitions (SA, KR, DR, etc.)FI
T030Standard Account Determination — automatic account assignment keysFI
TCURRExchange Rates — currency exchange rate tableCross
TCURCCurrency Codes — all currency definitionsCross
T005Countries — all country master dataCross
T005SRegions — region / state definitions per countryCross

🔎 How to Find Any SAP Table You Need

Even with this comprehensive SAP All Tables List, there will be times when you need to find a table that is not covered here. SAP provides several built-in techniques to discover any table in the system without relying on documentation.

Method 1 — F1 Technical Information

The fastest method. In any SAP transaction, place your cursor on any field on screen and press F1. In the help popup, click the Technical Information button (or press F9). SAP will display the exact table name and field name that stores the data shown on screen. This works in every standard SAP transaction and is 100% reliable.

Method 2 — SE11 Wildcard Search

Open SE11 and enter a partial table name with a wildcard. For example, entering VB* will list all SD document tables. Entering BKPF* or *VENDOR* helps narrow down tables by name. Use the Where-Used List to find tables that reference a specific field or domain.

Method 3 — SE84 Repository Information System

SE84 is the SAP Repository Information System — a powerful search tool that allows you to search for tables by description keyword, by field name, by data element, or by table type. It is the most comprehensive search tool for finding tables when you know what data you need but not the exact table name.

ABAP — Find tables containing a specific field
"Use SE84 or this ABAP snippet to find tables with a specific field
SELECT tabname, fieldname, ddtext
  FROM dd03vv
  INTO TABLE @lt_fields
  WHERE fieldname = 'MATNR'
    AND   tabclass  = 'TRANSP'
  ORDER BY tabname.

Method 4 — Check the Where-Used List in SE11

In SE11, once you have a table open, use the Where-Used List (Ctrl+Shift+F3) to find every ABAP program, function module, and other database object that reads or writes to that table. This is invaluable for understanding the full business context of any table and discovering related tables used in the same programs.

Golden Rule for SAP Tables: Never hard-code a table name in an ABAP report without first checking its delivery class in SE11. Tables with delivery class C (Customising) should only be read — never changed by custom programs. Tables with delivery class A (Application) are transactional data tables safe to read with SELECT statements.

📋 SAP All Tables List — Master Quick Reference

The table below is your single-page quick reference covering the most important tables from every major SAP module. Bookmark this page and use it whenever you need to quickly identify which table stores the data you are looking for.

SAP All Tables — Master Quick Reference by Module
TableModuleDescriptionPrimary Key(s)
MARAMMGeneral Material DataMATNR
MARCMMPlant Data for MaterialMATNR + WERKS
MARDMMStorage Location Stock DataMATNR + WERKS + LGORT
MAKTMMMaterial DescriptionsMATNR + SPRAS
MBEWMMMaterial ValuationMATNR + BWKEY
EKKOMMPurchasing Document HeaderEBELN
EKPOMMPurchasing Document ItemEBELN + EBELP
EKBEMMPurchasing Document History (GR/IR)EBELN + EBELP + VGABE + ...
EBANMMPurchase RequisitionBANFN + BNFPO
MKPFMMMaterial Document HeaderMBLNR + MJAHR
MSEGMMMaterial Document Line ItemsMBLNR + MJAHR + ZEILE
LFA1MM/FIVendor Master — General DataLIFNR
LFB1MM/FIVendor Master — Company Code DataLIFNR + BUKRS
KNA1SD/FICustomer Master — General DataKUNNR
KNB1SD/FICustomer Master — Company Code DataKUNNR + BUKRS
KNVVSDCustomer Master — Sales Area DataKUNNR + VKORG + VTWEG + SPART
VBAKSDSales Document HeaderVBELN
VBAPSDSales Document ItemVBELN + POSNR
VBEPSDSales Schedule LinesVBELN + POSNR + ETENR
VBFASDSales Document FlowVBELV + POSNV + VBELN + POSNN
LIKPSDDelivery HeaderVBELN
LIPSSDDelivery ItemVBELN + POSNR
VBRKSDBilling Document HeaderVBELN
VBRPSDBilling Document ItemVBELN + POSNR
BKPFFIAccounting Document HeaderBUKRS + BELNR + GJAHR
BSEGFIAccounting Document Line ItemsBUKRS + BELNR + GJAHR + BUZEI
BSISFIG/L Open ItemsBUKRS + HKONT + GJAHR + BELNR + BUZEI
BSIDFICustomer Open Items (AR)BUKRS + KUNNR + GJAHR + BELNR + BUZEI
BSIKFIVendor Open Items (AP)BUKRS + LIFNR + GJAHR + BELNR + BUZEI
SKA1FIG/L Account Master (Chart of Accounts)KTOPL + SAKNR
T001FICompany CodesBUKRS
CSKSCOCost Centre MasterKOKRS + KOSTL + DATBI
COEPCOCO Actual Line ItemsKOKRS + BELNR + BUZEI
AUFKCO/PP/PMOrder Master DataAUFNR
PA0001HREmployee Org AssignmentPERNR + BEGDA + ENDDA
PA0002HREmployee Personal DataPERNR + BEGDA + ENDDA
PA0008HREmployee Basic PayPERNR + BEGDA + ENDDA
HRP1000HROrg Object NamesPLVAR + OTYPE + OBJID + BEGDA + ENDDA
STKOPPBOM HeaderSTLNR + STLAL
STPOPPBOM ItemSTLNR + STLKN
AFKOPPProduction Order HeaderAUFNR
LQUAWMWarehouse Quants (bin stock)LGNUM + LQNUM
EQUIPMEquipment MasterEQUNR
PRPSPSWBS Element MasterPSPNR

📘 Related SAP Tutorials

SAP ABAP

SAP Table Relationships

How SAP tables are connected using primary keys, foreign keys and joins.

Read Tutorial
SAP MM

SAP MM Configuration

Complete MM configuration guide covering procurement cycle and system settings.

Read Tutorial
SAP FICO

SAP FICO Training 2026

Career paths, certification guide, and hands-on FICO module training.

Read Tutorial