Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A purchase requisition is an internal request to buy something. ME53N displays its details and status in classic SAP, helping distinguish an existing request from a completed supplier 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 ME53N: Read a purchase requisition before creating another one
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.

Classic ME53N requisition display and supported S/4HANA document relationships. Approval models, item controls, source assignment, partial processing and available references depend on release/configuration.

Reviewed the cited official SAP indexed documentation excerpts on 14 November 2026. Direct Help Portal opens did not consistently expose readable page text. This is documentation-based teaching, not customer-system execution. All document identifiers, quantities and outcomes in the worked case are illustrative; installed release, edition, configuration and authorizations require local verification.

A MANUFACTURING EXAMPLE

Check a maintenance-spares request

Check the existing request

Requisition: Internal request 1001. Requested quantity: 10 spare parts. Follow-on order: Inspect actual reference. New request: Check for duplication first
What to notice: A requisition’s existence does not itself mean the supplier has received an order.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Requisition
Internal request 1001
Requested quantity
10 spare parts
Follow-on order
Inspect actual reference
New request
Check for duplication first

A REAL SCREEN TO RECOGNIZE

SAP’s RAP workshop shopping-cart application illustrates requests for purchasing. This is a custom workshop app, not the classic ME53N screen. Recognize the requested items and actions; creating a request and creating a supplier order are separate business stages.

SAP’s RAP workshop shopping-cart application illustrates requests for purchasing. This is a custom workshop app, not the classic ME53N screen. Recognize the requested items and actions; creating a request and creating a supplier order are separate business stages.

View the original SAP example ↗ · License

© 2025 SAP SE or an SAP affiliate company and abap-platform-rap110 contributors. Apache-2.0 (repository REUSE annotation). Reproduced unchanged for educational commentary. This is a source example, not a capture of your system.
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.
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.

Internal request → Requisition status → Follow-on purchasing. Conceptual diagram for SAP ME53N: Read a purchase requisition before creating another one.
Apply the idea: A maintenance buyer receives another request for spares even though an earlier requisition may already be partly covered by a purchase order.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. Check a maintenance-spares request

    A maintenance buyer receives another request for spares even though an earlier requisition may already be partly covered by a purchase order.

  2. Read the existing demand before requesting it again

    ME53N displays a purchase requisition in relevant classic SAP purchasing processes.

  3. Scope and prerequisites

    The scope is classic ME53N and the cited ERP/S/4HANA purchase-requisition single-screen documentation.

  4. Understand the item’s separate states

    A requisition item expresses what is needed and when.

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.