My Oracle Support Banner

STP, Incorrect YTD With First Pay Event Checkbox Selected And PayGroup Transfer To NOT Active (Doc ID 2601531.1)

Last updated on OCTOBER 21, 2019

Applies to:

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

Symptoms


STP, Incorrect YTD with First Pay Event checkbox selected and Pay Group transfer to NOT Active

STEPS TO REPLICATE
-----------------------------------
The issue can be reproduced at will with the following steps:
1) Login as admin, consider two paygroups KABIWEEKLY and KAFNIGHT.
2) EMPXXX has only been paid in KA 2019F01, KA 2019F02 and KA 2019F03
There are no payments in KA 2019B02 and KA 2019B03
3) In the scenario, EMPXXX has the following transactions processed in Job, immediately after all
calendars been finalized and before the First Pay Event to Payment Date 02/15/2019 is processed.
4) The EMPLID terminated in Job:
The retrospective effective date (23/01/2019) is Sequence 0 and is mid-KA 2019F02 (01/16/2019-- 01/30/2019)
The EMPLID remains in Pay Group KAFNIGHT.
5) The EMPLID is rehired retrospectively ,The retrospective effective date (23/01/2019) is Sequence 1
The EMPLID remains in Pay Group KAFNIGHT
6) The EMPLID is transferred to Pay Group KABIWEEKLY retrospectively , The retrospective effective date (23/01/2019) is Sequence 2
The EMPLID is now in Pay Group KABIWEEKLY
7) The EMPLID is immediately on LOA retrospectively , The retrospective effective date (23/01/2019) is Sequence 3
The EMPLID remains in Pay Group KABIWEEKLY
8) Run the STP Prep Process for Pay Entity (FY 2019) with no other criteria.
9) The Staging Tables have been populated with all data for the financial year, but only up to and
including KA 2019F02. The data for KA 2019F03 is missing. These are not the correct YTDs for the STP being processed as at the end of KA 2019F03.


EXPECTED AND ACTUAL BEHAVIOR
-----------------------------------------------------
Actual: The Staging Tables have been populated with all data for the financial year, but only up to and including KA 2019F02. The data for KA 2019F03 is missing.
Expected:The process needs to be included the YTD's till KA 2019F03.


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.