Implement project role based custom approval hierarchy using AME - part 1 - challenge

• If you use Oracle's PA module to approve projects, more likely than not you have a custom approval hierarchy and leverage the PA project workflow.
• Let's say we have a  multiple level hierarchy based on business unit (Company), project type (Capex/Non-Capex), budget type (Budgeted/Non-Budgeted), project amount (Financial plan), project role (Key members) and its approval limit. Here is a mockup approval chain for budgeted capital project in one company:

Project manager: mandatory,  $0

Operation: optional, $0

Manager: mandatory, $1,000,000

Director: mandatory, $5,000,000

Operation director: optional, $0

.....

Finance Department (Review), mandatory, $0

Note: if a person holds "consecutive" position in the hierarchy, notify only once.