Best Practice for Running Retropay
Hi
What is the best practice for running retropay on Oracle Cloud Payroll?
We run retro and associated processes thus:
1. Run Generate HCM Rates
2. Run Recalculate Payroll for Retroactive Changes
3. Review and resolve retro errors and check retro entries
4. Rollback and re-run retropay as required with Generate HCM Rates (as appropriate) ahead of payroll run
5. Run Calculate payroll
However, recently we have noticed that retro notifications are still awaiting processing after retro has been run and this isn't simply a timing issue, new events or events missing from the retro group. So events that haven't been processed. Similarly, running the retro notifications report after the retro run has highlighted new events that have been created that didn't exist prior to the retro being.