Cancel hire against an Assignment which was turned Secondary due to a manual Primary Assignment creation - Creates an Assignment Corruption

(Doc ID 2190917.1)

Last updated on OCTOBER 07, 2016

Applies to:

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


On 12.1 HRMS RUP 7 version of Application, In the Assignment form.


When doing a cancel hire against an Assignment which was turned Secondary due to a manual Primary Assignment creation, it creates 2 open ended Primary Assignment record.


Expect that, what ever action is carry forwarded in the application, it should always have only one Primary Assignment. Action carried out should not create 2 primary assignments.


The issue can be reproduced at will with the following steps:

1. Login to 'HRMS Manager' Responsibility.

2. Navigate to People --> Enter and Maintain.

3. Query an 'Employee.Applicant' Record.

4. Date track to a Past Date (Compare to Sysdate).

5. Click on the 'Others' button and from the List Of Values (LOV), select the value 'Application'.

6. Change the Application Status to 'Accepted'.

7. Now came back to the People form, date tracked, and carried out a 'Hire Applicant' action.

8. Accept the applicant assignment to be New Primary assignment.

9. Now click on the 'Assignment' button and in the launched assignment form, key in a new Assignment record and make it 'Primary'.

10. Come back to the People Form and when a 'Cancel Hire' is done, the assignment got created against the application record is removed.

11. This change leaves two primary assignments to be open ended. Thus leaving the system with 2 primary assignments at any time.


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