GP Core: FYTDA Accumulator Does Not Hold Value When A Payment Is Reversed Retroactively
(Doc ID 3030953.1)
Last updated on JULY 01, 2024
Applies to:
PeopleSoft Enterprise HCM Global Payroll Core - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Accumulator does not hold value when a payment is reversed retroactively during the new accumulation period.
Retro is setup to be forwarded to a separate retro element, this configuration is done is retro process overrides(Set Up HCM > Product Related > Global Payroll & Absence Mgmt > Triggers > Retro Process Overrides).
The issue can be reproduced at will with the following steps:
Absence: AUS ANN leave element
Accumulation period is from 1st July to 30th June
1. Pay period is 1st June to 30th Jun, payment date is 5thJuly.
2. In June calendar, Annual leave amount is processed and finalized
3. In July calendar, Annual leave entry is removed.
4. Calculated calendar using( Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll > Calculate Absence and Payroll ), Annual leave amount is removed and the negative amount is carry forwarded to the retro element.
But the annual leave FYTDA element does not have any entry in the July calendar results while the retry Annual leave FYTDA element has negative value.
When the amounts of two elements are consolidated, it would result in negative value.
5. In One time positive input page ( Global Payroll & Absence Mgmt > Payee Data > Assign Earnings and Deductions > One Time (Positive Input) ), input Annual leave earning as 0.01 and reprocess July calendar.
6. If you see July Accumulator results, the Annual leave FYTDA elements holds the cumulative of 0.01 and the actual annual leave amount and the retro Annual leave FYTDA holds negative value. Here the values are perfectly seen.
6. Note that this issue happens only when the new accumulation period starts. Does not happen for the same scenario during the subsequent runs.
Changes
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 |
Changes |
Cause |
Solution |
References |