My Oracle Support Banner

Retro Triggers Are Incorrect Generated For Absence Event (Doc ID 2360433.1)

Last updated on MAY 07, 2018

Applies to:

PeopleSoft Enterprise HCM Global Payroll Core - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Retroactive calculations for Absence events

There is an issue related the way retro triggers are generated when it is updated the end date of an existing absence event entry. The trigger is being generated with effective date equal to absence begin date, instead of New Absence End date. This produces undesirable retro processing.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enter an absence . For example from January , for 1 year
2. Run payroll for January and finalize it.
3. Modify the end date of a an existing absence event next day or later (not
on same day)
4. Run February

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.