Skip to content
IT Canvass
SAP tables · Lesson

EKKO

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.

  • EKPO, purchasing document items.
  • EKET, schedule lines (delivery dates).
  • EKBE, PO history (GR/IR).
  • LFA1, vendor master.

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.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Which statement is true of EKKO?

    • A. Join them on EBELN, and use EKBE for goods-receipt/invoice history against the PO.
    • B. SAP labs are hands-on exercises where you practise real tasks in an SAP system, the only reliable way to turn…
    • C. Goods Receipt (GR) records the physical receipt of ordered goods into inventory, a pivotal step that updates…
    Show answer

    A. Join them on EBELN, and use EKBE for goods-receipt/invoice history against the PO.

    Covered in the “Working with it” section of this lesson.

  2. Which of these also applies to EKKO?

    • A. Skipping the PAM check, running an unsupported combination.
    • B. Learning features, not the end-to-end process.
    • C. View its structure in SE11 and its data (with authorization) in SE16N.
    Show answer

    C. View its structure in SE11 and its data (with authorization) in SE16N.

    Covered in the “Working with it” section of this lesson.

  3. Which part of the Learn SAP curriculum covers EKKO?

    • A. SAP FI
    • B. SAP tables
    • C. SAP ABAP development
    Show answer

    B. SAP tables

    This lesson sits in the SAP tables section of the Learn SAP course.

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.
CallWhatsAppEnquire