Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 14 · Approvals and BPM workflow
Diagnosing a stuck transaction
Lesson 144 of 177 · 2 min
"Pending approval" and nobody has it. Three places to look, and three usual causes. WHERE TO LOOK. The TASK HISTORY on the transaction — it shows every participant the task was routed to, when, and what they did. The WORKLIST of the person it should have reached, which answers whether it arrived. And the approval rules, read as the engine reads them, to see which rule matched. THE THREE USUAL CAUSES. ONE: a gap in the hierarchy. The chain could not be resolved, so the task went to an administrator, or nowhere. Lesson 3, and the fix is HCM data. TWO: it reached somebody who cannot act on it. The approver's role was removed, or they left, or they never had access to the page the task opens. The task is assigned and it is invisible to its assignee, which is the worst version because the history says it was…
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