Approval rule silently skips a reorganized cost center
Acme Industrial has been live for six months in three business units: US Operations (requisitioning), Shared Services (procurement), and Canada. The requisition approval rule set is amount-based: up to $4,999 auto-approves; $5,000-$49,999 routes to the Cost Center Manager approval group; $50,000 and above adds the VP Procurement group. The Cost Center Manager group is maintained from position hierarchy, but 12 cost-center manager positions became vacant after a restructuring. Users now report that $8,000-$20,000 requisitions sit at Pending Approval with no assignee, while a $3,200 requisition with an overridden cost center auto-approves. A $62,000 requisition shows only the VP Procurement approver and skips the cost-center step. The audit team wants no requisition to bypass cost-center review and wants evidence that approvals are not silently dropped.
1. Diagnose why the $8,000-$20,000 requisitions have no assignee and why the $62,000 requisition skips the cost-center step. What evidence would you inspect in Oracle Procurement?
Read the worked answer
The two symptoms are probably different failures. For the mid-range requisitions, the rule is firing and routing to the Cost Center Manager approval group, but the group resolves through position hierarchy entries whose incumbents are vacant. Oracle does not automatically promote a vacant position to the next manager unless the rule is deliberately built with a supervisory hierarchy or escalation path. The task becomes unassigned, so the requisition stays Pending Approval. Inspect the approval rule definition, the group membership, the position hierarchy, and the approval history/audit trail for the affected requisitions.
For the $62,000 requisition, the cost-center stage is either not being generated or is being skipped. Possible causes: the rule condition tests a requisitioning business unit or cost-center segment that changed after the cost center was overridden; the approval group has no active members and the rule is set to skip when no approver is found; or a later rule replaces the earlier approval list. Check rule order and stop-on-first-match behavior, the generated approval list, and whether the VP stage was configured as a separate rule that does not include the cost-center group. Also confirm that the $3,200 auto-approval is expected for that amount and is not being triggered by the override.
2. Design a configuration fix that preserves cost-center review without depending on 12 vacant positions. What should change in the approval group and escalation setup?
Read the worked answer
Do not simply add named users to the group; that recreates the same single-point-of-failure. Replace the position-only group with an active job-based or role-based approval group, for example Cost Center Manager as a job role, and include a named fallback group such as Procurement Operations. Set the group to require one response, not all responses, so the fallback can act.
Configure an escalation after a short inactivity period, such as two business days, to the next supervisory level or to the fallback group. Make sure the rule does not skip the cost-center stage when no approver is found; if skip is allowed, the requisition can bypass review. Keep the VP Procurement stage as an additional approver for $50,000 and above, and test that the stage is appended rather than replacing the cost-center stage. Finally, add a monitoring report for approval tasks with no assignee and for requisitions whose approval history lacks a cost-center action.
3. What test plan would prove the fix works before it is promoted to production?
Read the worked answer
Build test requisitions that cover the boundaries and the failure modes: $4,999, $5,000, $49,999, $50,000, and $62,000, with and without a cost-center override. For each, submit as a requester in US Operations and verify the generated approver list in the approval history. Confirm that the $5,000-$49,999 cases create an active cost-center task, that the $50,000+ cases show both cost-center and VP tasks, and that no case shows an unassigned task.
Then test vacancy by leaving the primary cost-center position unassigned in the test hierarchy and confirm the fallback group receives the task. Test escalation by not acting on a task and confirming it moves after the configured interval. Also test a reassigned or inactive approver, because group membership changes can behave differently from hierarchy changes. Capture screenshots of the rule, group, hierarchy, and approval history and attach them to the change record for audit.