Retropay Reprocess Date Changed By API Gets Set Back To Original Date
Last updated on JULY 07, 2017
Applies to:Oracle Payroll - Version 12.1 HRMS RUP9 and later
Information in this document applies to any platform.
Users have found that after changing the reprocess date for retro assignments either by API or through the Retropay Status screen, the original reprocess date is coming back after Retro-Notifications Report (Enhanced) - PDF or the Quick Retropay (Enhanced) process is run. The reprocess date should not be over-written by these processes.
The issue can be reproduced at will with the following steps:
1. Make a change to an existing unprocessed retro assignment, changing the recalculation date, either by API or through View > Retropay Status form
2. Run Retro-Notifications Report (Enhanced) or Quick Retropay (Enhanced) and see the recalculation date has been changed back to the original date.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms