Requisition and purchase order approval problems are almost always rule resolution problems. The approval rule evaluates conditions against the requisition and resolves an approver from a hierarchy. Where the hierarchy has a gap, the condition matches nobody, or the resolved approver has left, the request waits indefinitely with no error raised anywhere.
What problem does this solve?
A requisition sitting in approval with no visible error is the most common symptom. The rule resolved to an approver who cannot act — someone who left, an unpopulated supervisor field, or a position with no holder.
Approvals routing to the wrong person indicate rule conditions that do not reflect the current delegation of authority, often because limits were set once and never revised.
Purchase orders not created after approval usually means the requisition completed approval but failed at document creation — missing supplier site, inactive item, or an unavailable buyer assignment.
How the solution works
We inspect the resolved approver list rather than resubmitting. That shows immediately whether the rule found nobody, found the wrong person, or found someone unable to act.
Rules are then corrected with an explicit fallback approver and escalation period, because a rule that can resolve to nobody will eventually do so again.
- 1Look at the current stage and the resolved approver list for the specific document.
- 2Confirm the supervisor or position hierarchy is populated for everyone in the routing path.
- 3Verify the conditions match the requisition attributes and the current authority limits.
- 4Check the approver is active and has any required delegation configured while absent.
- 5Correct the rule and hierarchy so the next requisition routes correctly.
- 6Ensure every rule has a fallback approver and a defined escalation period.
Limitations & prerequisites
- Approval rules resolve against HR hierarchy data; where that data is incomplete, procurement cannot fix routing alone.
- Reassigning an individual document clears the immediate block but leaves the rule defect in place for every subsequent requisition.
- Authority limits usually reflect a delegation of authority document, so changes are a governance decision rather than a configuration one.
- Complex conditional rules become difficult to reason about; each additional condition increases the chance of a combination that matches no approver.
- Where requisitions are created by integration, missing attributes upstream produce routing failures that look like rule problems.
FAQ
The rule almost certainly resolved to somebody who cannot act — a person who has left, an empty supervisor field, or a position with no current holder. Inspect the resolved approver list rather than resubmitting; resubmission repeats the same resolution.
Either the requisition did not complete approval, or it completed and purchase order creation failed on missing setup: an inactive supplier site, an unavailable item, or no buyer assignment. Check which of the two stages actually ended.
Rule conditions no longer match the delegation of authority, usually because limits or the organisational structure changed and the rules did not. Review the conditions against the current authority document.
Yes, and it unblocks the document. But treat it as a symptom: if the same reassignment happens repeatedly, the rule or hierarchy is wrong and should be corrected.
Give every rule a fallback approver and an escalation period. Most stalled requisitions are rules that resolved to nobody with no timeout to catch it.
If rules resolve through the supervisor hierarchy, updating HR data is usually sufficient. Where rules name individuals directly, every departure becomes a configuration change — which is a good argument for not naming individuals.
Tell us the module, the release and the exact symptom.
Send the module in scope, your Fusion release or EBS version, and the exact error text or symptom with a screenshot where you have one. We reply with a written assessment: the likely cause, what we would check first, and whether it is a configuration fix, a data fix, or a defect that needs an Oracle service request. When Swedish Technology can help, we scope the remediation with effort and sequence before you commit to anything.
Request an Oracle AssessmentSources & evidence
- Oracle Help Center — Cloud Applications documentation — module setup, subledger accounting and period-close reference
- Oracle Help Center — all product documentation — database, middleware and infrastructure reference used for error diagnosis
- My Oracle Support — patches, known-issue notes and service requests; Oracle account required
Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement unless stated on the vendor's official pages.