My Oracle Support Banner

Segmentation Trigger Getting Deleted When Delete the Job Data Comp Rate Code (Doc ID 2732362.1)

Last updated on NOVEMBER 29, 2020

Applies to:

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

Symptoms

Employee Job Data has multiple EFFSEQ (eg 0, 1) for a given EFFDT, for each EFFSEQ row there are multiple Compensation Comp Rate Codes. When DELETE one of the Rate Code from non a MAX(EFFSEQ) Job/Compensation row (EFFSEQ=0), the associated COMPRATE Segmentation Trigger is removed (even though Job Data SEQ=0 still exists).

The issue can be reproduced at will with the following steps:
1. Insert new JOB EFFDT 07/01/2018, EFFSEQ = 0, ACTION = PAY. On the Compensation Page, add Rate Code as listed below and SAVE. (See below)
a. KABS01 $30,000
b. KABSTL $5
(note. KABSTL is Comp Base Pay Switch = Y)

2. Insert new JOB EFFDT 07/01/2018, EFFSEQ = 1, ACTION = PAY. On the Compensation Page, Increase Rate Code KABSTL value to $10, and increase value of KABS01 to $31000. SAVE. (See below)
Note:
- Job Compensation Rate has changed.
- Rate Code KABSTL has Comp Base Pay Switch = Y
 
3. Insert new JOB EFFDT 08/01/2018, EFFSEQ = 0, ACTION = PAY. On the Compensation Page, remove Rate Code KABSTL and update rate code KABS01 value from $31,000 to $40,000.
Note:
- Job Compensation Rate has changed.
 
4. Navigate to Global Payroll & Absence Mgmt > Absence & Payroll Processing > Prepare Payroll > Review Triggeres
Three new segmentation triggers created (Event ID COMPRATE) as expected with correct JOB EFFDT and EFFSEQ.

5. Go to Job Data in Correction Mode
a. Select EMPLID KA0030, and
b. Navigate to EFFDT 07/01/2018, EFFSEQ = 0 (no latest eff sequence)
c. Go to Compensation Page
d. Delete row with Comp Rate code KABSTL
e. Save
 
After Delete and save

6. Navigate to Global Payroll & Absence Mgmt > Absence & Payroll Processing > Prepare Payroll > Review Triggeres and verify the segmentation trigger with EFFDT 07/01/2018 SEQUENCE = 0 has been deleted.

NOTE: In the images or examples above and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.


 

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.