# SAP PO Report by Creator: Transactions and EKKO-ERNAM > Source: https://netray.co/erp-help/sap-po-report-by-creator-me2n-me2l-me80fn-ekko-ernam > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module MM Purchasing / Reporting ## Query sap po report by creator ## Alternate Queries - sap po report tcode - sap po report transaction - list purchase orders by created by user SAP - EKKO ERNAM purchase orders by user ## Applies To SAP ECC 6.0 and S/4HANA on-premise. Selection screen layout differs slightly between releases. ## Steps ### How to run a PO report by creator **Items:** - Run ME2N (Purchase Orders by PO Number), or ME2L (by Vendor) / ME2M (by Material) if that is how you want to slice the list. - Enter a plant, document date range and a document type (NB for standard POs) to keep the list manageable. - To 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. - Alternatively run ME80FN (Purchase Order Analysis), which presents a flexible selection for header fields and a list you can sort and subtotal. - Choose the scope of list (for example open items only, or all) and execute. - Switch the ALV layout to add buyer, value, vendor and status columns, then save the layout. - Save the whole selection as a variant (Goto > Variants > Save as Variant) so it can be reused or scheduled. - For a raw data check, open SE16N, table EKKO, filter ERNAM and BEDAT, and read EBELN, LIFNR, EKGRP and AEDAT. ## Sections ### Which transaction to pick **Body:** 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 **Body:** 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. **Code:** - SE16N > EKKO ERNAM = JSMITH BEDAT = 01.09.2026 to 30.09.2026 Output: EBELN, BSART, LIFNR, EKGRP, BEDAT, ERNAM ### Variants, layouts and scheduling **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Which SAP transaction lists POs by creator? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap po report by creator, sap po report tcode, sap po report transaction, me2n created by, ekko ernam, me80fn purchase order analysis, list purchase orders by user sap, sap purchase order report --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json