GP/AM: Segmentation Triggers Not Consistently Created When There Are Multiple Job Data Changes on the Same Effective Date (Doc ID 3067697.1)

Last updated on JANUARY 15, 2025

Applies to:

Symptoms

Segmentation triggers not created as expected when there are multiple JOB changes and the generic "Data Change" is the Action for Effective Sequence 0 row.

Steps to Reproduce:

1. Segmentation trigger is created for EMPL_STATUS change. (Set Up HCM>Product Related>Global Payroll and Absence Management>Triggers>Segmentation Triggers).
2. Main Menu>Workforce Administration>Job Information>Job Data select an employee.
3. Insert a row with action "Leave of Absence" and save (this creates effective sequence 0).
4. Insert a row with the same effective date and effective sequence 1 with action of "Data Change" and save.
5. Main Menu>Global Payroll and Absence Management>Absence and Payroll Processing>Prepare Payroll>Review Triggers.
6. Select Segmentation trigger and see a row for the changes above (note there is only one trigger, because that is based on effective date, not effective sequence).
7. If the rows above were created with "Data Change" as the effective sequence 0 row and "Leave of Absence" as the effective sequence 1 row, no segmentation trigger is created.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.