SAP MM Purchase Requisition to Purchase Order: Controls, Approvals and Common Errors

Follow the requirement through the purchasing handoff

The move from a purchase requisition to a purchase order is a handoff between an internal need and a supplier-facing commitment. The buyer must preserve the requirement while checking the source, quantity, timing and commercial terms. An incomplete handoff can create the wrong order even when the system allows a document to be saved.

This guide follows a fictional requirement through partial conversion and a price-unit check. It also separates document creation, approval and supplier output, because success at one checkpoint does not establish completion of the others. Use the examples to explain your checks rather than merely repeat screen entries.

Core concepts to learn

Build a practice scenario

1. Step 1: Write a 100-piece requirement with its plant, required date and agreed price basis.
2. Step 2: Prepare a 60-piece order worksheet referencing the requisition and calculate its net value independently.
3. Step 3: Document the remaining 40-piece need and reconcile any later follow-on order without double counting.
4. Step 4: Inspect creation, approval and output as separate checkpoints, recording the evidence for each.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

Separate requirement, sourcing and order approval

A purchase requisition expresses an internal need; a purchase order records the purchasing agreement with a supplier. Treating conversion as a simple copy operation misses the buyer’s checks. Confirm the required quantity and date, the intended receiving location, the source and the relevant account assignment before creating the follow-on document. A supplier name alone is not evidence that the source is valid for the requirement.

Approval also belongs to a specific document and process. An approved requisition does not prove that its resulting purchase order has completed every required approval. SAP supports different release approaches depending on the edition and configuration. Its purchasing course describes classic release procedures and flexible workflows, with purchase-requisition workflows possible at overall or item level. Establish which process applies before interpreting a status or looking for an inbox task.

Worked example: a partial conversion without losing the remaining need

Use a fictional requisition for 100 pieces required on 20 October. After review, the buyer orders 60 pieces from the selected supplier for that date and leaves 40 to be sourced separately. Record the original requisition item and its reference in the purchase-order item. The exercise is successful only if another learner can explain which quantity is ordered and which requirement remains to be addressed.

Now add a second purchase order for 40 pieces. Reconcile the follow-on quantities back to the original 100, checking their current status and any cancellations or changes. Do not count an obsolete order and its replacement as two active commitments. This reconciliation is a practice control, not a promise that every report displays remaining quantity in the same way.

For a price check, assume the agreed price is ₹2,000 per ten pieces. The 60-piece order has a basic net value of ₹12,000 before taxes or additional conditions. Entering ₹2,000 as the price per one piece would produce ₹120,000. The lesson is to check the price unit together with the number, rather than considering the displayed price in isolation.

Use a small pre-order checklist

Start with identity: requisition item, material or clear description, plant, delivery address and purchasing organisation. Continue with quantity, order unit, delivery date, supplier and commercial conditions. If the requirement is for direct consumption, verify the relevant account-assignment details with the responsible owner. Do not assume every stock purchase needs a cost centre, or that one account-assignment pattern applies to every item category.

Then inspect the master-data context. SAP S/4HANA manages supplier information through business partners, with purchasing and company-code information maintained at their relevant organisational levels. A supplier that exists in one context may still lack the data needed for the intended process. Investigate the exact message rather than repeatedly re-entering the same supplier.

Finally, record what changed during conversion. A changed delivery date, quantity or commercial term should be explainable against the requirement and agreement. Keep this note factual: what was changed, why, who confirmed it and which document now represents the current decision.

Diagnose common failures without bypassing controls

The requisition is not available for conversion

Confirm the document and item number, selection filters, organisational context and current processing status. Determine whether it is already covered by a follow-on order, marked for deletion, incomplete or waiting for an applicable approval. The actual cause must come from the document and message evidence; do not assume that every missing item is an authorisation problem.

The approver does not see a task

First identify the approval mechanism and the workflow instance, if one is expected. Check whether the document meets the configured start conditions and whether a responsible recipient was determined. Distinguish a document awaiting approval from one for which the expected workflow never started. Provide the document number, status, time and observed message to the workflow owner.

The order is saved, but the supplier has not received it

Saving, approval and output are separate checkpoints. Inspect the relevant output status and communication evidence for the system in use. Avoid creating another order merely because an email or printout is missing; that can duplicate the commercial requirement.

Build a repeatable handover exercise

Give a partner the fictional requisition, agreed price basis and required date. Ask them to create a proposed order worksheet, find the price-unit trap and explain the remaining 40-piece requirement after the first conversion. Then provide an exception card saying the order is saved but its approval is incomplete. A strong answer identifies the next responsible check rather than claiming the supplier can already deliver.

Keep the requisition and order references, quantity reconciliation, price calculation, status evidence and exception explanation together. End with one unresolved question if configuration evidence is unavailable. In an interview, being precise about what you checked is more convincing than naming a transaction and guessing what happened behind it.

Official SAP references

• SAP Learning: Setting Up Flexible Workflows in Purchasing
• SAP Learning: Creating Business Partners

Frequently asked question

What should a beginner practise after learning SAP MM purchase requisition to purchase order?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.