SAP transaction codeObjectME23NModuleMM

ME23N — Display a purchase order

ME23N displays a purchase order in read-only mode. It is the safe transaction for support, audit and reconciliation work: you read supplier, terms, item quantities, prices, delivery dates and account assignments, together with the purchase order history that lists every goods receipt and invoice posted against each item.

Displaying purchase orders: reading the order history, status information and account assignment without changing anything.

Reviewed by an ERPClimb SAP consultant on 13 Sept 2026· 581 words

What ME23N is for

ME23N shows the purchase order exactly as stored, with no possibility of changing it. That makes it the transaction of choice for anyone who needs the facts rather than the ability to act: a finance analyst reconciling an open commitment, an auditor tracing an approval, a support consultant explaining a variance, or a business user checking what was actually ordered. Read access to purchasing documents is also far easier to justify in an authorisation concept than change access, so in most landscapes many more users have this transaction than have the change transaction.

When it is used in procure-to-pay

It is the first stop in most procure-to-pay investigations. When a supplier claims a delivery was never ordered, when an invoice will not post because of a quantity or price difference, or when a goods receipt appears against the wrong cost object, the answer is usually visible in the order and its history. It is also used in reconciliation: an item whose ordered quantity, received quantity and invoiced quantity disagree explains a GR/IR balance far more reliably than a spreadsheet does. Project teams use it to confirm that an interface or a conversion created the order the design intended.

How it is used in practice

Open the order by number, or search by supplier, material, requisition or plant. Read the header for supplier, purchasing organisation, terms and release status, then the item overview for quantities, prices, delivery dates and plants. Item detail carries the account assignment, conditions, texts, confirmations and the purchase order history. The history is the most useful single view: it lists the goods receipts and invoices posted against the item with quantity and value, which immediately shows whether the item is fully received, partly invoiced or closed. Status information tells you whether delivery and invoice are flagged as complete, which explains why nothing further can be posted.

Fields and objects that matter

  • Purchase order number and document type, which set the rules the document follows
  • Ordered, received and invoiced quantity per item, the three numbers behind most disputes
  • Purchase order history, listing each material and invoice document posted against the item
  • Delivery completed and final invoice indicators, which explain a closed item
  • Account assignment and cost object, showing where the cost was intended to land
  • Purchase order header EKKO, items EKPO and the history records behind each posting

Common pitfalls and how they show up

  • Quoting the ordered quantity when the question was about what has actually been received
  • Concluding no invoice exists without opening the purchase order history
  • Missing a delivery-completed flag and reporting an open commitment that the business has already closed
  • Comparing a net price against a supplier invoice without checking conditions, taxes and delivery costs
  • Reading an old print of the order while changes were made the same day
  • Treating read access as harmless from a compliance point of view; pricing and supplier terms are commercially sensitive
  • Investigating in the order when the posting error is actually in the receipt or the invoice document

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Lessons and topics

ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.