Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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 with Redwood for Oracle Cloud HCM   Begin Now
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.

Guidance on Job Requisition Approval Setup

in Recruiting, Opportunity Marketplace 4 comments

Requirement:

Details of "Project" and the list of approvers is coming from a third party system. There are 2 levels of approvers for each project. While initiating the job requisition appropriate project needs to be selected and based on the selection approvals need to be sent to approvers identified against it. Hiring manager's can initiate requisition for each project they work on.

Challenges:

1) No specific pattern has been identified by business in identifying the approvers for any project

2) Currently we are populating list of Projects in the "Job Function" SRF field. To use "AOR" approach these job functions needs to be tagged to "Hiring Manager's" job. Which is not feasible since a hiring manager can initiate requisition against multiple projects and only one Job Function can be tagged to any job. Also, Jobs are generic and are tagged to multiple Hiring Managers.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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