My Oracle Support Banner

EPY: Retro Pay Process is Generating Retro's Dating Back To 2017 (Doc ID 2742192.1)

Last updated on FEBRUARY 24, 2021

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

1st payroll of 2021 generated retro's dating back to 2017 

We are running a test in non-prod in preparation of mirroring what the 1st payroll of 2021 will appear like.

We noticed that for 41 employees retro's were generated when it should not have been generated and these retro's date back to 2016.

The retros are loaded to paysheets for oncycle payroll with earning begin date in 2016.

There are earnings begin dates also dated back to way in the past. They are not expected retros. We have noticed these after applying 20-D.


The issue can be reproduced with the following steps:

1. Old retro request sequence number is still open for 2017 effective date for an employee via RETROPAY_EARNS

2. Create a new retro trigger in Additional Pay Data (Payroll for North America>Employee Pay Data USA>Create Additional Pay)

3.  Verify the new retro request is associated to the old retro request sequence number via RETROPAY_EARNS

4.  Run the retro calculation and verify the results (Payroll for North America>Retroactive Payroll>Retro Pay>Process Review Requests>Retro Pay Calculation Results).




Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.