SAP PO Report by Creator: Transactions and EKKO-ERNAM
sap po report by creator
Also searched as
- sap po report tcode
- sap po report transaction
- list purchase orders by created by user SAP
- EKKO ERNAM purchase orders by user
Short answer
To list SAP purchase orders by who created them, run ME2N or ME80FN and filter on Created By (EKKO-ERNAM), using dynamic selections when the field is not on the selection screen. For a quick raw list, read table EKKO in SE16N with ERNAM set to the user ID. Save the selection as a variant so buyers and managers can rerun it.
Applies to: SAP ECC 6.0 and S/4HANA on-premise. Selection screen layout differs slightly between releases.
How to run a PO report by creator
- 1Run ME2N (Purchase Orders by PO Number), or ME2L (by Vendor) / ME2M (by Material) if that is how you want to slice the list.
- 2Enter a plant, document date range and a document type (NB for standard POs) to keep the list manageable.
- 3To filter on creator, use the dynamic selections button on the selection screen and add the field Created By from the EKKO header fields. Enter the user ID.
- 4Alternatively run ME80FN (Purchase Order Analysis), which presents a flexible selection for header fields and a list you can sort and subtotal.
- 5Choose the scope of list (for example open items only, or all) and execute.
- 6Switch the ALV layout to add buyer, value, vendor and status columns, then save the layout.
- 7Save the whole selection as a variant (Goto > Variants > Save as Variant) so it can be reused or scheduled.
- 8For a raw data check, open SE16N, table EKKO, filter ERNAM and BEDAT, and read EBELN, LIFNR, EKGRP and AEDAT.
Which transaction to pick
ME2N is the everyday PO list: selection by document number, vendor, material, plant, purchasing group and dates, with scope-of-list options for open, delivered or invoiced status. ME2L and ME2M are the same engine with a vendor or material entry point. If you already know the buyer's purchasing group, filter on that first, because many sites set one group per buyer.
ME80FN is the analysis report. It reads purchasing documents and is better when you want to analyse many POs by a header attribute and then drill into items. Neither report is a dedicated creator report, so the creator filter is always a header field selection.
Creator versus buyer versus purchasing group
Created By (EKKO-ERNAM) is the user who saved the PO. The buyer a manager usually means is the purchasing group (EKKO-EKGRP), which can be different: a PO might be created by an assistant or generated from a requisition by an automatic job, which then shows the batch user as creator.
Decide which one the report is for. Performance reviews usually need purchasing group, audit questions about who keyed a PO need ERNAM, and change tracking needs the change documents in CDHDR and CDPOS for object class EINKBELEG.
SE16N > EKKO ERNAM = JSMITH BEDAT = 01.09.2026 to 30.09.2026 Output: EBELN, BSART, LIFNR, EKGRP, BEDAT, ERNAM
Variants, layouts and scheduling
Save two things: a variant for the selection and an ALV layout for the columns. Users often save only one and wonder why the report looks different tomorrow. Variants can be protected and assigned to a user group so managers cannot overwrite the shared version.
To run the list on a schedule, create a background job in SM36 with the report behind ME2N and the saved variant, and send the result as a spool or email. Test the report name in your system first, because ME2N is a transaction wrapping a standard purchasing list report.
When a query is cleaner
If the business needs PO value by creator by month, a plain SAP query (SQ01) or a CDS-based analytic app in S/4HANA is easier to maintain than a heavily dynamic ME2N variant. Keep the report authorised through the usual purchasing authorisation objects so a creator list does not expose vendors a user should not see.
Try it here, free
SAP MM Transaction Codes Reference
Searchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
Common pitfalls
- !Treating Created By as the buyer. Automated PO creation shows a batch user.
- !Forgetting that ME2N hides some deleted or closed items depending on scope of list.
- !Saving a layout but not a variant (or the reverse).
- !Running SE16N on EKKO for large date ranges in production without a plant or date filter.
- !Reading values from the header only when you need item value from EKPO.
How an ERP-grounded AI assistant handles this
Instead of building a variant per manager, an assistant grounded in SAP can answer a question like how many POs did each user create last month and their total value, run the equivalent read against EKKO and EKPO, and show the query it used. On-prem, Netray deploys this against your own SAP with SAP roles respected and no data leaving your network.
Frequently asked questions
Which SAP transaction lists POs by creator?
There is no dedicated one. Use ME2N or ME80FN and filter on Created By through dynamic selections, or read table EKKO with ERNAM in SE16N. Then save the selection as a variant so the report can be reused.
Where is the creator stored on a purchase order?
In the PO header table EKKO, field ERNAM (Created By), with AEDAT as the creation date. Later changes are not recorded there but in change documents CDHDR and CDPOS for the purchasing document object.
What is the main SAP PO report transaction?
ME2N is the standard PO list by document number, with ME2L for vendor and ME2M for material. ME80FN is the more flexible analysis report. Which one you use depends on whether you start from the PO, the vendor or the material.
Can I schedule a PO report for a creator?
Yes. Save the selection as a variant and schedule the underlying report in SM36 with that variant, with spool or email output. Check authorisations for the job user so the output matches what the requester is allowed to see.
Related
SAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tables
Use ME2N for a flexible open PO list, ME2M by material and ME2L by vendor, with the selection parameter Still to be delivered. The open quantity is the scheduled quantity in EKET minus goods received in EKBE, excluding deleted and delivery-completed items. For custom reports, read EKKO, EKPO, EKET and EKBE.
How-toSAP ME21N: why the release strategy is not determined on a purchase order
When a purchase order saves without a release strategy, no strategy in the release group matched the PO's characteristic values. Compare the PO header values (value, document type, purchasing group, plant) against the value ranges in the strategy classification (CL24N), and check that the release group and code are active for the PO document type.
Error fixPO Not Released in SAP: Release Strategy, ME28 and ME29N Fixes
A purchase order that stays unreleased almost always has a release strategy that is assigned but cannot advance: the release code is not given to the approver, the prior release step is still open, the approver or workflow agent does not exist, or a change reset the strategy. Check the Release Strategy tab in ME23N, then fix the code assignment, the workflow, or the value that triggered the strategy.
Error fixSAP 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 fixSAP 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.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI 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 ERPGet 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 ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP MM Transaction Codes ReferenceSearchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
- SAP Open Purchase Order Items ABAP SELECT GeneratorBuilds an ABAP report that selects open PO schedule lines with open quantity from EKKO, EKPO and EKET, filtered by purchasing organisation, plant, document type and date.
- SAP MM and QM BAPI and API List ReferenceA searchable list of the common SAP MM and QM BAPIs and S/4HANA OData APIs, what each does, and whether it needs a commit.
ERP fixes and how-tos
- SAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tablesHow to list open purchase order quantities in SAP with ME2N, ME2M and ME2L, which tables hold the data, and how to calculate open quantity from EKBE.
- Contract, MMBE and PPV Reports in SAP MMRun contract reports in SAP MM with ME2M and ME2N, check stock with MMBE, report purchase price variance and build custom MM reports with SQ01 and CDS views.
- How to Create a Purchase Order in SAP MM (ME21N)Step-by-step purchase order creation in SAP MM with ME21N: manual PO, PO from requisition, account assignment, release and the order-to-invoice flow.