How to Display a Purchase Order in SAP: ME23N and Purchase Order Lists

Companies running SAP process thousands of purchase orders every year, yet a single data entry error in a vendor field or a price mismatch can halt an entire production line. The purchase order (PO) acts as the legally binding contract between a business and its supplier. If a user cannot find this document quickly, the supply chain stops moving. Accessing this data is not just a basic task; it is the foundation of inventory management and financial auditing.

The reader will find that SAP provides two primary ways to look at this information. One method focuses on a single, detailed document, while the other provides a bird’s-eye view of many orders at once. Understanding the difference between these views prevents the common frustration of clicking through endless screens just to find a delivery date or a payment status. People who master these shortcuts save hours of manual searching over the course of a business week.

This guide explains the specific steps to navigate these screens without getting lost in the technical weeds. It covers:

• Using transaction ME23N to view every detail of a specific order.
• Breaking down the “Header” and “Item” sections so the reader knows exactly where the money and goods are going.
• Checking the “Purchase Order History” to see if a warehouse has actually received the items.
• Running list reports to find multiple orders based on a vendor name or a date range.

The direct reality: Most system errors happen because a user looked at the wrong tab or missed a status icon. Knowing exactly where to click in ME23N is the best defense against shipping delays and billing disputes.

The following instructions move past the manual and into the actual system logic. By the end of this tutorial, the user will be able to pull up any purchase order and explain its status in seconds. This clarity ensures that the business stays on track and the data remains clean.

Before You Start

• A valid SAP user ID and password for the environment.
• Authorization to access transaction codes ME23N and ME2L or ME2M.
• A specific Purchase Order number or a Vendor name to use for searching.

Step 1: Access the ME23N Transaction

The user must enter the transaction code ME23N into the command field at the top of the SAP Easy Access screen and press Enter. This specific code is the standard gateway for displaying purchase orders without making any accidental changes to the data.

This matters because using the “Display” mode instead of “Change” mode (ME22N) prevents record locking, which allows other colleagues to work on the document simultaneously.

Watch out: If the screen opens to a blank document or the wrong order, the user must click the “Other Purchase Order” button (Shift+F5) to enter the correct PO number.

Step 2: Navigate the Header Data

The reader should look at the top section of the screen, known as the Header. This area contains information that applies to the entire order, such as the vendor’s name, the total currency, and the organizational terms like the Purchasing Group and Company Code.

Correctly identifying the Vendor and Document Date here ensures the user is looking at the right contract before diving into specific parts.

Expected result: The top section expands to show general details that remain the same for every item listed in the order.

Step 3: Review the Item Overview and Details

The user needs to scroll down to the “Item Overview” table to see exactly what products were ordered. Each row represents a different item, showing the quantity, the price per unit, and the expected delivery date for that specific line.

This step is where the reader catches mismatched quantities or incorrect pricing that could lead to overpayment or stock shortages.

Watch out: If an item has a trash can icon next to it, it has been deleted and will not be processed by the warehouse or the accounting department.

Step 4: Check the Purchase Order History

The user should select a line item and click on the “Purchase Order History” tab in the bottom “Item Details” section. This tab lists every action that has happened since the order was created, such as Goods Receipts (when the box arrived) or Invoice Receipts (when the bill was paid).

Checking this history allows the reader to verify if a supplier has fulfilled their promise or if a shipment is missing.

Expected result: A list of follow-on documents appears, showing the specific material document numbers and accounting entries linked to that PO line.

Troubleshooting

The “Other Purchase Order” button is greyed out

This usually happens if the user is already in the middle of an unsaved action or if the system is experiencing a temporary lag. The user should try hitting the “Esc” key or restarting the transaction to reset the interface.

No data appears in the Purchase Order History tab

If this tab is empty or missing, it means no activity has occurred for that item yet. The supplier hasn’t sent the goods, or the warehouse hasn’t scanned them into the system. It is also possible the “Goods Receipt” box was not checked during the initial order setup.

The system says “Purchase order does not exist”

Double-check the number for typos. If the number is correct, the order might have been created in a different SAP client or deleted from the database. Users should verify the document number with the person who created the request.

Before You Start

• Obtain the specific 10-digit purchase order number from your procurement records or a vendor invoice.
• Ensure your SAP user profile has the necessary authorization objects for Display access in the Materials Management (MM) module.
• Log into the SAP Easy Access menu to begin the navigation process.

Step 1: Access the ME23N Transaction

Some users prefer drilling through the SAP Easy Access menu tree, while others prioritize speed by typing directly into the command field. Entering the transaction code ME23N is the most efficient way to pull up the display interface without navigating through multiple folders.

Executing this command opens the Display Purchase Order screen. Because this is a display-only transaction, the system will not lock the record, allowing other users to edit the document if they have the appropriate permissions. This is a standard safety feature in global SAP environments to prevent workflow bottlenecks.

Step 2: Enter the Purchase Order Number

