Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A purchase order records what is ordered from a supplier. ME23N displays it in classic SAP, including item history that connects receipts and invoices to the order.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Materials Management supports purchasing and inventory. A request, order, goods receipt and supplier invoice describe separate events, each with its own record and status.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP ME23N: Use purchase-order history to explain what happened
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

ME23N purchase-order display/history in classic ERP and supported S/4HANA scenarios. Available tabs and follow-on documents depend on item and process.

Reviewed linked SAP purchasing-history documentation and available official indexed text on 14 November 2026. The PO, references, quantities and calculations are fictional teaching examples. They were not posted or tested in a customer SAP system. Screen layouts and supported follow-on processes depend on item type, release and configuration.

A MANUFACTURING EXAMPLE

Reconcile an assembly-component PO

Reconcile one PO item

Ordered quantity: 100 PC. Net goods receipts: 60 − 10 + 30 = 80 PC. Invoiced quantity: 50 PC. Quantity difference: 30 PC to explain
What to notice: Simplified receipt/invoice comparison assumes aligned units and no other movements; it does not establish payment.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Ordered quantity
100 PC
Net goods receipts
60 − 10 + 30 = 80 PC
Invoiced quantity
50 PC
Quantity difference
30 PC to explain
Words you’ll meet in this guide
Material
A product or supply item managed in SAP.
Plant
An organizational unit for relevant logistics operations.
Goods receipt
A recorded receipt of goods in a business process.
Purchase order
A purchasing document requesting goods or services from a supplier or supplying plant.
Invoice
A supplier’s bill for goods or services.
CDS
Core Data Services: reusable definitions of business data and relationships.
Fiori
SAP’s approach to business application design.
HANA
SAP’s database platform.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Purchase-order item → Receipt and invoice history → Remaining business work. Conceptual diagram for SAP ME23N: Use purchase-order history to explain what happened.
Apply the idea: A machinery buyer needs to explain why a component PO shows receipts, a reversal and a smaller invoiced quantity while assembly still needs the material.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Reconcile an assembly-component PO

    A machinery buyer needs to explain why a component PO shows receipts, a reversal and a smaller invoiced quantity while assembly still needs the material.

  2. What purchase-order history can tell you

    ME23N is a useful starting point when a buyer, receiving team and accounts-payable team describe the same purchase order differently.

  3. Prerequisites: choose the document, item and display context

    Use an authorized purchasing display role in classic ERP or a supported S/4HANA landscape.

  4. Read each row as a business event with a reference

    For a receipt entry, retain the material-document number and item, posting date, movement context and quantity.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.