New Position Data Row Creates/inserts Job Data Row When It Should Not
(Doc ID 2368663.1)
Last updated on JANUARY 31, 2019
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Adding a new position data row with any reason (Reason is not a 'trigger' field and should not prompt a job row to be inserted) and when saving, we get a
Position data is updated for position XXXXXX with effective date YYYY-MM-DD. (1000,1592)
Any change in position data would reset the compensation frequency from job code for all incumbents.
Are you sure you want to proceed with the changes?
No matter if you choose Yes or No on the warning, a job row is inserted.
The issue can be reproduced at will with the following steps:
1. Update position information and save
2. Select No on the message.
3. Check incumbents that have N for Override Position Data to see that there
is a new job row.
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