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.
"Example: Select all records from MARA for a specific material SELECT * FROM mara INTO TABLE @lt_mara WHERE matnr = @lv_matnr.
📦 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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| MARA | General Material Data — valid across all organisational levels | MATNR | MTART (type), MATKL (group), MEINS (base UOM), BRGEW (weight) |
| MARC | Plant Data for Material — plant-specific settings | MATNR + WERKS | DISMM (MRP type), DZEIT (in-house production time), MINBE (reorder point) |
| MARD | Storage Location Stock Data stock per storage location | MATNR + WERKS + LGORT | LABST (unrestricted stock), EINME (restricted stock), SPEME (blocked stock) |
| MAKT | Material Descriptions — text in multiple languages | MATNR + SPRAS | MAKTX (short text), MAKTG (upper case text) |
| MARM | Units of Measure for Material — alternate UOM | MATNR + MEINH | UMREZ (numerator), UMREN (denominator), BRGEW (gross weight per UOM) |
| MVKE | Material Data for Sales Organisation | MATNR + VKORG + VTWEG | MTPOS (item category group), KONDM (material pricing group) |
| MBEW | Material Valuation — price and value data per plant | MATNR + BWKEY | VERPR (moving average price), STPRS (standard price), LBKUM (total valuated stock) |
| MLAN | Tax Classification of Material | MATNR + ALAND | TAXM1 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).
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| EKKO | Purchasing Document Header — PO, contract, scheduling agreement | EBELN | BSART (doc type), LIFNR (vendor), EKGRP (purchasing group), BEDAT (PO date) |
| EKPO | Purchasing Document Item — line items of all PO types | EBELN + EBELP | MATNR (material), MENGE (quantity), NETPR (net price), WERKS (plant), LGORT (storage loc) |
| EKKN | Account Assignment in Purchasing — cost centre / GL assignment per PO item | EBELN + EBELP + ZEKKN | KOSTL (cost centre), SAKTO (G/L account), AUFNR (order) |
| EKET | Scheduling Agreement Schedule Lines | EBELN + EBELP + ETENR | EINDT (delivery date), MENGE (scheduled qty), WEMNG (goods receipt qty) |
| EBAN | Purchase Requisition — header and item combined | BANFN + BNFPO | MATNR, MENGE, WERKS, AFNAM (requisitioner), EKGRP, BADAT (creation date) |
| EKBE | History per Purchasing Document — GR and IR history per PO item | EBELN + EBELP + VGABE + GJAHR + BELNR + BUZEI | VGABE (transaction type), MENGE (qty), DMBTR (amount in local currency) |
| LFA1 | Vendor Master — General Data | LIFNR | NAME1 (name), LAND1 (country), ORT01 (city), SPRAS (language) |
| LFB1 | Vendor Master — Company Code Data | LIFNR + BUKRS | AKONT (reconciliation account), ZTERM (payment terms), ZWELS (payment methods) |
Inventory Management Tables (MM-IM)
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| MKPF | Header: Material Document — goods movement header | MBLNR + MJAHR | BLDAT (document date), BUDAT (posting date), USNAM (user), TCODE |
| MSEG | Document Segment: Material — goods movement line items | MBLNR + MJAHR + ZEILE | MATNR, WERKS, LGORT, BWART (movement type), MENGE, DMBTR (value) |
| MCHB | Batch Stocks — stock per batch per storage location | MATNR + WERKS + LGORT + CHARG | CLABS (unrestricted), CEINM (restricted use), CSPEM (blocked stock) |
| MCH1 | Batches (if batch management active) — master record per batch | MATNR + CHARG | ZUSTD (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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| KNA1 | Customer Master — General Data (valid across company codes) | KUNNR | NAME1, LAND1 (country), ORT01 (city), SPRAS, ADRNR (address number) |
| KNB1 | Customer Master — Company Code Data | KUNNR + BUKRS | AKONT (reconciliation account), ZTERM (payment terms), ZWELS (payment method) |
| KNVV | Customer Master — Sales Area Data | KUNNR + VKORG + VTWEG + SPART | KDGRP (customer group), KONDA (price group), BZIRK (sales district), VKBUR (sales office) |
| KNVP | Customer Master — Partner Functions | KUNNR + VKORG + VTWEG + SPART + PARVW + PARZA | KUNN2 (partner number), PARVW (partner function: SP, SH, BP, PY) |
| ADRC | Addresses — centralised address storage for all business partners | ADDRNUMBER + DATE_FROM | NAME1, STREET, CITY1, POST_CODE1, COUNTRY, REGION |
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| VBAK | Sales Document: Header Data — one row per sales order/quotation/contract | VBELN | AUART (order type), KUNNR (sold-to), VKORG (sales org), AUDAT (order date), NETWR (net value) |
| VBAP | Sales Document: Item Data — one row per line item | VBELN + POSNR | MATNR, KWMENG (order qty), NETPR (net price), WERKS, LGORT, PSTYV (item category) |
| VBEP | Sales Document: Schedule Line Data — delivery dates and quantities | VBELN + POSNR + ETENR | EDATU (delivery date), WMENG (confirmed qty), BMENG (assessed qty) |
| VBPA | Sales Document: Partner — all partners per document (sold-to, ship-to, etc.) | VBELN + POSNR + PARVW | KUNNR (partner number), PARVW (partner function) |
| VBUK | Sales Document: Header Status and Administrative Data | VBELN | GBSTK (overall status), LFSTK (delivery status), FKSTK (billing status) |
| VBUP | Sales Document: Item Status | VBELN + POSNR | GBSTA (overall item status), LFSTA (delivery status), FKSTA (billing status) |
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| LIKP | SD Document: Delivery Header Data | VBELN | KUNNR (ship-to), LFART (delivery type), WADAT (planned GI date), VSTEL (shipping point) |
| LIPS | SD Document: Delivery Item Data | VBELN + POSNR | MATNR, LGMNG (delivery qty), WERKS, LGORT, VGBEL (ref sales order number) |
| VBRK | Billing Document: Header Data | VBELN | FKART (billing type), KUNRG (payer), FKDAT (billing date), NETWR (net value), WAERK (currency) |
| VBRP | Billing Document: Item Data | VBELN + POSNR | MATNR, FKIMG (billed qty), NETWR (net value), AUBEL (ref sales order), VGBEL (ref delivery) |
| VBFA | Sales Document Flow — links all SD documents in the order-to-cash chain | VBELV + POSNV + VBELN + POSNN + VBTYP_N | VBTYP_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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| BKPF | Accounting Document Header — one row per financial document | BUKRS + BELNR + GJAHR | BLART (doc type), BUDAT (posting date), BLDAT (doc date), USNAM (user), WAERS (currency) |
| BSEG | Accounting Document Segment — line items (cluster table, read via BSIS/BSAS) | BUKRS + BELNR + GJAHR + BUZEI | HKONT (G/L account), DMBTR (amount), SHKZG (Dr/Cr indicator), KOSTL, KUNNR, LIFNR |
| BSIS | Accounting: Secondary Index for G/L Accounts (Open Items) | BUKRS + HKONT + GJAHR + BELNR + BUZEI | DMBTR (amount), BUDAT, AUGDT (clearing date — blank if open) |
| BSAS | Accounting: Secondary Index for G/L Accounts (Cleared Items) | BUKRS + HKONT + GJAHR + BELNR + BUZEI | DMBTR, BUDAT, AUGDT (clearing date — filled when cleared) |
| BSID | Accounting: Secondary Index for Customers (Open Items) | BUKRS + KUNNR + GJAHR + BELNR + BUZEI | DMBTR, BUDAT, ZFBDT (baseline date), ZTERM (payment terms) |
| BSAD | Accounting: Secondary Index for Customers (Cleared Items) | BUKRS + KUNNR + GJAHR + BELNR + BUZEI | DMBTR, AUGDT (clearing date), AUGBL (clearing document) |
| BSIK | Accounting: Secondary Index for Vendors (Open Items) | BUKRS + LIFNR + GJAHR + BELNR + BUZEI | DMBTR, BUDAT, ZFBDT, ZTERM |
| BSAK | Accounting: Secondary Index for Vendors (Cleared Items) | BUKRS + LIFNR + GJAHR + BELNR + BUZEI | DMBTR, AUGDT, AUGBL |
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| SKA1 | G/L Account Master (Chart of Accounts) — chart level data | KTOPL + SAKNR | KTOKS (account group), XBILK (balance sheet account flag), TXT50 (description) |
| SKB1 | G/L Account Master (Company Code) — company code level settings | BUKRS + SAKNR | WAERS (currency), XOPVW (open item management), XSALH (line item display) |
| SKAT | G/L Account Master Record Description (Text) | SPRAS + KTOPL + SAKNR | TXT20 (short text), TXT50 (long text) |
| T001 | Company Codes — master record for all company codes | BUKRS | BUTXT (company name), LAND1 (country), WAERS (currency), KTOPL (chart of accounts) |
| FAGLFLEXA | General Ledger: Actual Line Items (New GL, S/4HANA) | RLDNR + RBUKRS + GJAHR + BELNR + DOCLN | RACCT (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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| CSKS | Cost Centre Master Data — one row per cost centre per controlling area | KOKRS + KOSTL + DATBI | KOSAR (cost centre category), VERAK (person responsible), ABTEI (department) |
| CSKT | Cost Centre Texts — descriptions in multiple languages | SPRAS + KOKRS + KOSTL + DATBI | KTEXT (name), LTEXT (long text) |
| CSKA | Cost Elements (Chart of Accounts) — primary and secondary cost elements | KTOPL + KSTAR | KTOKS (cost element group), KATYP (cost element category) |
| COEP | CO Object: Line Items (by Period) — actual CO postings | KOKRS + BELNR + BUZEI | KOSTL, KSTAR (cost element), WKGBTR (value in controlling area currency) |
| COSS | CO Object: Cost Totals for Internal Postings | OBJNR + LEDNR + VERSN + GJAHR + KSTAR + VRGNG | WKG001–WKG016 (period values 1–16) |
| COSP | CO Object: Cost Totals for External Postings | OBJNR + LEDNR + VERSN + GJAHR + KSTAR + VRGNG | WKG001–WKG016 (period values 1–16) |
| AUFK | Order Master Data — internal orders | AUFNR | AUART (order type), BUKRS, KOSTV (responsible cost centre), OBJNR |
| PRPS | WBS Element Master Data — project work breakdown structure | PSPNR | POSID (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.
| Table | Infotype | Description | Key Fields |
|---|---|---|---|
| PA0000 | IT 0000 | Actions — hiring, transfer, termination events | PERNR + BEGDA + ENDDA + SUBTY |
| PA0001 | IT 0001 | Organisational Assignment — position, job, org unit, cost centre | PERNR + BEGDA + ENDDA |
| PA0002 | IT 0002 | Personal Data — name, date of birth, nationality, gender | PERNR + BEGDA + ENDDA |
| PA0006 | IT 0006 | Addresses — home address, emergency contact address | PERNR + BEGDA + ENDDA + SUBTY |
| PA0007 | IT 0007 | Planned Working Time — work schedule, part-time factor | PERNR + BEGDA + ENDDA |
| PA0008 | IT 0008 | Basic Pay — pay grade, pay scale level, salary amount | PERNR + BEGDA + ENDDA |
| PA0009 | IT 0009 | Bank Details — employee bank account for payroll payment | PERNR + BEGDA + ENDDA + SUBTY |
| PA0014 | IT 0014 | Recurring Payments and Deductions — allowances, deductions | PERNR + BEGDA + ENDDA + SUBTY + SEQNR |
| PA0105 | IT 0105 | Communication — SAP user ID, email address, phone number | PERNR + BEGDA + ENDDA + SUBTY |
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| HRP1000 | Infotype 1000 — Object names for org units, positions, jobs | PLVAR + OTYPE + OBJID + ISTAT + BEGDA + ENDDA | STEXT (short text / name of the object) |
| HRP1001 | Infotype 1001 — Relationships between org objects | PLVAR + OTYPE + OBJID + RSIGN + RELAT + ISTAT + BEGDA + ENDDA + SUBTY | SOBID (related object ID), OTYPE (object type: O=org unit, S=position, P=person) |
| T527X | Organisational Units — master record | WERKS | Name 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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| STKO | BOM Header — one row per bill of materials | STLNR + STLAL | MATNR (parent material), WERKS, STLST (BOM status), DATUV (valid from) |
| STPO | BOM Item — one row per component in the BOM | STLNR + STLKN | IDNRK (component material), MENGE (quantity), MEINS, POSTP (item category) |
| MAST | Material to BOM Link — links a material to its BOM | MATNR + WERKS + STLAN | STLNR (BOM number), STLAL (alternative), STLAN (BOM usage) |
| PLKO | Routing Header — task list header for work centres and operations | PLNTY + PLNNR + PLNAL | MATNR, WERKS, PLNST (status), DATUV (valid from) |
| PLPO | Routing Operation — one row per operation in the routing | PLNTY + PLNNR + PLNAL + PLNFL + VORNR | ARBID (work centre), LTXA1 (operation text), VGW01–VGW06 (standard values) |
| AFKO | Production Order Header Data | AUFNR | MATNR, GAMNG (order qty), GSTRS (scheduled start), GLTRP (scheduled finish), FTRMI (actual finish) |
| AFPO | Production Order Item — components assigned to the production order | AUFNR + POSNR | MATNR (component), BDMNG (required qty), ENTNR (reservation number) |
| CRHD | Work Centre Header — master data for work centres and capacity | OBJID | ARBPL (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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| LGPLA | Storage Bin — master record for each bin in the warehouse | LGNUM + LGTYP + LGPLA | LPTYP (bin type), SKZUE (putaway blocked), SKZUA (removal blocked) |
| LGPLO | Storage Bin — quant link (bin to stock quantity) | LGNUM + LGTYP + LGPLA | Links bins to their current stock quants |
| LQUA | Quants — actual stock quantities at bin level | LGNUM + LQNUM | MATNR, WERKS, LGTYP, LGPLA, VERME (available stock), EINME (restricted) |
| LTBK | Transfer Order Header — warehouse movement instruction | LGNUM + TANUM | TBNUM (transfer order number), TRART (transfer order type), BDATU (date) |
| LTBP | Transfer Order Item — line items of the transfer order | LGNUM + TANUM + TAPOS | MATNR, WERKS, NLTYP (dest storage type), NLPLA (dest bin), ANFME (qty requested) |
| T300 | Warehouse Number Definition — master record for warehouses | LGNUM | LGBEZ (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.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| EQUI | Equipment Master Data — physical assets and machines | EQUNR | EQTYP (equipment category), MATNR, SERNR (serial number), GEWRK (work centre), INBDT (install date) |
| EQUZ | Equipment Usage Period — installation / removal history | EQUNR + DATBI | TPLNR (functional location), IEQUI (installation indicator), DATAB (valid from date) |
| IFLOT | Functional Location — hierarchical structure of plant locations | TPLNR | TPLKZ (structure indicator), EQKLA (equipment category), ADRNR (address) |
| AUFK | Order Master Data — maintenance orders (also used in CO and PP) | AUFNR | AUART (order type), QMNUM (notification), TPLNR (functional location), EQUNR (equipment) |
| QMEL | Quality Notification / PM Notification Header | QMNUM | QMART (notification type), EQUNR, TPLNR, QMDAT (notification date), PRIOK (priority) |
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| PROJ | Project Definition — master record for each project | PSPID | POST1 (project description), VERNR (project manager), PLFAZ (planned start), PLSEZ (planned finish) |
| PRPS | WBS Element Master Data — work breakdown structure elements | PSPNR | POSID (WBS ID), STUFE (level), PKOKR (controlling area), PBUKR (company code) |
| PRTE | Project: Date Segment of WBS Element — planned/actual dates | PSPNR | PLFAZ (planned start), PLSEZ (planned finish), ISTAT (system status) |
| NETZ | Network Header — project network (activity network) | AUFNR | PSPEL (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.
| Table | Description | Module |
|---|---|---|
| T001 | Company Codes — all company code definitions | FI |
| T001W | Plants / Branches — all plant definitions | MM |
| T001L | Storage Locations — all storage locations per plant | MM |
| TVKO | Sales Organisations — all sales org definitions | SD |
| TVTW | Distribution Channels — all distribution channel definitions | SD |
| TVTA | Sales Area — combination of sales org, dist channel, division | SD |
| T023 | Material Groups — all material group definitions | MM |
| T134 | Material Types — all material type definitions (ROH, FERT, HALB, etc.) | MM |
| TVAK | Sales Document Types — all sales order type definitions (OR, ZOR, etc.) | SD |
| T003 | Document Types — FI document type definitions (SA, KR, DR, etc.) | FI |
| T030 | Standard Account Determination — automatic account assignment keys | FI |
| TCURR | Exchange Rates — currency exchange rate table | Cross |
| TCURC | Currency Codes — all currency definitions | Cross |
| T005 | Countries — all country master data | Cross |
| T005S | Regions — region / state definitions per country | Cross |
🔎 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.
"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.
| Table | Module | Description | Primary Key(s) |
|---|---|---|---|
| MARA | MM | General Material Data | MATNR |
| MARC | MM | Plant Data for Material | MATNR + WERKS |
| MARD | MM | Storage Location Stock Data | MATNR + WERKS + LGORT |
| MAKT | MM | Material Descriptions | MATNR + SPRAS |
| MBEW | MM | Material Valuation | MATNR + BWKEY |
| EKKO | MM | Purchasing Document Header | EBELN |
| EKPO | MM | Purchasing Document Item | EBELN + EBELP |
| EKBE | MM | Purchasing Document History (GR/IR) | EBELN + EBELP + VGABE + ... |
| EBAN | MM | Purchase Requisition | BANFN + BNFPO |
| MKPF | MM | Material Document Header | MBLNR + MJAHR |
| MSEG | MM | Material Document Line Items | MBLNR + MJAHR + ZEILE |
| LFA1 | MM/FI | Vendor Master — General Data | LIFNR |
| LFB1 | MM/FI | Vendor Master — Company Code Data | LIFNR + BUKRS |
| KNA1 | SD/FI | Customer Master — General Data | KUNNR |
| KNB1 | SD/FI | Customer Master — Company Code Data | KUNNR + BUKRS |
| KNVV | SD | Customer Master — Sales Area Data | KUNNR + VKORG + VTWEG + SPART |
| VBAK | SD | Sales Document Header | VBELN |
| VBAP | SD | Sales Document Item | VBELN + POSNR |
| VBEP | SD | Sales Schedule Lines | VBELN + POSNR + ETENR |
| VBFA | SD | Sales Document Flow | VBELV + POSNV + VBELN + POSNN |
| LIKP | SD | Delivery Header | VBELN |
| LIPS | SD | Delivery Item | VBELN + POSNR |
| VBRK | SD | Billing Document Header | VBELN |
| VBRP | SD | Billing Document Item | VBELN + POSNR |
| BKPF | FI | Accounting Document Header | BUKRS + BELNR + GJAHR |
| BSEG | FI | Accounting Document Line Items | BUKRS + BELNR + GJAHR + BUZEI |
| BSIS | FI | G/L Open Items | BUKRS + HKONT + GJAHR + BELNR + BUZEI |
| BSID | FI | Customer Open Items (AR) | BUKRS + KUNNR + GJAHR + BELNR + BUZEI |
| BSIK | FI | Vendor Open Items (AP) | BUKRS + LIFNR + GJAHR + BELNR + BUZEI |
| SKA1 | FI | G/L Account Master (Chart of Accounts) | KTOPL + SAKNR |
| T001 | FI | Company Codes | BUKRS |
| CSKS | CO | Cost Centre Master | KOKRS + KOSTL + DATBI |
| COEP | CO | CO Actual Line Items | KOKRS + BELNR + BUZEI |
| AUFK | CO/PP/PM | Order Master Data | AUFNR |
| PA0001 | HR | Employee Org Assignment | PERNR + BEGDA + ENDDA |
| PA0002 | HR | Employee Personal Data | PERNR + BEGDA + ENDDA |
| PA0008 | HR | Employee Basic Pay | PERNR + BEGDA + ENDDA |
| HRP1000 | HR | Org Object Names | PLVAR + OTYPE + OBJID + BEGDA + ENDDA |
| STKO | PP | BOM Header | STLNR + STLAL |
| STPO | PP | BOM Item | STLNR + STLKN |
| AFKO | PP | Production Order Header | AUFNR |
| LQUA | WM | Warehouse Quants (bin stock) | LGNUM + LQNUM |
| EQUI | PM | Equipment Master | EQUNR |
| PRPS | PS | WBS Element Master | PSPNR |
📘 Related SAP Tutorials
SAP Table Relationships
How SAP tables are connected using primary keys, foreign keys and joins.
Read TutorialSAP MM Configuration
Complete MM configuration guide covering procurement cycle and system settings.
Read TutorialSAP FICO Training 2026
Career paths, certification guide, and hands-on FICO module training.
Read Tutorial