My Oracle Support Banner

After Converting from Retropay by Element to Retropay (Enhanced), Old Retro Entries are Reprocessed and Creating Incorrect Retro Entries (Doc ID 2856556.1)

Last updated on MARCH 18, 2022

Applies to:

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

Symptoms

After converting from Retropay by Element functionality to Retropay (Enhanced), it is found that some retro entries are created by Retropay (Enhanced) that are related to very old retroactive changes that were already processed by Retropay by Element.
 
STEPS
-----------------------
The issue can be reproduced at will with the following steps:

After conversion to Retropay (Enhanced) functionality, in HRMS Manager responsibility or equivalent:

1. Run Retro-Notifications Report (Enhanced) - PDF concurrent process
 - Navigate: Processes and Reports > Submit Processes and Reports > Single Request

2. Run Retropay (Enhanced) concurrent process
 - Navigate: Processes and Reports > Submit Processes and Reports > Single Request

3. Check employee element entries to confirm retro entries created
 - Navigate: People > Enter and Maintain > query for employee > Assignments > Entries



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
References


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