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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Not Running Load Candidate into Candidate Table - Is it recommended
Summary:
Hi Team,
We have a requirement where 2 LE's are going to use the ORC system. Clients do not want Particular Staff's candidate profile to be created in ORC so approach we are thinking to take is given below:
1. Not to run the Load Candidate into Candidate table process so that none of the candidate's profile gets created.
2. To create the candidate profile using HDL load by linking with employee record for whom candidate record to be created.
Or
1. Run the process and delete the Candidate profile later?
We would need oracle's advice on below pointers:
1. So can you please let us know the recommended approach as OOTB process do not provide an option to filter employees?
0