Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 14 · Approvals and BPM workflow
Supervisory and position hierarchies
Lesson 139 of 177 · 2 min
Routing up a chain that HCM owns is the most common approval design and the one with the most external dependencies. A supervisory hierarchy routes to the requester's manager, then theirs, until a condition is met — a number of levels, or an approval limit. A position hierarchy does the same up positions rather than people, which is more stable when individuals move and requires the position structure to be maintained. WHAT HAPPENS WHEN THE CHAIN HAS A GAP is the failure you will meet. Somebody has no manager recorded, or their manager left and the assignment was not updated, or the chain runs out before the approval limit is reached. The task cannot be routed. Depending on configuration it is auto-approved, sent to an administrator, or simply sits. The requester sees "pending approval" and nobody has it, which is Lesson 8. THAT GAP IS AN HCM DATA PROBLEM, NOT…
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