SAP tables · LessonBy Ravi M, SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels
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).
Quick answer
EKKO/EKPO is the classic header/item pair for purchasing.
Key takeaways
- EBELN, purchasing document number (key).
- EKPO, purchasing document items.
- EKET, schedule lines (delivery dates).
- Watch out: Reading tables directly instead of using CDS/reports where appropriate.
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.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of EKKO?
Frequently asked questions
What does EKKO stand for in SAP?
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).
What is the practical takeaway on EKKO?
EKKO/EKPO is the classic header/item pair for purchasing.
What is worth remembering about EKKO in practice?
EBELN, purchasing document number (key). BSART, document type. LIFNR, vendor.
What tends to go wrong with EKKO?
Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.