SAP typically defaults to the last purchase order you viewed, which can be confusing for beginners. To find a specific document, you must manually trigger the selection window to input your 10-digit number.

1. Select “Other Purchase Order” – Press the button that looks like a sheet of paper with a small arrow, or use the keyboard. This opens a small dialog box specifically for document selection.
2. Input the 10-Digit PO Number – Type the unique identifier into the “Purchase Order” field. Precision here is mandatory; a single transposed digit will lead to a “Document does not exist” error or show the wrong vendor’s data.
3. Execute the Search – Press the “Enter” key or click the “Other Document” button to pull the data from the database into your active view.

Expected result: The screen refreshes, and the top section of the document updates to show the correct document number, vendor name, and creation date.

Step 3: Review the Initial Display Layout

The standard layout in this transaction is divided into three distinct functional areas. The Header contains overarching data like the legal entity and currency, while the Item Overview acts like a summary table for every product or service requested from the supplier.

Below these, the Item Details section provides the granular data needed for inventory management, such as the specific material group table in SAP that categorizes the items. The system automatically populates these sections based on the purchase order’s current status in the supply chain. Understanding how these sections interact is a prerequisite for interpreting the more complex document history that tracks goods receipts and payments.

Troubleshooting Common Issues

Document Does Not Exist

This usually happens if the PO number was entered incorrectly or if the document was archived. SAP numbers are strictly 10 digits; verify you aren’t missing leading zeros if you are copying from an external spreadsheet.

Transaction Opens in Change Mode

If the screen allows you to type into fields like “Quantity” or “Price,” you are likely in ME22N by mistake. Exit immediately and re-enter ME23N to ensure you are in a safe, display-only environment that won’t accidentally alter procurement data.

Before You Start

• Verify you are in the correct SAP client (e.g., Production or Quality Assurance).
• Identify the vendor name or code to cross-reference with the display.
• Ensure your user role has authorization for the Organizational Data views.

Step 2: Decoding the Purchase Order Header Data

In a standard implementation, the header functions as the legal “envelope” of the document. While item details specify what is being bought, the header dictates the rules for the entire transaction. If the Company Code is wrong, the accounting department cannot pay the invoice, regardless of how accurate the line items are.

The reader should look for the Org. Data tab first. This area identifies the Purchasing Organization, which is the unit responsible for negotiating terms, and the Purchasing Group, the specific buyer or team managing the order. I have seen many buyers ignore these fields, only to find that their reports are completely empty because they filtered by the wrong group code.

Analyzing Key Header Fields

The Vendor field is more than just a name; it is a direct link to the vendor master data. This connection pulls in the Payment Terms, which determine exactly when the money leaves the company’s bank account. If these terms are not negotiated correctly at the header level, you risk losing early-payment discounts.

Pro Tip: Always check the Document Date in the header rather than the entry date; the document date represents when the legal commitment was made, which is what auditors look for during year-end reviews.

The Header Details also house the Delivery/Invoice tab. This is where the Currency is defined. For global fashion or FMCG companies, a mistake here-such as selecting USD instead of EUR-can lead to massive financial discrepancies during the invoice verification process. You must ensure the Company Code aligns with the legal entity receiving the goods to avoid cross-company billing errors.

Understanding these global conditions is mandatory for any supply chain manager. These settings act as the foundation for the specific logistics data found in the MARC table in SAP, which governs how materials behave at the plant level. Getting the header right ensures that the rest of the document follows the correct business logic.

Expected Result

The reader will see the top section of the screen expand to show the vendor’s address, the purchasing organization’s details, and the agreed-upon payment terms. All fields should be greyed out, confirming the user is in a safe display mode that does not lock the record for others.

Correctly interpreting this data allows a user to verify the high-level parties involved before moving into the specifics of quantities and prices. This step confirms the “who” and “how” of the procurement process, setting the stage for the granular “what” found in the individual line items.

Before You Start

• Confirm you have already navigated to the ME23N transaction as previously discussed.
• Ensure a specific purchase order is currently displayed on your screen.
• Locate the Item Overview and Item Details sections, which sit below the header area.

Step 1: Locate the Material and Quantity in the Item Overview

The Item Overview acts like a summary table where every row represents a different product or service being bought. You need to identify the Material Number, which is the unique identifier linked to the Material Master table in SAP. This ensures the system knows exactly which physical item is being moved through your supply chain.

Right next to the material description, you will see the Order Quantity and the Unit of Measure (such as PC for pieces or KG for kilograms). I have seen buyers make the mistake of ordering “10” without checking the unit; if the unit is “Boxes of 100,” you just bought 1,000 items instead of 10. Always verify these two fields together.

Expected result: You can see a list of all items, their descriptions, and exactly how many of each have been requested.

Step 2: Verify Pricing and Valuation

Once you select a line item, look at the Net Price field. This value represents the cost per unit after any initial discounts but before taxes or freight charges. SAP calculates the total value of the line by multiplying this price by the quantity you just verified.

