The Procure-to-Pay cycle in SAP is one of the most important processes for any organization. However, users often rely on multiple transactions like ME5A, ME2N, MB51, MB03 and MIR4 just to track one document from start to finish. This leads to confusion, delays and unnecessary back and forth between teams.
To solve this, companies build a Combined P2P Report in a single consolidated view that shows the complete flow:
Purchase Requisition → Purchase Order → Goods Receipt → Invoice
This report works perfectly in SAP ECC and with only minor adjustments, it also runs smoothly in S/4HANA. Below is a full overview of how it helps and what users can expect, along with placeholders for screenshots you can upload.
Works in SAP ECC
The combined report is most commonly used in ECC because all necessary tables for PR, PO, GR, and Invoice exist as-is. The flow remains extremely stable and reliable. This allows the report to show the exact lifecycle from the moment a requisition is raised until the invoice is posted.
ECC users benefit because they no longer have to switch repeatedly between transactions or compare data manually. Everything required for procurement tracking appears on one screen.
Works in S/4HANA with Minor Adjustments
The overall logic remains the same and the report behaves just like it does in ECC, only faster due to the HANA in-memory database.
Combined P2P Report Simulation
For Status Option : All
Selection Screen
Input PO Date Range, Vendor and Plant or Give only PO Date Range to get all vendor and Plant
Combined P2P output showing PR → PO → GR → Invoice flow in one view.
For Status Option : Open
Selection Screen
Input PO Date Range, Vendor and Plant or Give only PO Date Range to get all vendor and Plant
Status Open : Combined P2P output showing PR → PO → GR → Invoice flow in one view.
For Status Option : Completed
Selection Screen
Input PO Date Range, Vendor and Plant or Give only PO Date Range to get all vendor and Plant
Why a Combined P2P Report Is So Useful
This one report removes the pain of checking multiple SAP transactions. It provides a complete story of what happened to a PR or PO and helps teams quickly identify delays or missing steps.
Here are some major benefits:
- End-to-end procurement visibility from requisition to invoice
- Faster troubleshooting for stuck or delayed documents
- Accurate GR/IR reconciliation at month end
- Vendor performance insights like delivery and invoice timelines
- Audit ready reporting with a single consolidated view
- Reduces manual effort by avoiding multiple SAP transactions
Where This Report Helps in Real SAP Work
This report is extremely valuable in:
- Procurement follow-ups
- Daily goods receipt monitoring
- Invoice verification
- Vendor management
- Internal & external audits
- Finance month end closing
Users can instantly see whether:
- A PR is converted to PO
- A PO has a GR posted
- An invoice is posted
- Anything is pending from vendor or internal team
Perfect for SAP MM Procurement & FI Teams
This report gives clarity to everyone involved in the P2P process:
- MM Teams track materials and vendor deliveries
- Procurement Teams monitor PR and PO status
- Finance Teams verify invoices and GR/IR balance
- Auditors get a clean end-to-end view
Once implemented, it becomes one of the most used reports in the entire SAP landscape.
Conclusion
A Combined P2P Report is one of the simplest yet most powerful additions you can make in SAP. It delivers complete visibility across the entire procurement flow in a single screen whether you are on ECC or S/4HANA.
I created this report through a custom ABAP program. If you have any questions or need clarification, feel free to ask in the comments or email me anytime.









Please keep these guidelines in mind when commenting:
Stay On Topic:
Comments should be relevant to the blog post’s subject, focusing on SAP, Microsoft Dynamics 365 FO.
No Promotions or Spam:
Promotional messages, irrelevant links and spam comments will be removed to keep the discussion valuable.
Privacy Reminder:
Please avoid sharing sensitive or personal data in your comments.