Retrospective Insertion Of History Job Data Row Deletes The Already Generated Triggers

(Doc ID 1483987.1)

Last updated on OCTOBER 31, 2017

Applies to:

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

Symptoms

CUSTOMER ENVIRONMENT
---------------------
HRMS / GP Release: PeopleSoft Enterprise HRMS Global Payroll Core 9.1
Tools Release: 8.51
Issue occurring in Production Environment

STATEMENT OF THE ISSUE:
-----------------------------------
Segmentation Triggers for the Termination row get deleted when another row with prior Effective date is entered in the JOB Data.

STEPS TO REPLICATE
--------------------
1. Insert a termination row as of 03/30/2012
 
2. Trigger got generated as of Termination date

3. Inserted a new row as of 3/15/2012 prior to termination row of 3/30/2012, Saved. The termination row is still there.

4. Trigger generated as of 03/30/2012 got deleted automatically. Even though the 03/15/2012 row was not configured to create any trigger
 

EXPECTED BEHAVIOUR
--------------------
Segmentation trigger existing for a Termination row must not get deleted when a new row with prior EFFDT is added to the Job Data.

and

ACTUAL BEHAVIOUR
------------------
Segmentation trigger existing for a Termination row gets deleted when a new row with prior EFFDT is added to the Job Data.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms