Retropay Creates Retro Entries for an Element When Changes Were Made for a Different Element

(Doc ID 2027645.1)

Last updated on JULY 03, 2015

Applies to:

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


Retropay (Enhanced) is creating unexpected retro entries for an element that was not changed.


Current period is June-2015. An employee has a change in Element 'A' from 16-Jan-2015. After running Enhanced Retropay, there are retro entries for Element 'B' also from Jan-2015.

This should not have happened. When Element A is changed, why are there retro entries for Element B?



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