ME3N — Outline Agreements by Agreement Number
ME3N is a Purchasing report for listing outline agreements by agreement number. SAP documentation groups it with the ME3* outline-agreement reports: ME3L by vendor, ME3M by material, ME3K by account assignment, and ME3N by agreement number. It is not a purchase-order-by-vendor list; ME2L is the purchase-order/purchasing-document report by vendor.
This page covers ME3N, the vendor-based purchase order list display used for day-to-day procurement monitoring. It focuses on the selection-screen traps and layout confusion that cause consultants to think data is missing when it is actually filtered out by a checkbox or an authorization restriction.
Published 20 Sept 2026· 519 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
ME3N lists outline purchase agreements—contracts and scheduling agreements—using agreement/document number and related selection criteria. It belongs to the ME3* outline-agreement reporting family. This distinction matters because outline agreements have target quantities/values, validity, and release/call-off behavior different from ordinary purchase orders.
When it is used
Use ME3N when procurement needs a worklist of contracts or scheduling agreements by agreement number or other selection fields, for example to review validity, status, supplier, material, or agreement consumption. For ordinary purchase-order lists use the ME2* family instead.
How to use it in practice
- Enter the agreement number/range or other organizational criteria required for the analysis.
- Restrict purchasing organization, purchasing group, supplier, plant, document type, or validity where appropriate.
- Choose a list scope/layout that exposes the fields needed for contracts or scheduling agreements.
- Execute and separate contract versus scheduling-agreement behavior when interpreting quantities/values.
- Drill into ME33K or ME33L, as appropriate, for detailed agreement display and follow-on history.
Key data objects
Outline agreements are purchasing documents stored in the purchasing header/item model with agreement-specific fields and follow-on documentation.
- EKKO — agreement header, supplier, purchasing organization, document type, validity, and currency.
- EKPO — agreement items, material/material group, plant, target quantity/value, and item status.
- Agreement number/document type — identifies whether the object is a contract or scheduling agreement.
- Release/call-off or schedule history — interpret consumption using the appropriate contract/scheduling-agreement follow-on data.
- Pricing result/conditions — review the agreement's purchasing conditions using current S/4HANA pricing data structures where relevant.
How to prove it in the data
Take an agreement from the ME3N result and open it in ME33K for a contract or ME33L for a scheduling agreement. Confirm EKKO/EKPO header/item keys, validity, target quantity/value, and follow-on consumption or schedule information. If an expected agreement is absent, compare the ME3N selection with the agreement's document type, validity, purchasing organization, and deletion/block status.
ECC vs S/4HANA
SAP's current purchasing documentation continues to describe ME3N as Outline Agreements by Agreement No. Fiori contract and scheduling-agreement apps can provide modern worklists, but ME3N remains a classic purchasing report for the outline-agreement object family.
Common pitfalls and how to diagnose them
- Calling ME3N a purchase-order-by-vendor report — ME2L covers purchasing documents by vendor; ME3N is for outline agreements by agreement number.
- Mixing contracts and scheduling agreements without considering their different follow-on processes.
- Interpreting target quantity/value as open quantity/value without checking release/call-off consumption.
- Using current agreement values to explain historical releases without considering change history and validity.
Whose problem this is
Primary ownership is MM Purchasing. Contract and strategic-sourcing owners handle contracts, scheduling teams handle scheduling agreements, and integration teams join where supplier releases are transmitted electronically.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/me3nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.