SAP EKPO
EKPO is a key SAP table in MM (Purchasing). It stores purchasing document items, the line-level data (materials, quantities, prices, plant) of purchase orders and related documents.
EKPO holds purchase order line items in SAP, keyed by purchasing document EBELN and item EBELP: one row per PO line, with the material, quantity, net price, plant and account assignment. The header sits in EKKO, schedule lines in EKET and the PO history in EKBE. It is one of the most-queried MM tables for procurement reporting.
- EBELN, purchasing document (key).
- EBELP, item number (key).
- Watch out: plant and account assignment are per item, which is why one order can hit several cost objects.
What it stores
It stores purchasing document items, the line-level data (materials, quantities, prices, plant) of purchase orders and related documents.
Key fields
- EBELN, purchasing document (key).
- EBELP, item number (key).
- MATNR, material.
- MENGE, quantity; NETPR, net price.
- WERKS, plant.
Keys and relationships
The key is EBELN + EBELP, one row per PO line. It links back to the header (EKKO) via EBELN and to schedule lines (EKET) and history (EKBE).
Working with it
EKPO is where PO line detail lives, quantities, prices, plant, account assignment. It is one of the most-queried MM tables for procurement reporting. View its structure in SE11 and its data (with authorization) in SE16N.
Common pitfalls
- Reading tables directly instead of using CDS/reports where appropriate.
- Ignoring header/item relationships.
- Performance: querying large tables without indexed selection.