SAP Tables hub
SAP stores all its data in database tables, and knowing the key ones, their fields and relationships, is essential for reporting, development and troubleshooting. This hub lists the most important tables; each page details structure, fields, keys and related tables.
SAP tables follow patterns: master data in MARA, KNA1 and LFA1, documents as header and item pairs in VBAK and VBAP, EKKO and EKPO, BKPF and BSEG, linked by a key such as VBELN. SE11 shows a table's structure, keys and indexes and SE16N its contents. Each table page here gives what it stores, key fields, relationships and related tables.
- Watch out: Reading raw tables where a CDS view/report is better.
Why tables matter
Understanding tables lets you report, write CDS/SQL, and debug ("which table holds this field?"). SAP tables follow patterns, master data (MARA material, KNA1 customer, LFA1 vendor) and documents in header/item pairs (VBAK/VBAP sales, EKKO/EKPO purchasing, BKPF/BSEG finance). Table references are among the most-searched SAP topics.
Exploring tables
- SE11: view a table’s structure, fields, keys, indexes.
- SE16N: browse table contents (with authorization).
- Header/item patterns link related tables via a key (e.g. VBELN).
- CDS views increasingly provide a modeled layer over raw tables.
Using this module
Each table page gives what it stores, key fields, keys/relationships, and related tables, the reference practitioners look up constantly. In S/4HANA, note that some classic tables are now CDS views/compatibility views over a simplified model (e.g. finance in ACDOCA).
Common pitfalls
- Reading raw tables where a CDS view/report is better.
- Ignoring header/item relationships.
- Querying big tables without indexed selection.