My Oracle Support Banner

Generic Upgrade Mechansim (Retropay by Element to Retropay Enhanced) created retro components for retro elements with self retro (Doc ID 2666257.1)

Last updated on MAY 11, 2020

Applies to:

Oracle Payroll - Version 12.1 HRMS RUP12 and later
Information in this document applies to any platform.

Goal

For International Payroll, have been using Retropay by Element.

In order to move to Retropay Enhanced, have run 'Generic Upgrade Mechansim'.

Program: Generic Upgrade Mechansim
Parameter:
Name = International Payroll: Upgrade Retro Elements

Post running this process, as expected retro components are created for the required parent elements with corresponding retro elements.

But the issue is; retro elements also have retro components created with the retro elements attached being themselves.

Example:

1. Before Generic Upgrade Mechanism:

Parent Element: XX Allowance
Recalculation Events: XX Retro Group
Retropay Element: XX Allowance Retro

Retro Element: XX Allowance Retro
Recalculation Events: blank
Retropay Element: blank

2. After Generic Upgrade Mechanism:

Parent Element: XX Allowance
Recalculation Events: XX Retro Group
Retro Components: Backdated changes (enabled)
Retropay Element: XX Allowance Retro

Retro Element: XX Allowance Retro
Recalculation Events: blank
Retro Components: Backdated changes (enabled)
Retropay Element: XX Allowance Retro

Note: Post generic upgrade, 'XX Allowance Retro' itself has retro element (with retro component) but unlike parent element there is no event group.

Solution

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
Goal
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.