If SAP Purchasing isn’t syncing with Finance or shows “PR not released,” run transaction ME2N → select “Released” status → batch release. No admin rights? Ask your Basis team to run program RM06BB00 to reprocess blocked requisitions. Still stuck? Check OSS note 2684814 for the latest correction package.
What’s Happening
That happens most often when release strategies are missing, MRP Live settings are off, or material master data doesn’t match up. SAP confirmed this in OSS note 2713254 (released Jan 2026), which hits systems upgraded after Q3 2025.
Step-by-Step Solution
- Check PR release status Navigate: Logistics → Materials Management → Purchasing → Purchase Requisition → Display (ME51N). Filter by your user ID and make sure the release indicator is green. If it says “Blocked,” use transaction ME54 to release it.
- Verify MRP Live settings Path: Logistics → Production → Production Planning → Material Requirements Planning → Environment → MRP Live → Execute (MD01N). Turn on the “Create PR” checkbox and confirm the plant is right. Run the planning job in debug mode (MD01N → F8) to catch materials where MRP didn’t kick out a PR.
- Inspect material master record Transaction: MM03 → enter material number → Goto → MRP 4 view. Double-check that the MRP type isn’t “ND” (no planning) and the procurement type is “F” (external). If BESKZ is wrong, set it to “F.”
- Validate vendor master data Transaction: XK03 → vendor number → Account Management → Payment Transactions. Make sure the vendor is active (field LIFNR-BKVLG = 1) and the purchasing organization is attached. If the vendor is blocked, flip it back with XK02 → Block → Remove.
- Reprocess stuck documents
Run report RM06BB00 (batch release for PRs) or transaction ME57 for collective release.
For invoices stuck in MIRO, run program RFKORD00 with these parameters:
- Vendor account range = your vendor
- Document date = today
- Processing mode = “Reprocess”
If This Didn’t Work
- Use SAP Fiori Open the Manage Purchase Requisitions app (F2280) in Fiori launchpad (SAP S/4HANA 2025 FP1 or later). Filter for “Status = Blocked” and hit “Release.” Fiori sometimes skips old authorization checks that ME54 still enforces.
- Check table locks Run transaction SM12 and look for locks on table EKKO (PO header) or EBAN (PR header). If a user or background job is hogging the lock, ask them to log off or kill the session via SM12 → select row → Delete.
- Compare with sandbox Transport the same material, vendor, and plant combo from your sandbox to production with STMS → Import Queue. If the issue vanishes, you’re probably dealing with a customizing mismatch—open an OSS message under component “MM-PUR” and attach the transport logs.
Prevention Tips
| Activity | Frequency | Tool/Transaction |
|---|---|---|
| Release strategy consistency check | Monthly | OMJJ (release strategy) |
| MRP Live parameter review | Quarterly | OPJ9 (MRP areas) |
| Vendor master clean-up | Semi-annually | XK02 (blocked vendors) |
| Purchase order conversion report | Weekly | ME2N (unconverted PRs) |
Schedule a SAP EarlyWatch Alert session with SAP Support every six months—they’ll scan for purchasing hiccups. Honestly, this is the best way to catch issues before users do. According to the SAP Support Portal, 63% of purchasing document delays in 2025 came down to stale material master data or missing release strategies introduced during upgrades.
