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 MARCH 06, 2024

Applies to:

Symptoms

Problem Description:

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:

Returns:

SYSTEM_PERSON_TYPE (ORA_CANDIDATE)
SYSTEM_PERSON_TYPE (EMP)

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.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.