Oracle Recruiting mental model
ConceptfoundationThe scope Oracle Recruiting configures, its prerequisites and offering structure, and the boundary at hire where Core HR takes over.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That Recruiting owns the worker record. It does not; the worker record begins at hire in Core HR.
- That recruiters can opt in to the offering. The opt-in is performed by the Application Implementation Consultant role.
Recall it
Name the seven functional areas of the Recruiting and Candidate Experience offering.
Recruiting and Candidate Experience Management, Job Requisitions, Candidate Experience, Candidate Job Applications, Job Offers, Source Candidates, Recruiting Assistant.
Memory hook: Management, Requisitions, Experience, Applications, Offers, Source, Assistant.
Rests on ORC-OFFERING-004.
Taught in
- The Oracle Recruiting mental modelWhat Oracle Recruiting is for, what it stops at, which offerings and prerequisites it has, and the one identity constraint that surprises every implementer.
- Job Requisitions Over REST: Grants, Roles and What the Page Will Not Tell YouWhich duty role grants what on the recruitingJobRequisitions resource — and why the same role can hold both read-only and full privileges, and why this page is not where you learn the endpoint.
Related
- Terminology glossary — what a term means, and what people get wrong when they use it