IT CanvassTalk to an advisor
SAP tables · LessonBy , SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels

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.

Quick answer

EKPO is where PO line detail lives, quantities, prices, plant, account assignment.

Key takeaways
  • The key is EBELN + EBELP, one row per PO line.
  • EBELN, purchasing document (key).
  • EBELP, item number (key).
  • Watch out: Reading tables directly instead of using CDS/reports where appropriate.

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.

Practice challenge

+0 XPStreak ×0
Question 1 of 3
Which statement is true of EKPO?

Frequently asked questions

What does EKPO stand for in SAP?
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.
Which fields matter most in EKPO?
The key is EBELN + EBELP, one row per PO line.
What is worth remembering about EKPO in practice?
EKPO is where PO line detail lives, quantities, prices, plant, account assignment.
What tends to go wrong with EKPO?
Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.
Already working on SAP and stuck on a live ticket?Get an expert SAP developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support