EPY Idea Space: When running Payroll, The Retro Calculation is Prorating ADDITIONAL PAY Calculation When the On-Cycle Calculation Does Not (Doc ID 2958769.1)

Last updated on APRIL 15, 2024

Applies to:

Symptoms

Retro for Earning Code for LEP(Law Enforcement Pay) should have been zero since nothing had changed with ADDITIONAL PAY for LEP. Retro Calculation is prorating ADDITIONAL PAY Calculation when the On-Cycle Calculation does not.
LEP paid for the period did not prorate even though the prior end date on Additional Pay was a new effective date.

Steps to reproduce the issue:

1. Navigator > Payroll for North America > Employee Pay Data USF > Create Additional Pay
- JOB transaction ended LEP on 01/14/2023 for $899.20
- started LEP again on 01/23/2023 for $899.20.

2. Navigator > Payroll for North America > Payroll Processing USF > Produce Payroll > Review Paycheck > Paycheck Earnings
Calculation for PP02 (01/15/2023 – 01/28/2023)
- LEP Paid 899.20 for period and did not prorate even though the prior end date on Additional Pay was 01/14/2023 and new effdt on Additional Pay was 01/23/2023.

Create a Retro trigger back to PP02:
3. Navigator > Payroll for North America > Employee Pay Data USF > Create Additional Pay
- Generated a retro trigger by starting Post Diff (PD) as of 01/15/2023.
- Did not change anything on Additional Pay for LEP!

4. Navigator > Payroll for North America > Retroactive Payroll > Retro Pay > Process and Review Requests > Request and Trigger Summary

5. Navigator > Payroll for North America > Retroactive Payroll > Retro Pay > Process and Review Requests > Retro Pay Calculation Results
- Retro Calculation collected $449.60 from week 1.
- Retro Calculation for week 2 is correct.

Note: The amounts are just an example for calculation purposes.

Cause

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