Unprocessed Entries Are Picking Up In Retropay Process After Deletion from Retropay Status Form
(Doc ID 2910359.1)
Last updated on JANUARY 01, 2024
Applies to:
Oracle Payroll - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
Unprocessed element entries are picked up in the Retropay (Enhanced) process after marking the retro assignment as Completed - Deferred Forever in the Retropay Status form.
Users expectation is that even though there is a retroactive update on employee record, unprocessed entries which was originally marked as Deferred Forever shouldn't pick up in following Retropay process.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Example:
In HRMS Manager responsibility or equivalent:
1. Make a retroactive element entry for 20 hours.
Navigate: People > Enter and Maintain > query for employee > Assignments > Entries
2. Run Retro-Notifications Report (Enhanced) - PDF
Navigate: Processes and Results > Submit Processes and Results > Single Request
3. Delete (defer forever) the retro assignment created in step 2.
Navigate: Navigate: View > Retropay Status
4. Make subsequent retroactive changes to salary for the same employee.
Navigate: People > Enter and Maintain > query for employee > Assignments > Salary
5. Run Retro-Notifications Report (Enhanced) - PDF
6. Run Retropay (Enhanced)
Navigate: Processes and Results > Submit Processes and Results > Single Request
7. Run QuickPay
Navigate: People > Enter and Maintain > query for employee > Assignments > Others > Quick Pay
8. Check element entries and see that Retropay created entries for the 20 hours in step 1.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |