ME2L — Purchase Orders by Vendor List

ME2L displays purchase orders (and other purchasing documents when the document type range is widened) filtered by vendor. It is a pure evaluation transaction - it reads EKKO/EKPO/EKET/EKBE and renders an ALV list, it does not create or change anything itself, though double-clicking a line normally jumps into ME23N or ME22N depending on authorization. The structural fact that explains most confusion: the list layout and the underlying selection logic are both driven by the 'Scope of List' parameter on the selection screen (ALV, BEST, EIKO and others). Two consultants running ME2L for the same vendor and date range can see completely different columns, and sometimes completely different document sets, purely because they picked a different scope of list - this is far more often the cause of 'the PO is missing' than a genuine data problem.

Purchasers and MM consultants use ME2L to review a vendor's open order book before a delivery follow-up call, to check GR/IR exposure ahead of period-end, or to confirm which items are still outstanding before closing a negotiation. It is the vendor-centric sibling of ME2M (material-centric) and ME2K (account-assignment-centric) - reach for ME2L specifically when the question is framed around one vendor or a vendor range, not a material or a cost object. In S/4HANA, Fiori apps for single-document purchase order handling cover individual transactions, but ME2L is still the faster tool for a bulk, vendor-level cut across many open items, and it remains the first stop when diagnosing why a document a buyer expects to see is not appearing in a vendor's evaluation.

ME2L itself writes nothing, so proving a symptom means checking the source tables directly. In SE16N on EKPO, filter on EBELN or on LIFNR via an EKKO join, and check LOEKZ (deletion indicator), ELIKZ (delivery completed) and ERKZ (final invoice) - any of these set removes the item from an 'open' selection even though the document still exists. Cross-check EKET-EINDT against the selection screen's date range, and if the complaint is about invoicing status, check EKBE for movement type and quantity to confirm whether a goods receipt or invoice receipt actually posted against the item.

ME2L continues to function identically on S/4HANA; the underlying tables and selection logic are unchanged. Fiori offers transactional apps for single-document purchase order handling and analytical apps for spend and status reporting, but none of them replace the fast bulk vendor-level cut that ME2L provides, so the transaction remains in active use rather than being deprecated.

This is a functional MM/purchasing problem in the overwhelming majority of cases - the selection parameters, scope of list, and document flags described above are business configuration and business data, not code. ABAP involvement is only needed if a custom scope-of-list variant or a Z-report built on the same tables is broken. Basis involvement is limited to authorization role fixes. A useful handover includes the vendor number, an example PO number, and the exact selection screen values used.

ME2M is the material-centric equivalent and worth comparing when the same discrepancy needs to be checked from the material side rather than the vendor side. ME3N gives the same kind of list view for outline agreements and contracts, which ME2L does not surface by default. MK03 confirms whether the vendor number in question is current, extended to the right purchasing organization, or has been superseded. MIR4 is useful once a 'still to be invoiced' discrepancy from ME2L needs to be traced forward into an actual invoice document.