My Oracle Support Banner

GPUK: After Performing Changes on Maintain Tax Data GBR Page, a Retro Trigger is Generated with Wrong Effective Date (First Row Effdt and not Latest Effdt) (Doc ID 2888020.1)

Last updated on NOVEMBER 03, 2022

Applies to:

PeopleSoft Enterprise HCM Global Payroll UK - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Whenever changes are performed on Maintain Tax Data GBR Page, a retro trigger is generated with the wrong Effective Date (Employee Last start date instead of the Effective Date inserted on the Maintain Tax Data GBR Page).

Steps to reproduce the issue:

  1. Apply Bug 31556863 through PUM.
  2. Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll: Finalize Payroll up to date.
  3. Navigate to Global Payroll & Absence Mgmt > Payee Data > Taxes > Maintain Tax Data GBR: Select an Employee whose student loan plan type is “1”. Run the following SQL in order to identify this: select * from PS_GPGB_EE_TAX where GPGB_SL_PLAN_TYPE = '1' and EMPLID LIKE 'ABC';
  4. Add a row with the current date. Observe: Retro trigger is created with date Last Start Date instead of the Effective Date, which is not correct

 

Changes

 Issue encountered after applying Bug 31556863.

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.