You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

How to Skip an Approval Level based on Management Hierarchy of Employee Assignment

edited Mar 23, 2024 4:11AM in Human Capital Management 1 comment

Summary:

We have an approval requirement where the Project Manager(s) need to be the first level of approval, then the Line Manager, then the HR Representative. Employees can have up to 3 project managers assigned at one time for each project they are assigned.

In attempts to meet this, we have built 3 levels of project managers in the Supervisor Type Lookup (PM1, PM2, PM3). Then, within the approval rules, the first level of approval is the Project Manager 1, then PM2, PM3, Line Manager, and finally HR (Illustrated below).


The issue we are trying to solve is: what if an employee is only assigned

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!