Purchase requisition versus purchase order: Internal demand and supplier commitment
A maintenance team needs ten spare parts, but a request inside the plant has not yet established a supplier commitment.
START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED
What it is. Why it matters.
A purchase requisition asks the purchasing team to buy something. A purchase order communicates a purchasing request to a supplier or supplying plant, turning internal demand into a later purchasing stage.
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.

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 ERP and supported S/4HANA requisition/order concepts. Approval, conversion, consolidation/splitting, output and special-procurement routes vary by installed process.
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
Turn a spares requirement into purchasing evidence
Request first, then order
Read the example values
- Department need
- 10 spare parts
- Internal document
- Purchase requisition
- Supplier selection
- Buyer chooses source
- External purchasing
- Purchase order
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.
© 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.
Turn a spares requirement into purchasing evidence
A maintenance team needs ten spare parts, but a request inside the plant has not yet established a supplier commitment.
A requisition asks internally; an order directs procurement externally
A purchase requisition expresses an internal requirement for material or services.
Scope and prerequisites
The guide covers classic ERP and supported S/4HANA purchasing concepts.
Understand demand, authorization, ordering and communication
The requisition records what the organization needs.
Turn a spares requirement into purchasing evidence
A maintenance team needs ten spare parts, but a request inside the plant has not yet established a supplier commitment.
Trace the requisition and purchase-order relationship before telling maintenance that the spares have been ordered.
| Reader | Business question | Evidence to carry forward |
|---|---|---|
| Manufacturing buyers and purchasing managers | Turn a spares requirement into purchasing evidence | Trace the requisition and purchase-order relationship before telling maintenance that the spares have been ordered. |
01 A requisition asks internally; an order directs procurement externally
A purchase requisition expresses an internal requirement for material or services. A purchase order is the formal purchasing request or instruction to a supplier or supplying plant. They represent different responsibilities and stages even when a PO item references a requisition item. [1] [2]
An approved requisition does not by itself prove that a supplier was selected, an order was created or the order was communicated. This tutorial follows a ten-spare-part request through purchasing and receipt, then shows how partial coverage and duplicate requests create confusion. The goal is to identify the actual missing stage instead of calling every document “the purchase.”
02 Scope and prerequisites
The guide covers classic ERP and supported S/4HANA purchasing concepts. Requisitions can originate manually or from planning/other applications; orders can follow several permitted paths. Approval models, automatic conversion and output differ by edition/configuration. Contracts, scheduling agreements and special procurement have additional flows.
Collect the business need, requester, material/service, plant, quantity/unit, required date and intended account assignment. Obtain display access to the requisition, related purchasing items, approval evidence, output and receipt history. Proposed creation/conversion tests require an approved training process.
Do not assume every PO must have a requisition or every requisition must become a standard PO. Identify the permitted procurement route in the actual organization. The example uses a simple referenced PO so the relationship can be traced clearly.
03 Understand demand, authorization, ordering and communication
The requisition records what the organization needs. Its approval expresses the relevant internal authorization. Source selection identifies how procurement should fulfill it. The PO specifies the supplier-facing commercial and delivery requirement, and communication establishes what instruction was sent. Supplier acknowledgement and receipt follow in their own stages. [1] [2]
These facts require separate evidence. A saved PO number is not proof of supplier receipt, and a supplier acknowledgement is not a posted goods receipt. Keeping the stages separate lets a requester ask the right team for action.
SAP’s purchasing definitions distinguish requisition and order, while the actual process can carry references between their items. Use those references instead of assuming documents correspond because their descriptions and quantities look similar.
04 Worked case: ten spare parts due on one date
The maintenance department requests 10 PC of PART-P for plant P100 by 25 November. PR-A item 10 records that need with the approved recipient/account-assignment context. A buyer confirms the source and creates PO-A item 10 for the ten pieces, referencing PR-A/10 in the supported process.
The order uses an illustrative price of 50 per PC, giving 500 net before tax, freight and other conditions. The approved PO is communicated through the actual output process. Later, receiving posts six pieces and then four under the correct PO item, with no corrections in this simplified timeline.
The full chain is ten internally required, ten externally ordered, ten eventually received in two events. Approval, output and receipts are distinct evidence. The 500 is an illustrative order net value, not proof of an invoice liability or payment.
| Stage | Document/evidence | Meaning |
|---|---|---|
| Internal need | PR-A / 10: 10 PC | Request for procurement |
| Authorized requirement | Applicable PR approval | Internal permission in actual model |
| External order | PO-A / 10: 10 PC at 50 | Supplier requirement and commercial basis |
| Communication | Actual PO output reference | Instruction processing evidence |
| First receipt | GR-A: 6 PC | Partial received event |
| Second receipt | GR-B: 4 PC | Full ten received in stated fixture |
05 Compare requisition and PO items without assuming equality
A buyer may consolidate, split or otherwise process demand through supported purchasing paths. Therefore inspect actual item references and coverage rather than expecting a one-to-one header relationship. A single PO can cover several internal requests, and one request can have partial follow-on coverage in permitted scenarios.
Quantity, date and assignment can also change through approved processing. Compare the actual current documents and change rationale. An original requisition date may express the requester’s need while a PO date reflects the agreed supplier delivery. A mismatch is a question to investigate, not automatically a system defect.
Commercial value can differ because the requisition estimate and actual PO condition have different purposes. Do not treat the estimate as a final supplier agreement unless the supported process specifically adopts it and the resulting order confirms that treatment.
06 Investigate a request in sequence
The following sequence turns a vague status request into a document-supported next action.
Validate the internal requirement
Confirm PR-A/10, ten PC, P100, date and recipient. Ask whether the need remains valid.
Expected observation: The business requirement is identified independently of ordering.
Read approval and source progress
Establish the active approval model, pending state and actual source assignment.
Expected observation: Authorization and sourcing are not mistaken for supplier instruction.
Follow the purchasing reference
Inspect PO-A/10 and any other follow-on documents. Compare current quantity, dates and account assignment.
Expected observation: Existing coverage is known before creating more supply.
Verify communication
Review the supported output result and supplier reference/acknowledgement where relevant.
Expected observation: Order creation is separated from successful communication.
Reconcile receipt evidence
Read six plus four PC and any corrections through PO history.
Expected observation: The ten-piece physical/document outcome can be explained.
07 Partial coverage creates a different remaining-demand question
Change the case so PO-A covers only six of the ten requested pieces. Under the no-other-coverage worksheet assumption, four are not covered by that order. Whether they remain active demand depends on current item controls, other documents and the business decision.
If the requester raises another ten-piece request while the six-piece order remains active, later purchasing can create sixteen pieces of supply against the original ten-piece need. The duplication begins with misunderstanding coverage, not with receipt processing.
Record whether the remaining four will be ordered separately, added through a supported change or closed because the need changed. Do not derive the operational status solely from ten minus six; inspect the installed completion and follow-on rules.
08 Approval models and output controls are independent
A classic release strategy and flexible workflow have their own configuration and evidence. Establish which approval mechanism applies to the requisition and which applies to the PO. Approval of one document does not automatically establish approval of the other.
Likewise, an approved PO can await output processing or encounter a communication error. Inspect the actual supported output state and reference before claiming that the supplier is late. A supplier cannot act on a local number they never received.
After a change, determine whether reapproval or renewed communication is required in the installed process. The latest local quantity/date and the supplier’s last received version can differ legitimately until the configured change process completes.
09 Account assignment and receipt destination must match purpose
Stock procurement and direct consumption have different intentions. The requisition’s recipient and category explain the need, while the resulting PO and receipt carry their supported posting context. Review what was actually adopted or changed.
A maintenance spare held for general stock is different from a service or supply purchased specifically for a cost object. Entering a convenient recipient merely to complete a required field can misstate the intended treatment.
After receipt, inspect the actual destination/category and accounting evidence where relevant. Ten ordered and ten received does not prove the goods are in unrestricted stock or that the supplier invoice has been posted. Follow the relevant next document rather than extending the PO’s meaning.
10 Troubleshooting decisions
Choose the next owner from the missing stage. Replacing the requisition is not a universal solution to delay.
| Observation | Question | Next evidence |
|---|---|---|
| PR approved, supplier knows nothing | Was a PO created and communicated? | Follow-on item and output |
| No PO found from requester email | Does PR already carry a reference? | Actual PR item status/history |
| Ten requested, six ordered | What covers or closes the remaining four? | All active follow-on documents and item controls |
| PO date later than PR date | Was supplier timing agreed? | Current order/change and confirmation evidence |
| Ten received, invoice unresolved | Is the issue now invoice matching/payment? | Logistics invoice and accounting documents |
| New PR duplicates old need | Was existing supply reconciled? | Original requirement and active coverage |
11 Common mistakes and useful language
Avoid saying “purchasing complete” without naming the stage. Prefer “PR approved, source pending,” “PO created, output failed” or “ten received, invoice under review.” Each statement directs the next action.
Do not recreate a PO after an uncertain interface response until existing documents are searched. A timeout can occur after creation. Duplicate orders can both be communicated and create real supplier commitments.
Do not use receipt quantity as proof of supplier payment. Receipt, invoice posting, payment release and payment execution each have different documents and states. A clear explanation preserves those boundaries while showing their relationships.
12 Verification exercises
For the positive worksheet check, trace PR-A ten to PO-A ten and receipts six plus four. Verify item references, units, commercial basis and communication evidence separately. In training, capture actual document identities and status labels.
For the negative check, leave the PO uncommunicated and explain why PR approval does not prove supplier delay. Then retain a six-piece active order and introduce a new ten-piece request to demonstrate sixteen-piece overbuying risk.
For boundary checks, test a PO created without a PR under an approved route, several PR items consolidated into an order and a changed/canceled residual requirement. Expected behavior must follow the installed process; the simple fixture is not a universal coverage algorithm.
13 Questions and the handover
Is a requisition a supplier commitment? It is internal demand; inspect the actual external purchasing document and communication. Must a requisition always create a PO? The permitted sourcing/procurement route decides. Does a PO prove the goods arrived? Only receipt evidence establishes the posted receiving event.
A useful handover names PR-A/10, the ten-piece need, current approval/source state, PO-A/10 coverage, communication reference and six/four receipts. If something is missing, state that stage and its owner rather than asking the requester to start over.
Continue with ME53N, purchasing worklists and PO history to inspect the internal request, identify candidate orders and reconcile follow-on events at item level.
Related services and next steps
Primary sources
Found this useful?
Share this guide with your network, or leave a like.
Your like is saved in this browser.