Element Frequency Rule Change Causes Unwanted Retro Entries
(Doc ID 2334191.1)
Last updated on MARCH 26, 2025
Applies to:
Oracle Payroll - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
The Frequency Rules have been changed for an element and now when Retropay (Enhanced) is run, there are unwanted retro entries for the element that was changed. When making the change to the frequency rules, there was no option to make the change as an update and was made as a correction only.
Example:
For a bi-weekly payroll, the frequency rule for a deduction element was changed so the deduction is taken in periods 1 and 2, thus changing the deductions from 26/year to 24/year. After the change is made, there are retro entries for the element since some periods had deductions for a third pay period in a month.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Updated frequency rules for some elements in Correction mode (Update mode is not available)
2. Run Retro-Notifications Report (Enhanced)
3. Run Retropay (Enhanced)
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 |
| Cause |
| Solution |