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
Get Started: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

Requisition Approval Visibility

Summary:

Creating a Requisition Approval path that is robust

Content (please ensure you mask any confidential information):

Our current Requisition approval path is pretty much straight forward. for example, if the Requisition is an add to headcount, the approval path is, HR Rep -> Hiring Manager one over -> Hiring Manager 2 over, Else approved. One idea is to base the approval path on 'role' approvals vs hierarchy, i.e. HR, VP, SVP and or contextualize approvals by Generic title/Job Families/or Template. Is this possible? What are others doing to put more visibility around Req. approvers?

I saw that there is a way to add approvers ad hoc so this could be one solution.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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