Retropay Involving Reversal Run Incorrectly Recovering Deleted Entries. (Doc ID 1925224.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Payroll - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Core Payroll

ACTUAL BEHAVIOR
---------------
When Retropay runs with a re-calculation date that INCLUDES the reversal run but EXCLUDES the pay run that the reversal is run for and the element entries for the period the reversal has been run has been deleted, then the retro pay recoveres the deleted entries again.

The reversal of a pay run happens much later as compared to the pay run itself that it reverses. Any changes to the assignment or its element entries that brings in a re-calculation date that includes the reversal but NOT the original pay run for which the reversal was run, we think has this issue.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an earnings element for an employee as of 29-Apr-2013 – Start date of the pay period 23 2013 Bi-Week – 29-Apr-2013 to 12-May-2013
2. Run a Quickpay
3. Further payroll processes are run and the employee is paid.
4. Reverse the Quickpay run in the next pay period – Effective date of 15-May-13
5. Delete the earnings element entry created in Step 1.
6. Create Retro pay status for this employee with a re-calculation date of 29-Apr-2013. In reality when the Retro Notifications process is run this would create this record.
7. Run Retropay (Enhanced) with an effective date of 18-May-2013.
The above process creates a positive and a negative entry corresponding to the Quick Pay and the Reversal.
8. Run a Quick Pay for the period 24 2013 Bi Week. This will process the Retro entries generated in Step 7.
9. Create Retropay status for this employee with a re-calculation date of 13-May-2013 which is the pay period 24 2013 Bi-Week
10. Run Retropay (Enhanced) with an effective date of 01-Jun-2013.
11. This again creates a negative retro entry which we think is incorrect.
In reality the reversal of a pay run happens much later as compared to the pay run itself that it reverses. Any changes to the assignment or its element entries that brings in a re-calculation date that includes the reversal but NOT the original pay run for which the reversal was run, we think has this issue.

Observations/comments.
---------------------------------------
When customer updated the the RETRO_OVERLAP to 'Y' and then reran the Retro as given in Step 10 of the Steps_to_replicate.docx. This also does NOT create the Retro entry again and seems fine.

However customer believes this this should work as expected and should NOT create the negetive retro entry with the RETRO_OVERLAP to 'N' and the re-calculation date of 13-May-2013.

Also currently have enabled retro Overlap functionality (RETRO_OVERLAP legislation rule type parameter to 'N'). This was a change suggested by Oracle to improve retro process performance.


Cause

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