SAP MM Tables 2026:
Complete Database Reference for S/4HANA

The most important SAP MM tables are: EKKO (purchasing document header), EKPO (purchasing document item), MARA (general material data), MARC (plant-level material data), MARD (storage location stock), MATDOC (goods movements in S/4HANA — replaces MSEG), RBKP (invoice document header from MIRO), RSEG (invoice document item), and LFA1 (vendor master general data). These cover the four core MM areas: procurement, inventory management, master data, and invoice verification.

MSEG (document segment for material documents) was replaced by MATDOC in SAP S/4HANA. MATDOC is the unified inventory management document table that replaced the old MKPF (material document header) and MSEG (material document item) split. In S/4HANA, all goods movement data is stored in MATDOC as a single table with a simplified structure. MKPF and MSEG still exist in S/4HANA for compatibility but are no longer the primary tables — always use MATDOC for new development and reporting.

EKKO (purchasing document header) and EKPO (purchasing document item) are joined on two fields: MANDT (client) and EBELN (purchasing document number). The relationship is one-to-many: one EKKO header record links to multiple EKPO item records. In SE16N or SE16, when you query purchasing data you typically need both tables — EKKO gives you vendor (LIFNR), document date (BEDAT), and document type (BSART); EKPO gives you material (MATNR), quantity (MENGE), and plant (WERKS).

In SAP S/4HANA, goods movement data is stored in MATDOC (Material Document). This replaced the old two-table structure of MKPF (header) and MSEG (item) from SAP ECC. MATDOC stores everything in one table: document number (MBLNR), year (MJAHR), item (ZEILE), material (MATNR), plant (WERKS), movement type (BWART), quantity (MENGE), and the linked purchasing document (EBELN/EBELP). When doing ABAP development or reporting in S/4HANA, always use MATDOC — not MSEG.

MARA holds material data that applies across the entire SAP client — material number (MATNR), material type (MTART), material group (MATKL), base unit of measure (MEINS), and gross weight. It is the top-level material master table with one record per material. MARC holds material data at the plant level — one record per material per plant combination. It contains MRP settings (DISMM, DISPO), procurement type (BESKZ), special procurement key (SOBSL), and ABC indicator. A single MARA record can have many MARC records — one for each plant where the material is maintained.

Current stock levels are stored in MARD (storage location data for material). MARD holds unrestricted stock (LABST), quality inspection stock (EINME), and blocked stock (SPEME) at the storage location level — one record per material, plant, and storage location combination. For the most accurate real-time stock figure, always use transaction MMBE (Stock Overview) or MB52 (Warehouse Stocks of Material) rather than querying MARD directly, as posting delays can affect table accuracy in busy systems.

Invoice data entered via MIRO is stored in two tables: RBKP (header data — vendor, posting date, gross amount, invoice number) and RSEG (line item data — purchasing document reference, material, quantity, amount, tax code). The join is MANDT + BELNR + GJAHR. A third table, BKPF (accounting document header), is created simultaneously in FI. For blocked invoices, query RBKP with field RBSTAT = 'A' to identify invoices pending release in MRBR.

EINA (purchasing info record — general data) and EINE (purchasing info record — purchasing organisation data) store the purchasing info record created via ME11. EINA holds the material-vendor relationship at the client level: vendor (LIFNR), material (MATNR), and info record number (INFNR). EINE holds the purchasing organisation level data: net price (NETPR), valid from/to dates, and planned delivery time. The join between EINA and EINE is on MANDT + INFNR. Info records are the source of default pricing when a purchase order is created for a vendor-material combination.

The plant on a purchase order line item is stored in table EKPO (purchasing document item), field WERKS. Query SE16N with table EKPO, enter your purchasing document number in field EBELN, and the result shows WERKS at the line item level. Note that different line items on the same PO can be for different plants — the plant is always at item level, not header level. The header table EKKO does not contain plant — it only contains vendor (LIFNR), document type (BSART), and purchasing organisation (EKORG).

The most commonly asked SAP MM tables in interviews are: EKKO and EKPO (and the ability to explain their join and what data each holds); MARA, MARC, MARD (material master hierarchy — client, plant, storage location); MSEG/MATDOC (goods movement — and crucially, knowing that S/4HANA uses MATDOC); RBKP and RSEG (invoice verification); LFA1 and LFB1 (vendor master); and T156 (movement type table). Interviewers test whether you know which table to go to for which data — not just that the tables exist.

