My Oracle Support Banner

Fusion Global HR: Rehire Checklist Allocated to AORs based on Prior Termed Assignment, Not New One (Doc ID 2782674.1)

Last updated on JUNE 16, 2021

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.13.21.01.0 and later
Information in this document applies to any platform.

Goal

You created AOR based on a work location.
So, Employees working in that locations will have designated AORs for that location.
When employee changes the location after rehire, checklist is using AORs that were tied to old location Employee used to work.
Now, checklist Tasks are getting allocated to all AORs (AOR from old location + new location) causing confusion and delay in completing required pre-boarding tasks.

Scenario is like this:
Employee was terminated (used to be in Location_A and had AOR_1)
Rehired as a Pending Worker a year later in Location_B and now has AOR_2
Tasks that have AOR as a perfomer are getting allocated to both AOR_1 and AOR_2.

Expectation: Checklist should not select AOR_1 because this Emp-AOR relationship is no longer active as of rehire effective or checklist creation date.

Why application is looking at AOR even on a terminated work relationship?


 

Solution

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
Goal
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.