Oracle Fusion Recruiting Cloud: Offer Assignment is Not End Dated When Candidate is Hired which Causes Hired Person to Keep the Person Type of ORA_CANDIDATE
(Doc ID 2835579.1)
Last updated on JUNE 13, 2023
Applies to:Oracle Recruiting Cloud Service - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When an external candidate applies for a job and moves through the stage from a pending worker to an employee, after they become an employee their active pending worker assignments are end dated/set to inactive.
However, during this process, there are also assignments created for the offer (assignment type 'O' and 'OT' associated with the action EMPL_OFFER_CREATE). The offer assignments have not been end dated/set to inactive.
A consequence of this, is that the system person type associated with the Offer assignment is ORA_CANDIDATE. Because the offer assignment has not been Inactivated and end dated, a person who has been hired via Oracle Recruiting may have two person types active, for example:
This can cause issues in some circumstances. For example, a custom context sensitive segment to show certain fields for candidates only, will also show these fields for Employees who have been hired through Oracle Fusion Recruiting because they retain the ORA_CANDIDATE system person type.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document