As you may already know, RetroPay (Enhanced) process is the current advanced version of RetroPay and is a step forward to automatic back-pay processing.
Running Retro-Notifications Report (Enhanced) is a mandatory step before running in enhanced RetroPay.
How Retro Pay Works?
RetroPay process assignment by assignment. Oracle Payroll, internally, in a separate session, rollback and rerun all the payrolls of an assignment from a specified date. The system then compares the old balance values with the new ones and entry values are created for the RetroPay elements based on the difference of values. These entries are processed for the assignments in the subsequent payroll run for your current period.
It is important to note that, no actual changes are made to audited payroll data, which means RetroPay process won't touch the existing data of previous payrolls.
There are different types of dates in the context of RetroPay with the descriptions as given below.
Date Earned
It is the date on which payroll action is created.
In fact, this is one of the columns in PAY_PAYROLL_ACTIONS table.
This date will be one for all assignments in a payroll.
Effective Date
It's one of the mandatory parameters of "Retropay (Enhanced)" Concurrent Program (CP) and RetroPay payroll action will be created with this date. Enhanced RetroPay internally checks if there are any payroll actions exists after this date and it will create derived retro element entries (if any) only when there are no future payroll actions after this date.
This date will be one for all assignments in a payroll.
Entry Creation Date
Optional parameter to RetroPay (Enhanced) CP, visible only to specific legislations like SA.
This is the date on which calculated retro element entries (EEs) are created.
This date can be greater than or equal to "Effective Date". This parameter is used to pay the back dated payroll changes in the future payroll periods, instead of current payroll periods.
It will be one for all assignments in a payroll.
Recorded Date
This date is used internally by Retro Notifications Report Enhanced (RNR) to list out all the assignments that have unaccounted back-dated changes in the given payroll. It can be defined as the date on which last RNR was run. For the first run of RNR on a fresh assignment, it will be "Date Earned" of latest payroll action.
This date will be one for one assignment.
Reprocess Date
This date is calculated by RNR for an assignment based on the events that are logged.
It is the earliest date of all the back-dated changes on the given assignment. If there are no overlaps, RetroPay will rollback/rerun the payrolls in memory starting from this date.
It is one of the columns in PAY_RETRO_ASSIGNMENTS table.
This date will be one for one assignment.
Overlap Start Date
This date is internally calculated by enhanced EntroPay process depending on the overlappings with previous retropay runs.
It is the date from which actual rollback/re-run of payrolls happens in memory.
RetroPay recursive go back to all the overlaps (if exist) and calculates the earliest date from when payrolls need to re-run so that it derives correct results.
This date will be one for one assignment.
