My Oracle Support Banner

GP Core: Incorrect Forecast Results With Retro Triggers Exceeding Retro Limit (Doc ID 3073464.1)

Last updated on FEBRUARY 27, 2025

Applies to:

PeopleSoft Enterprise HCM Global Payroll Core - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise HCM Absence Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Employees forecast results are often incorrect when they have a retro trigger in the current calendar group which exceeds their retro limit.

Due to the nature of the issue, the forecast is usually corrected once the open Calendar Group is finalized, however the employee is unable to forecast leave in self service while affected.


The issue can be reproduced at will with the following steps:
1.Consider Payee KA0003
2.Last finalized Cal Run is May 2024 (calculated retro for previous periods)
3.Retro triggers:  01/01/2024 and 04/30/2024
4.Retro limit assigned by Payee is 3 months backward
5.Forecasting ANN TKEDYS as of 12/31/2024
6.Forecast begin date:
a.Without June Payroll calculated - Begin date is 03/01/2024 - Balances are ok and the date is correct as well.
b.When June payroll is calculated - Begin date is 04/30/2024 and ANN ENTDYS_BAL is zero - Both values are incorrect.

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


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