Data Conflict Error Observed When Rehire done on a Secondary Job, on the Same Effective Date as the Rehire of the Primary Job Record
(Doc ID 2643592.1)
Last updated on MAY 26, 2020
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise HCM Payroll for North America - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Rehire on a Secondary Job Record for an Employee on the same effective date as the Rehire of the Primary Job Record is giving Data Conflict Errors.
Data being added conflicts with existing data. (18,2)
When adding a new item to the database, the system found a conflicting item already exists.
This problem can happen if another user has entered similar information at the same time as you. Note the changes you have made, cancel the page, then retry your changes.
If the problem persists, it may be because of an application or other programming error and should be reported to technical support staff.
This error occurs when the keys on the record being inserted match a record that is already in the database. The application must ensure that each inserted record has unique keys.
The issue can be reproduced with the following steps:
1) Login as an Administrator
2) Choose an employee whose has Empl Record 0 and 1
3) Terminate the Empl Record 0 which is a Primary Job with effective date as 01/01/2019
4) And Terminate Empl Record 1 for the same employee which is a Secondary Job as of 01/01/2019
5) Rehire the Employee for Empl Rcd '0' which is a Primary Job by adding a New Row with effective date as 01/29/2020.
5) Observe that Rehire is successful and a effective dated row was added to the Employee Tax Data
6) Now goback to Empl Record 1 for the same employee which is in an Inactive status and add a New Row with the Action as Rehire with effective date as 01/29/2020.
7) Observe the Data conflict Error.
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