My Oracle Support Banner

GSS Retirement Transaction Allowed For Employees With Existing Retirement Rows, Which Creates A Second Effective Sequence Row On Job Data (Doc ID 2821276.1)

Last updated on NOVEMBER 14, 2021

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

When a retirement transaction is entered in job data with effective sequence 0 and then an GSS Retirement transaction for the same employee is approved in the system, the system creates a new effective sequence 1. This can override the data that was originally made and mess up reporting.


The issue can be reproduced at will with the following steps:
1. User enters a retirement row for an employee in Job Data, with effective date in the future.
2. User then submits a GSS Retirement transaction for the same employee with the same effective date.
3. Transaction gets approved by approvers as necessary.
4. Job Data for the employee now has two Retirement rows for the same day, with the GSS transaction adding Effective Sequence 1

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
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.