You can retry an employee or a run only when no post-run processing has occurred. You use reversals when you need to correct run results for a single assignment after post-run actions have already occurred.
In other words, reversals are useful when you need to correct run results some time after the run has occurred.
You may reverse a run for a past period during or after which stop dates exist for earnings or deductions. When this happens, Oracle Payroll issues a warning. This tells you to check whether you should restart any of the stopped earnings or deductions.
For example, the reversal may have cancelled out a deduction that was an employee's final payment toward an outstanding loan. In this case, the warning alerts you to the need to restart the deduction.
Reversals of payroll runs with nonrecurring and additional element entries provide an exception to the 'once only' rule for processing nonrecurring elements.
Normally, nonrecurring element entries can be given only once to an employee. Additional entries for recurring elements can be given only once in each pay period.
The effect of this rule on payroll run reversals is that nonrecurring and additional entries do not get reprocessed in subsequent runs following a reversal. As a consequence, the results of subsequent runs will not be identical to the original run results.
To prevent this, Oracle Payroll allows nonrecurring and additional entries to be reactivated and reprocessed in subsequent runs following payroll run reversals. This makes it possible for the run results of subsequent runs to be identical to the original results.
Warning: You cannot roll back a reversal if there are subsequent payroll runs. This is to prevent nonrecurring and additional entries being given twice - in the reversed run and in the subsequent run.
You use batch reversal when you need to correct run results for a batch or multiple assignments after post-run actions have already occurred.