SAP Purchase Order Report

What the purchase order report shows

A SAP purchase order report answers a simple question that SAP makes surprisingly hard: give me every purchase order record, with all the attributes that matter, in one place I can filter and share. On screen, SAP shows one record at a time and splits its attributes across several views. This report flattens all of that into a single Excel sheet, one row per record, with the codes turned into readable labels.

Because the output is a plain sheet, it becomes the starting point for the work people actually do with it: a data-quality review, a cleanup before a migration, a hand-off to an auditor, or a source for a pivot. The value is not just the extract, it is that the extract is complete and consistent every time you run it.

The SAP tables behind it

A purchase order is a header with many items, and each item has its own history. EKKO holds the header: PO number EBELN, document type, company code, purchasing org and the vendor. EKPO holds the items, keyed by EBELN plus the item number EBELP, with material, quantity, price and value. EKET holds the delivery schedule lines for each item. EKBE holds the PO history, the goods receipts and invoice receipts posted against each item, which is what tells you how much has actually been delivered and invoiced. The vendor name is joined from LFA1 on LIFNR, and the material description from MAKT on MATNR. The report is keyed at item level so each PO line is one row.

The joins are the whole reason this is worth automating. Miss one and the report is subtly wrong; get the key fields slightly off and rows fan out or drop. Doing it once, correctly, and then reusing it is what turns a fragile spreadsheet exercise into a reliable report.

The columns you get

Every column below is a real SAP field, labelled in plain English, with the table it is read from. These are the fields most teams want on a purchase order report; a tool like PostNow lets you add or remove columns without touching the underlying join.

Building it yourself: ME2M/ME2L, SE16 or SQVI

ME23N shows one purchase order in full but only one at a time. ME2M and ME2L give list views, but they are shaped around specific selection logic and are awkward to bend into a flat export with exactly the columns you want. SE16 on EKKO and EKPO gives you the header and item tables, which you then match on the PO number in Excel, and you still have to bring in EKET for schedules and EKBE for the receipt history separately. The GR/IR history in EKBE is the hardest part to assemble by hand, because it holds several movement types per line that have to be summed correctly. Getting all of that into one refreshable sheet is a developer job.

None of this is impossible; people do it every month. The problem is that it is manual, easy to get subtly wrong, and stale the moment it is saved. Each refresh means repeating the same exports and the same lookups, and any new column means another round with a developer. For a one-off you can push through it. For a report you run every period, the cost adds up. If you want the general landscape of options first, see our overview of SAP reporting tools and how to get SAP to Excel.

The out-of-the-box way: PostNow's purchase order report

PostNow's Report Library already contains this exact report, pre-built. You do not assemble the joins or resolve the texts; that is done for you. You open Excel, log in to postnow.ai from the task pane, pick the purchase order report, set your range filters, and run. The governed, joined data lands in the sheet, ready to filter, pivot or share, and you can refresh it whenever you need the latest.

Two things make this different from a SE16 dump. First, it is governed: PostNow enforces your own SAP authorizations, so you only ever see the data you are entitled to, and every row can be traced back to its source. Second, it is repeatable: the same report, the same columns, refreshable on demand, with no ABAP to write or maintain. That is the payoff of teaching the hard version first, then handing you the shortcut.

Filters and selection you'll want

A good purchase order report is only as useful as the selection you can put on it. The filters most teams reach for are:

• PO range (EBELN from / to)
• Vendor (LIFNR)
• Purchasing org (EKORG)
• Company code (BUKRS)
• Document date (BEDAT range)
• Open / completed (ELIKZ)

You set these once as your selection, then reuse or adjust them each run. Because the selection travels with the report, a monthly extract becomes a single refresh rather than a rebuild.

ECC vs S/4HANA

The purchase order tables are read through standard interfaces, so the report behaves the same way on SAP ECC and S/4HANA. Where the underlying data model shifts between releases, a table-based read stays stable because it targets the fields your report actually needs.

The practical takeaway is that a report built on the tables and read through standard interfaces survives a migration far better than one wired to a specific screen or a custom program. When you eventually move from ECC to S/4HANA, a table-based purchase order report keeps working, which is one less thing to rebuild in an already large project.

Frequently asked questions