My Oracle Support Banner

UK-PAY: _PER_PTD Balance Dimension Is Not Working As Expected Within Retro Pay (Doc ID 2283192.1)

Last updated on SEPTEMBER 06, 2019

Applies to:

Oracle Payroll - Version 12.1 HRMS RUP9 and later
Oracle HRMS (UK) - Version 12.1 HRMS RUP9 and later
Information in this document applies to any platform.


When an employee has 2 assignments, RetroPay is refunding all the amounts used by the first assignment, when this assignment has been terminated and a second assignment is created.

The issue is when a second assignment is created and the first assignment is terminated, the event group is capturing the earliest trigger date to apply for Retro Notifications, and based on the update to the assignment status the earliest date for Retro Notification is being taken from a standard linked element on employee's record, which was applied at the start of their employment and has never been updated, forcing Retro to go back across many years.

Retro is then assuming that there must be more than one assignment way back when and is recovering all the amounts from the first assignment, when actually there is only one assignment at that point.

The PER_PTD dimension will not be visible across both assignments until both assignments are active .

The issue can be reproduced at will with the following steps:
1. Using UK HRMS Responsibility
2. Create a secondary assignment with a certain date, e.g. 01-Dec-2016
3. Terminate the primary assignment with 01-Dec-2016
4. Run Retro Notification Report and Retropay Enhanced
5. Check the element Entries for terminate assignment - Retro <ELEMENT NAME> is generated for a long time ago




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

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