My Oracle Support Banner

E-AD: PT 8.56 Record-level Auditing Causes "Data Integrity" Issues. (Doc ID 2441126.1)

Last updated on FEBRUARY 07, 2019

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
Information in this document applies to any platform.


On : 9.2 version, Other

Auditing of the PS_JOB record

In trace- Rollback.

On page-
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 auditing works fine if you update the current row compensation. The auditing works fine on historical rows as long as you do not change the compensation amount.

The issue can be reproduced at will with the following steps:
1. Create and enable audit record for JOB
2. Workforce Administration > Job Information > Job Data
3. Correct History mode
4. Salary Plan tab. Change Grade
5. Compensation tab. Click Default Pay Components and save
6. Error occurs

The issue has the following business impact:
Due to this issue, users were forced to turn off JOB auditing in order to save changes. Auditing prevented until issue resolved


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

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