SAP Reference
SAP Reference Database
The table names everyone learned in ECC survive in S/4HANA, but what several of them store has moved: BSEG now backs onto ACDOCA, MKPF reads through a compatibility view over MATDOC, and every table here carries its S/4HANA status. A searchable reference for analysts and data engineers modeling SAP sources in Databricks, Snowflake, or any analytics platform.
Free & ungated · Last verified October 2026
- Tables
- 159
- T-Codes
- 92
- Modules
- 11
- CDS Views
- 23
The traps that survive a successful extract
Getting rows out of SAP is only the first gate. The quirks guide covers the source semantics that make plausible lakehouse models fail reconciliation: tenant keys, padded identifiers, initial values, language grain, units, composite document keys, and the S/4HANA split between readable names and physical persistence.
Read all 8 quirksHow this is scoped
- Scope: core supply chain and financial modules — MM, PP, SD, EWM plus classic WM, QM, FI, CO, APO, LE, plus cross-module org tables. Not a complete SAP Data Dictionary (yet).
- Feeds: the business-problem grid draws on this reference for Inventory & Working Capital, Demand Planning & Forecasting, Customer Service & Fulfillment, Procurement & Supply and Manufacturing & Production.
- S/4HANA awareness: every table and t-code carries an S/4HANA lifecycle tag — active, deprecated, replaced, or migrating to IBP — and tables whose classic name still answers reads carry a second tag for the mechanism (compatibility view or NSDM proxy view). Module-level tags flag broader shifts: APO moving toward IBP and embedded PP/DS depending on planning capability, and classic WM moving toward EWM (embedded or decentralized) or SAP Stock Room Management, depending on warehouse complexity. Classic WM objects that stay live under SAP Stock Room Management (opens in new tab) carry a path-dependent tag — active with Stock Room Management, replaced where EWM is the path — rather than a single unconditional status. Released CDS views are cataloged alongside the classic tables they read over.
- Field data: key fields are populated for every table; secondary fields for the highest-traffic tables. Table and field metadata is cross-checked against SAP Help (opens in new tab) and the community SAP object repositories at SAP-Tables (opens in new tab) / SAP Datasheet (opens in new tab) — affiliated properties of one operator, counted as a single independent source, and snapshotted from ECC-era DDIC (their published field data is ~2013–2014). S/4HANA-era objects and fields are verified against SAP Help and SAP’s released-API data instead. Every field record carries its provenance, shown beneath each table’s field listing; see the full sources list below. Last verified October 2026.
- Built for analytics: relationships are focused on the joins you’ll actually write — header/item pairs, foreign keys, and the cross-module keys (MATNR, EBELN, VBELN, BUKRS) that stitch SAP data together.
Frequently Referenced Tables
The workhorses of SAP analytics — material master, sales orders, purchase orders, accounting.
Material master
Inventory movements
Sales & delivery
Frequently Used T-Codes
Display and reporting t-codes analysts use to validate SAP data, reverse-engineer schemas, and reconcile reports against the source system.
- MM03Display Material
- MMBEStock Overview
- MB51Material Document List
- MIGOGoods Movement
- ME23NDisplay Purchase Order
- MD04Display Stock/Requirements List
- COOISProduction Order Information System
- VA03Display Sales Order
- VL03NDisplay Outbound Delivery
- FB03Display Document
- FBL1NVendor Line Item Display
- KSB1Cost Centers: Actual Line Items
Getting SAP into your lakehouse
The extraction guide covers the paths that matter in 2026 — Business Data Cloud’s zero-copy sharing into Databricks, Datasphere premium outbound, what SAP Note 3255746 did to the ODP connectors, the table-level CDC tools that still work, and the MERGE patterns that land it all correctly in bronze.
Read the extraction guideBrowse by Module
Organized by SAP functional area. Click a module to see its tables and transaction codes.
- APOAdvanced Planning & OptimizationDemand planning, supply network planning, PP/DS, and global ATP10 tables · 0 t-codes→ IBP
- COControllingCost center accounting, profit center accounting, internal orders, and profitability analysis7 tables · 5 t-codesUniversal Journal (ACDOCA)
- EWMExtended Warehouse ManagementAdvanced warehouse management with wave management, labor management, and yard management15 tables · 0 t-codes
- FIFinancial AccountingGeneral ledger, accounts payable/receivable, asset accounting, and bank accounting10 tables · 9 t-codesUniversal Journal (ACDOCA)
- LELogistics ExecutionShipping, transportation, and handling unit management7 tables · 1 t-codes
- MMMaterials ManagementCovers procurement, inventory management, invoice verification, and material master data29 tables · 32 t-codes
- ORGOrganizational StructureCompany codes, plants, storage locations, sales orgs, purchasing orgs12 tables · 0 t-codes
- PPProduction PlanningCovers demand management, MRP, production orders, capacity planning, and shop floor control24 tables · 17 t-codes
- QMQuality ManagementCovers quality planning, inspection, control, certificates, and notifications19 tables · 9 t-codes
- SDSales & DistributionCovers sales orders, deliveries, billing, pricing, and customer master data16 tables · 14 t-codes
- WMWarehouse Management (Classic)Classic warehouse management for storage bin management, transfer orders, and physical inventory. In S/4HANA classic LE-WM has two supported paths: SAP EWM (embedded or decentralized), or SAP Stock Room Management, which continues the core storage-bin, quant, and transfer-order capability on the same tables for simpler warehouses10 tables · 5 t-codes→ EWM / Stock Room Mgmt
Sources & further reading
S/4HANA status, simplification semantics, and Fiori mappings are authoritative only at source. Use these references to verify before building on any claim in this reference — plus one research-data group, flagged as such, that is not a verification source.
Show all 17 sources, graded by group
SAP official
- SAP Help Portal (opens in new tab) — authoritative S/4HANA simplification, Universal Journal, NSDM, Business Partner/CVI, and CDS documentation.
- SAP View Browser — released CDS views (S/4HANA Cloud) (opens in new tab) — the canonical lookup for which CDS views are released in a given S/4HANA Cloud release. Only Released-status views are safe to build on.
- SAP Business Accelerator Hub — CDS views (opens in new tab) — the Hub's CDS-view catalog, browsable by package and line of business with per-view release status. The first stop when replacing classic-table reads with released CDS views.
- SAP Cloudification Repository (opens in new tab) — SAP-official, machine-readable JSON/CSV lists of released and classic APIs with successor objects for Cloud ERP — the bulk-export counterpart to the View Browser.
- SAP Fiori Apps Reference Library (opens in new tab) — classic-to-Fiori transaction mapping and S/4HANA release availability; requires a free SAP Universal ID, S-user, or P-user sign-in to browse.
- SAP Simplification Item Catalog (opens in new tab) — SAP's authoritative per-release list of simplification items: the primary lookup for why a table carries its S/4HANA status here. Requires an SAP S-user sign-in to browse.
- SAP Samples (GitHub) (opens in new tab) — official sample repos for ABAP CDS, CAP/RAP, S/4HANA extensions, Fiori Elements, and clean-core patterns.
Community references
- sap-tables.org (opens in new tab) — community SAP table and field reference, useful for spot-checking classic DDIC objects. Affiliated with sapdatasheet.org and sap-tcodes.org; treat all three as one community source, not three independent checks.
- sapdatasheet.org (opens in new tab) — deep-linkable SAP object repository (tables, data elements, search helps, T-codes) for ECC-era schemas. Same operator as sap-tables.org and sap-tcodes.org.
- sap-tcodes.org (opens in new tab) — transaction code descriptions and module/component analytics. Same operator as sap-tables.org and sapdatasheet.org.
Databricks integration
- SAP Databricks documentation (opens in new tab) — Business Data Cloud integration, SAP data products, and Delta Sharing with SAP.
- SAP Architecture Center — BDC ↔ Databricks integration (opens in new tab) — SAP-authored reference architecture for exploring hyperscaler data with SAP Business Data Cloud, with Databricks among the covered platforms. The SAP-side view of the Databricks docs above.
- SAP Architecture Center — Integration with Databricks (opens in new tab) — SAP-authored reference architecture covering Business Data Cloud sharing with Databricks and federated access from SAP Datasphere to Databricks data.
- SAP Architecture Center — SAP Databricks in SAP BDC (opens in new tab) — SAP-authored reference architecture for the embedded SAP Databricks component inside Business Data Cloud and BDC Connect to an existing Databricks platform, both over Delta Sharing.
- SAP Business Data Cloud Catalog (opens in new tab) — official index of concrete BDC data packages and products. Pairs the integration pattern and mechanics above with what is actually available to activate.
Research data (not production metadata)
- SAP SALT (GitHub) (opens in new tab) — SAP-published research dataset of real, linked ERP tables (sales documents and master data) for machine-learning research. Not an authoritative DDIC source and not used to verify this reference; licensed CC-BY-NC-SA-4.0 (noncommercial).
- SAP SALT dataset (Hugging Face) (opens in new tab) — the dataset files themselves; downloading requires a free Hugging Face login. Same noncommercial CC-BY-NC-SA-4.0 license.