HR ESP AFI: SS WORK GROUP NOT CORRECT SYNCHRONIZED WHEN JOB EFF SQ=1 (Doc ID 2298456.1)

Last updated on AUGUST 18, 2017

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
"Data Change + change in work group" movement on 10th September 2015 with effective sequence 0 and the information is populated properly on Update Contracts Esp component (a new row has been added on both, Afflliation Data and Affilliation Event details). Add a new row on Job Data component with the combination action + action_reason: Data Change + change in work group on 10th September 2015 with effective sequence 1 and a new value on work group field. The new value on work group field on Affilliation Data details is not the last one. If the row with effective sequence 1 on Job Data component is deleted, on Affilliation Data details the row on 10th December 2015 has been removed and this is not correct because on the Affilliation Event details the row on 10th December with effective sequence 0 is still there without the related row on Affilliation Data details.

Explanation of the user experience: Due having multiple users, it happens that one user enter data in the system, that produce AFI movement.
This is being reported to SS...then the same day another user correct the information. Because the previous data was already sent...they enter the new data with new effective seq.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Setup IB
2. Enter an effective date in Job -->i.e 1-Jan-2016 with action=Data Change, Reason: Change work Group. Labor Agreement category = 32
3. Check AFI data row is generated for this , check the Work group is the one associated with category =31
4. Enter a new effective sequence in Job --> 1-Jan-2016, seq=1 with action=Data Change, Reason: Change work Group . Labor Agreement category = 37
5. Check if AFI data (work group) has bee updated with the work group associated to LA category =37 (This is what looks to be incorrect)

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