GP CORE: Unwanted Retro Triggers are being Processed in the Current Month Calendar
(Doc ID 3030077.1)
Last updated on JUNE 20, 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
Unwanted retro triggers are getting processed in the current month calendar for a specific scenario.
The issue can be reproduced at will with the following steps:
1. Login as payroll admin and enable the Absence Event checkbox on Retro event definitions page.
Navigation: Set Up HCM > Product Related > Global Payroll & Absence Mgmt > Triggers > Retro Event Definitions > Retro Event Definitions
Country: AUS
Trigger Event ID: GPABSEVENT
Retro Process Definition ID: AU RETRO
2. Note the Last finalized calendar in this DB was: KA 2023M06
3. Create a Correction Off cycle for KA 2023M06.
Navigation : Global Payroll & Absence Mgmt > Absence and Payroll Processing > Off Cycle > Off Cycle On Demand > Off Cycle On Demand
Emplid: KA0003 with PI of 125 AUD for the earnings element “ONCALL” Finalize OFF_KA2023M06 calendar.
4. Then Calculate and finalize the KA 2023M07 calendar.
Navigation: Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll > Calculate Absence and Payroll.
5. For emplid “KA0003”, retroactively compensation is increased to AUD 84,000 effective from June 1 , 2023
Navigation: Main Menu > Workforce Administration > Job Information > Job Data
There by generating a retro trigger as the current period is August 2023.
6. Add absence events for the Emplid “KA0001” and “KA0007” have the following absence event page:
KA0001: Absence Take: ANN TKEDYS
Begin Date: 30th Aug 2023
End Date: 01st Sep 2023
KA0007: Absence Take:ANN TKEDYS
Begin Date: 30th Aug 2023 End Date: 30th Aug 2023
Begin Date: 19 Sep 2023 End Date: 19th Sep 2023
to be processed in August 2023.
7. Process calendar group “KA 2023M08”.
For both “KA0001” and “KA0007” .
Note that July periods are getting re-calculated, when there are no retro triggers going back to July is not a expected retros.
NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample (based up made up data used in the Product name test environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
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 |