7/25/2019 Primary Assignment Issue

1/6

Manager hierarchy looping issue

7/25/2019 Primary Assignment Issue

2/6

7/25/2019 Primary Assignment Issue

3/6

Infosys confidential 3

racle introduced a new #alidation in P/% where primary assignment cannot 0e Inacti#e.

This causes the data to fail in !or*elationship Integration with error Primary Assignment must 0e acti#e". There are

11$ errors in P23.

!e cannot ha#e Acti#e and Inacti#e relationship on the same day.

Issue

Impact :

The data for e4isting *etiree partners will not get updated

,ew *etiree will not get into 3usion system

7/25/2019 Primary Assignment Issue

4/6

Infosys confidential 4

Suggested !oraround

1. Change the 0usiness process how we retire partners5 ,ot possi0le as 0usiness process change is re6uired7 this will ha#e impacts on UPAS payroll7 retirement

system

'. !hile sending the data from UPAS to 3usion set the date 1 day apart 0etween *ehire and *etire from P+,

Company5 This will ha#e impact in 3usion as one day acti#e assignment will 0e considered for compensation.5 The data in UPAS and 3usion will 0e out of sync.

-. Instead of sending the data for the retire row as Inacti#e 8 payroll ineligi0le for assignment status7 send the row

with assignment status as Acti#e 9 *etired Partner .5 Partner status is correctly updates a *etired Partner

5 Partner is not eligi0le for the compensation cycle as re6uired5 ata 0etween UPAS and 3usion are in sync

7/25/2019 Primary Assignment Issue

5/6

Infosys confidential 5

Test *esults

7/25/2019 Primary Assignment Issue

6/6

T)A,;