Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 14 · Approvals and BPM workflow
What breaks: the approval nobody received
Lesson 145 of 177 · 2 min
Three failures, and none of them errors. ONE: A GAP IN THE HIERARCHY. A requester with no supervisor recorded, or a chain that ends before the approval limit. The transaction sits, or is silently auto-approved depending on configuration — and auto-approval is the dangerous half: a control that quietly did not apply, with nothing to distinguish it from one that did. TWO: A RULE MATCHING EARLIER THAN INTENDED. The exception rule never fires because the general one is above it. Everything is approved, by somebody, so nothing looks wrong — and the finance director's threshold has not applied for six months. This is discovered by an auditor rather than by a user, which is the worst way to discover it. THREE: AN APPROVER WHOSE ROLE WAS REMOVED while items were still assigned to them. The tasks remain in a worklist the person can no longer open. The history says the…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 14 · Approvals and BPM workflow
- 1How approvals are actually structured
- 2Approval rules and how they are evaluated
- 3Supervisory and position hierarchies
- 4Parallel, serial and FYI participants
- 5Delegation, escalation and timeouts
- 6Notifications and what they say
- 7Testing an approval rule properly
- 8Diagnosing a stuck transaction
- 9What breaks: the approval nobody received
- 10Lab briefing · Build and break an approval chain