In my time at Accenture, I noticed that price discrepancies here are the number one cause of invoice blocks later on. If the price in this field doesn’t match your contract, the finance department will have a headache when the vendor sends the bill. This price is the financial truth for this specific line.

Step 3: Confirm Logistics and Destination Data

Every item needs a home, which is why the Plant and Storage Location fields are mandatory for physical goods. The Plant represents the broad site (like a factory or retail store), while the Storage Location identifies the specific warehouse bin or backroom where the stock will be placed upon arrival.

You must also check the Delivery Date for each individual line. While the header has a document date, individual items might have different arrival schedules based on vendor lead times. This date is what the production team uses to plan their work, so it must be realistic.

Key Fields to Check for Every Line Item

• Material Number: The technical ID for the product.
• Net Price: The cost per unit in the PO currency.
• Plant: The physical location receiving the goods.
• Storage Location: The specific area within the plant for inventory.
• Delivery Date: When the vendor is legally expected to deliver this specific item.

Checking these details ensures the “what, where, and how much” of the order is correct before the goods actually hit the receiving dock. However, knowing what you ordered is only half the battle; you also need to know if the vendor has actually sent the items or if the warehouse has processed the paperwork.

Before You Start

• Ensure you have the specific purchase order displayed in the ME23N transaction.
• Verify that the item you want to track is selected in the “Item Overview” section.
• Confirm that at least one follow-on activity, such as a warehouse delivery, has occurred.

Step 1: Locate the Purchase Order History Tab

Decide whether you need to see if the warehouse actually received the goods or if the vendor has been paid yet. To find these answers, look at the Item Details section at the bottom of the screen and click on the Purchase Order History tab.

This tab only appears after a follow-on document, like a Goods Receipt (GR) or an Invoice Receipt (IR), is posted against the line item. If the tab is missing, it means no physical or financial movement has been recorded in the system yet.

Key Takeaway: The history tab acts as a real-time audit trail; if it is blank or missing, your supplier likely hasn’t delivered the items or the warehouse hasn’t processed the paperwork.

In high-volume environments like SAP Retail, checking this tab is the fastest way to resolve disputes between the buyer and the vendor regarding missing stock.

Step 2: Interpret Goods and Invoice Receipts

Analyze the list of documents to see the chronological progression of the order. Each entry provides a specific Material Document number for warehouse movements or an Accounting Document number for payments.

Pay close attention to these specific indicators:

• Movement Type 101: This signifies a standard goods receipt where items entered the Plant.
• Invoice Receipt (IR): This entry shows the financial value the vendor billed for the specific quantity.
• Quantity and Value: Compare the “Quantity Received” against the “Quantity Invoiced” to ensure they match.
• Cancellations: Look for movement types like 102 or 122, which indicate the warehouse sent items back or reversed a mistake.

Expected result: You will see a line-by-line breakdown of every time someone touched this order after it was sent to the vendor.

Step 3: Identify Process Discrepancies

Spotting out-of-sync processes is where the real value lies for a procurement professional. If you see an Invoice Receipt without a corresponding Goods Receipt, you have a major issue: the company is paying for items it hasn’t physically received.

These discrepancies often cause invoice blocks, preventing the vendor from being paid on time. By reviewing the dates and quantities in this history, you can pinpoint exactly where the supply chain broke down. This level of detail is much more granular than the high-level data found in a source list table in SAP, as it reflects actual physical movement.

Troubleshooting Document History Issues

The History Tab is Missing

This usually happens because the vendor hasn’t shipped the goods yet or the warehouse clerk hasn’t entered the receipt into the system. It is not a system error; it is a lack of activity.

Quantities Do Not Match

If the “Total Goods Received” is higher than the “Total Invoiced,” the vendor might have under-billed you, or an invoice is still sitting in a clerk’s inbox. Check the Delivery/Invoice tab to see if the “Final Invoice” indicator was accidentally flipped.

Conclusion

Mastering the ME23N transaction and list reports turns a confusing mess of data into a clear map of the supply chain. A purchase order is not just a digital piece of paper; it is a legal contract that dictates when goods arrive and when money leaves the company. If a user cannot find the document history or fails to check the header status, they risk missing critical delays that stop production or leave retail shelves empty.

• ME23N is the single source of truth for individual document details, allowing users to toggle between the header, item overview, and item details to see exactly what was ordered.
• The Purchase Order History tab acts like a tracking number, showing every receipt of goods and every invoice tied to that specific order line.
• List transactions like ME2L or ME2N provide the “big picture” view, helping users identify which vendors have not delivered or which orders are still open across an entire plant.
• Header data controls the whole document, including the currency and vendor terms, while item data handles the specific quantities and delivery dates for each product.

Users should log into their SAP system today and run transaction ME2L using their plant code to identify any purchase orders that are past their delivery date. They should then drill down into one specific order using the “Display Document” icon to practice navigating between the different data levels. Effective operations depend on knowing exactly where a shipment sits at any given moment.

Speed in SAP comes from knowing which screen holds the answer before the system even loads.