SAP EKKO
EKKO is a key SAP table in MM (Purchasing). It stores purchasing document headers, the header-level data of purchase orders (and related purchasing documents).
EKKO holds purchasing document headers, keyed on EBELN, with the document type BSART, vendor LIFNR, purchasing organisation EKORG and document date BEDAT. Its items sit in EKPO keyed on EBELN plus item, schedule lines in EKET and the goods receipt and invoice history in EKBE. Join on EBELN; SE11 shows the structure and SE16N the data.
- EBELN, purchasing document number (key).
- EKPO, purchasing document items.
- EKET, schedule lines (delivery dates).
- Watch out: the release strategy fields sit here, so an unreleased order looks complete in the header.
What it stores
It stores purchasing document headers, the header-level data of purchase orders (and related purchasing documents).
Key fields
- EBELN, purchasing document number (key).
- BSART, document type.
- LIFNR, vendor.
- EKORG, purchasing organization.
- BEDAT, document date.
Keys and relationships
EBELN is the key. EKKO holds the header; the line items are in EKPO, keyed by EBELN + item. Together they represent a complete purchasing document.
Working with it
EKKO/EKPO is the classic header/item pair for purchasing. Join them on EBELN, and use EKBE for goods-receipt/invoice history against the PO. 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.