LFA1 is the vendor master general data table in SAP. It stores the core vendor information at the client level: vendor account number (LIFNR), name (NAME1), country (LAND1), city (ORT01), and tax number (STCD1). In S/4HANA, vendor master is maintained via transaction BP (Business Partner) but data still sits in LFA1. LFA1 has a companion table LFB1 (vendor master company code data) which stores company-code-specific data like reconciliation account (AKONT) and payment methods. The join is MANDT + LIFNR.

Use transaction SE16N (General Table Display) — the standard way to query any SAP database table without writing code. Enter the table name, add filter values for the fields you want, set a maximum number of results, and execute. SE16N is available to most SAP consultants with appropriate authorisation. In production systems, direct table access is often restricted — use standard reports like ME2M (purchase orders by material), MB51 (material document list), or MIR4 (display invoice) to get the same data through controlled transactions.

EKET is the scheduling agreement delivery schedule table in SAP MM. It stores delivery schedule lines for outline agreements (scheduling agreements created with ME31L). Key fields: EBELN (scheduling agreement number), EBELP (item number), EINDT (delivery date), MENGE (scheduled quantity), and WEMNG (quantity of goods received against this schedule line). The join to the main purchasing tables is MANDT + EBELN + EBELP. EKET is only populated for scheduling agreements — standard purchase orders do not have EKET records.

The GR/IR clearing account balance is visible via GL account data in table BSEG, filtered by the specific account configured in OBYC (transaction key WRX). To find open GR/IR items specifically, use report MB5S (GR/IR Account Analysis) — it reads from EKBE (purchasing document history), MATDOC (goods movements), and RBKP/RSEG (invoices) to calculate what is open. The EKBE table is the most useful direct table for seeing all GR and IR postings against a specific purchase order line.

EKBE (purchasing document history) stores the complete history of all transactions posted against a purchase order or scheduling agreement line item. Key fields: EBELN (PO number), EBELP (PO item), VGABE (transaction event type — E for GR, Q for invoice), MENGE (quantity), WRBTR (value), BELNR (material or accounting document number). EKBE is the single most useful table for answering questions like: "Has a GR been posted for this PO?" or "What has been invoiced so far?" — making it critical for AP reconciliation, three-way match checking, and GR/IR clearing work.

T156 is the movement type text table in SAP MM. It stores the description and short text for each movement type used in MIGO and other inventory management transactions. Key fields are MANDT, BWART (movement type), and SPRAS (language). The companion table T156S contains the control parameters for each movement type — whether it creates a financial document, which account determination it triggers, and whether it is a reversal movement. Movement types are configured via OMJJ, which reads from T156 and T156S.

In SAP S/4HANA, table MATDOC links a goods movement to its originating purchase order via fields EBELN (purchasing document number) and EBELP (purchasing document item). In SAP ECC, this same link was in table MSEG. When a goods receipt is posted in MIGO with reference to a purchase order, SAP automatically populates EBELN and EBELP in the resulting MATDOC record. This is how the three-way match works in the background — MIRO reads MATDOC to find what goods receipts exist for a PO before allowing invoice posting.

MLAN is the material master tax classification table. It stores the tax indicator for a material at the client level, used in tax determination during purchasing. Key fields: MATNR (material number), ALAND (country), TATYP (tax category), and TAXM1 (tax classification value — 0 = full tax, 1 = reduced tax, 2 = tax exempt). In SAP MM, MLAN matters when dealing with non-deductible input tax on purchase orders — the tax indicator in MLAN affects how VAT/GST is calculated and whether it is fully recoverable. Maintained through MM01 in the Sales views.

Use transaction ME2L (purchase orders by vendor) — the standard report for this task. If you need to query the database directly, use SE16N on table EKKO with the vendor number (LIFNR) as the filter. EKKO is the purchasing document header table, and vendor is a header-level field. Add a document type filter (BSART = 'NB' for standard POs, 'FO' for framework orders) if needed. To get line item details (materials, quantities, amounts), join EKKO to EKPO on MANDT + EBELN. In interviews, always mention both the transaction (ME2L) and the table join (EKKO/EKPO) to show you understand both the system and the data model.

Yes — VoiSAP's SAP MM training covers both the functional processes and the underlying data model, including the key tables in this guide. You get hands-on access to a live SAP S/4HANA system, so you can run SE16N queries and see how EKKO, EKPO, MATDOC, and RBKP actually look in a real system — not just theory. Training from an instructor with 18 years of SAP consulting experience across enterprise clients in the UK and Canada. Students consistently land their first SAP MM role within 3-6 months. Book a free demo to discuss your background and the right preparation path.