Effective Date Can Be Left Blank On the 'Request Details' Page When Adding a New Row To a Position That Is In 'Approval Process' Status
(Doc ID 2584367.1)
Last updated on OCTOBER 22, 2019
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When position has row in 'Approval Process' and a new row is added, the Effective Date field is not required field on the 'Request Details' page.
On the 'Request Details'- if the user picks a date after the effective date of the row that is in "Approval Process", the user will receive an error message "Only history rows can be added as the current row is in Approval Process'. However, if the user does not pick a date and clicks continue, the system uses the current date, even if this date is after the effective date of the row that is in "Approval Process".
The issue can be reproduced at will with the following steps:
1. Pick position that has a row with status in "In Approval Process", for example effective date is June 16, 2019.
2. Add a new row, do not pick a date. Click Continue.
3. The system uses current date, for example July 2, 2019 (This is incorrect, only history rows should be allowed).
4. The system allows the user to submit the position update with July 2, 2019. Which produces SQL error message when the user will try to view this row 'SQL error in Exec. (2,280). During the execution of SQL, an error occurred in the Exec subroutine. The preceding message should have described the SQL being executed'.
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