How-toSAP ERP / S/4HANAMM / FI Procure-to-Pay Reporting

SAP Procure-to-Pay (PTP) Reporting: Reports, Tcodes and Tables

Question
sap ptp reporting

Also searched as

  • sap procure to pay reports
  • sap open po report
  • sap gr/ir report MB5S
  • sap p2p cycle time report

Short answer

SAP procure-to-pay reporting spans requisition, PO, goods receipt, invoice and payment. Use ME2N for open POs, MB5S for GR/IR balances, MIR5 and MRBR for invoices, and FBL1N for vendor open items. For cycle time, join EBAN, EKKO, EKBE and RBKP.

Applies to: SAP ECC 6.0 and S/4HANA, standard MM and FI-AP

How to build a PTP reporting set

  1. 1Open purchase orders and undelivered items: ME2N, with scope for items not yet fully delivered.
  2. 2Goods received not invoiced: MB5S for GR/IR analysis, then clear balances with MR11 after review.
  3. 3Invoice status: MIR5 to list invoice documents, MRBR to release invoices blocked for price or quantity.
  4. 4Vendor payables: FBL1N for vendor line items, with open items, due dates and payment status.
  5. 5Receipts: MB51 with movement type 101 for goods receipts and 102 for reversals.
  6. 6Cycle time and process analysis: join EBAN, EKKO, EKPO, EKBE, RBKP and RSEG in a query, or use process analytics apps on S/4HANA.

The key reports by stage

Requisition to PO: ME5A lists purchase requisitions and ME57 helps assign sources. A backlog here shows buyers who are behind. Table EBAN holds requisitions.

PO to goods receipt: ME2N and ME2L show open quantities and delivery dates. MD04 shows planned receipts against requirements. EKET holds the schedule lines with delivery dates and EKES holds vendor confirmations.

Goods receipt to invoice to payment: MB5S analyses GR/IR, MIR5 lists invoices, and FBL1N shows payables. The GR/IR account is a clearing account and its balance is the main control for this step.

GR/IR and the three-way match

The GR/IR clearing account holds the value of goods received but not invoiced, and invoices received before goods. Large old balances usually mean missing invoices, wrong quantities or a PO posted in the wrong unit.

Three-way match compares PO, goods receipt and invoice. Differences beyond the tolerance limits block the invoice, which then appears in MRBR. Tolerance limits are set in OMR6.

A monthly review of old GR/IR items, grouped by vendor and age, is the standard control. Clearing without review writes off real liabilities.

Cycle-time query across the tables

To measure PR to PO time, compare EBAN creation date to EKKO document date. PO to receipt uses EKKO and EKBE with history category E for goods receipt. Receipt to invoice uses EKBE category Q and the invoice header RBKP.

The history table EKBE has a transaction type field VGABE: 1 for goods receipt and 2 for invoice receipt. Joining on it gives a per-PO timeline.

-- PO item timeline (illustrative)
SELECT p.ebeln, p.ebelp, h.vgabe, h.budat, h.menge, h.dmbtr
FROM ekpo p
JOIN ekbe h ON h.ebeln = p.ebeln AND h.ebelp = p.ebelp
WHERE h.vgabe IN ('1','2')
ORDER BY p.ebeln, p.ebelp, h.budat

Try it here, free

SAP MM Standard Reports and Report T-Codes

Open full tool

Search SAP MM standard report t-codes for POs, RFQs, stock, GR/IR and audit, with the use case for each.

Common pitfalls

  • !ME2N shows open quantities per item, not per schedule line. Late deliveries need schedule-line data from EKET.
  • !Reversed goods receipts (movement 102) must be netted in cycle-time calculations.
  • !Delivery-completed flags can hide partial deliveries. Check item status.
  • !Invoices posted through FI without a PO do not appear in MM reports.
  • !Currency and unit conversions affect GR/IR reconciliation. Compare in local currency and base unit.

How an ERP-grounded AI assistant handles this

A PTP report set is a good fit for a grounded assistant because the questions are routine and the joins are tedious. Ask 'which vendors have GR/IR items older than 90 days' and get the list with the query shown. Read-only access and on-prem deployment keep supplier and pricing data private.

Frequently asked questions

Which report shows open purchase orders in SAP?

ME2N lists purchase orders with open quantities, and ME2L lists them by vendor. Use the selection scope for items not yet fully delivered.

What is MB5S?

MB5S analyses the GR/IR clearing account by PO, showing quantities and values received but not invoiced and the reverse.

How do I see blocked invoices?

Use MRBR to list and release invoices blocked for price, quantity or other tolerance differences. MIR5 lists all invoice documents.

Which tables hold PO history?

EKBE holds the PO history with goods receipts and invoice receipts, distinguished by field VGABE. EKKO and EKPO hold header and item data.

Related

How-to

Landed cost in SAP MM: planned and unplanned delivery costs

SAP MM handles landed cost through delivery cost conditions. Planned delivery costs are conditions on the purchase order (flagged as delivery costs) that are accrued at goods receipt and settled with the freight invoice. Unplanned delivery costs are entered in MIRO when the invoice arrives. How they hit inventory value depends on the price control of the material.

How-to

SAP MM Approval Process: Release Strategies, Workflow and Fiori

SAP MM approval is built on release strategies: rules that block a purchase requisition (PR) or purchase order (PO) until the right people release it with release codes. Strategies are configured with classification characteristics and can be released in ME28 or ME29N, through workflow, or in Fiori approval apps. In S/4HANA there are also flexible workflows for PRs.

Error fix

SAP F5 060: Posting Only Possible in Periods X and Y

Message F5 060 fires when a document date falls in a fiscal period that the posting period variant has not opened for that account type. Either change the document/posting date into an open period, or have Finance open the required period and account type in OB52 for the relevant variant.

How-to

SAP MMPV Period Closing Error: Opening and Closing MM Periods

MM keeps its own posting period, separate from FI. MMPV (Close Period for Materials Management) moves the current MM period forward one month, MMRV allows posting back into the previous period, and OMSY initializes periods once at setup. The control values are stored in table MARV, one row per company code. Most MMPV errors mean the periods are not in the state the program expects or open work blocks closing.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

AI for ERP

AI for SAP S/4HANA, Running On-Prem or in Your Private Cloud

Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.

AI for ERP

Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANA

SAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.

Stuck on SAP ERP / S/4HANA?

Talk to engineers who work inside SAP ERP / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP