Post B.RUP.10: Assignment Primary Flag Disappears When Delete Future Primary Assignment

(Doc ID 2341150.1)

Last updated on JANUARY 22, 2018

Applies to:

Oracle Human Resources - Version 12.1 HRMS RUP10 and later
Information in this document applies to any platform.

Symptoms

On : 12.1 HRMS RUP10 version, Person / Assignment Issues

ACTUAL BEHAVIOR
---------------
Assignment Primary Flag Disappears When Delete Future Primary Assignment

When Changing a person type from Ex-Employee to Contingent Worker; upon the save of the assignment data, a new row is added to the Ex.Employee record using the placement create date, which removes the primary flag from the Ex-Employee record. In the past, prior to August update, the end date on the Employee Assignment remained in its primary state, and no update was made to the record.
Fix was in place before we went to RUP 10, but after we went to RUP 10 is no longer working. We do not get error so we are not able to provide.
 

EXPECTED BEHAVIOR
-----------------------
It is expected the primary flag would not be turned off by hiring the CWK.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Hire a Contingent Worker (CWK)
2. Terminate (End Placement of CWK)
3. Hire this CWK as an Employee
2. Terminate the EE - Do not use a final process date
3. Create a new Placement for this EE to be a CWK
4. Check the assignment and see the primary flag is now unchecked for the employee assignment

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms