Atlas Diagnostic

SAP purchase requisition diagnostics

A first-pass structure for finding why a purchase requisition cannot be created, approved, or converted to a purchase order.

Reviewed

Core idea

Purchase requisition is the first document in the procure-to-pay chain. It captures internal demand but does not yet commit the organization to a supplier. When a PR is blocked, cannot be created, or fails conversion, the support goal is to identify whether the issue is in master data, account assignment, sourcing, release strategy, or user authorization.

Most PR failures are not system errors: they are missing account assignments, unextended materials, or incomplete release strategies surfacing at the first document in the chain.

Common symptoms

  • ME51N fails to save or shows a hard error.
  • PR is created but cannot be converted to PO (ME59N or ME21N).
  • PR remains in status 'release strategy active' and cannot be approved.
  • MRP-generated PR has wrong plant, quantity, or delivery date.
  • PR account assignment is rejected during posting or conversion.

Likely causes

  • Master data issue: material not extended to plant, supplier blocked, or purchasing organization mismatch.
  • Account assignment error: cost center, WBS element, or GL account is invalid or not open for posting.
  • Release strategy block: the PR value or material group triggers an approval path that is not complete.
  • Source determination failure: no valid info record, source list, or quota arrangement exists for automatic sourcing.
  • Authorization issue: the user lacks authorization to create PRs for the plant, material group, or account assignment type.
  • MRP parameter issue: lot size, safety stock, or planning horizon produced an unexpected PR quantity or date.

Where to check in SAP

  • ME53N — display PR and check status, account assignment, and source of supply.
  • ME59N log — automatic PO creation rejection reasons.
  • ME54N — PR release status.
  • MD04 / MD05 — MRP list to see how the PR was generated.
  • SU53 — authorization check after a failed transaction.

Key tables / transactions / objects

  • EBAN / EBKN — PR header and items.
  • EKKO / EKPO — PO header and items (for converted PRs).
  • AUFK — WBS / internal order master.
  • CSKS — cost center master.

Diagnostic workflow

  1. Identify the PR number and the exact error or status that blocks progress.
  2. Check ME53N for PR details: material, plant, quantity, account assignment, and source of supply.
  3. Verify master data: material plant extension, supplier status, and purchasing organization.
  4. Check release status if the PR is blocked for approval.
  5. Check MRP parameters if the PR was system-generated and has unexpected values.
  6. Test manual PO creation (ME21N) from the PR to isolate conversion issues.

Typical fixes or next actions

  • Correct the account assignment if the cost center or WBS element is wrong.
  • Extend the material to the plant or unblock the supplier master.
  • Complete the release strategy approval if the PR is blocked.
  • Create or update the source of supply if automatic sourcing fails.
  • Adjust MRP parameters if system-generated PRs are consistently wrong.

What to capture first

PR blocks are usually upstream master data or account assignment problems. Capture: PR number, material, plant, error message, account assignment, and whether the issue is isolated or recurring.

When the PR came from MRP

If the requisition was system-generated, treat it as an MRP exception. Verify the exception message in MD04/MD05, then check whether the root cause is a demand signal change, a supply delay, or a planning parameter in the material master. For a full diagnostic frame, see SAP MRP Exception Diagnostics.

Escalation signals

  • Requisitions are stuck across multiple users or plants, suggesting a release strategy or workflow failure.
  • The requested material or service has no approved source, contract, or budget approval.
  • MRP-generated requisitions repeatedly have wrong quantities, dates, or source of supply.
  • The case requires a change to sourcing policy, approval limits, or procurement governance.

Boundaries and non-goals

This page is a diagnostic frame, not a PR configuration guide. It does not cover MRP logic, approval workflow design, or catalog integration. It does not replace SAP's purchasing documentation.

This is not official SAP documentation and not a replacement for system-specific analysis.

Related Atlas Pages