Hi,

After creating employee via API, it created an initial assignment record.

I have multiple assignment records for an employee, How to migrate employee assignment?

I saw these API, not quite which one to use

hr_assignment_api.update_emp_asg
hr_assignment_api.update_emp_asg_criteria
hr_assignment_api.activate_emp_asg


Appreciate response on this

BTS

Hi

It depends on what items on the assignment you are migrating

update_emp_asg_criteria is used to update anything on the assignment that could control eligibility for an element - e.g. grade, job, position, people group, payroll etc

update_emp_asg (or for UK legislation you can - and should - use update_gb_emp_asg) will do the other things such as supervisor, normal hours, assignment desc flex etc.

For any given assignment record, it is more than likely you will need to call both of these apis to furnish all the required data.

activate_emp_asg is more of a process than a simple 'update', as it controls the switching of the assignment status ONLY - specifically, to some flavour of 'ACTIVE_ASSIGN'. In a migration context it is unlikely (but not impossible) that you would need to make use of it. The default employee assignment has its assignment status set to the default flavour of ACTIVE_ASSIGN (which may well be 'Active Assignment') at creation time.

Hi CT,

Thanks for the help! I was able to load the assignment records. I used activate_emp_asg in order to update the assignment status. This is because I'm migratin multiple assignment status for every employee.

Does the record have to be sorted by effective date ascending? What happens if there are few assignment left out which is in the middle of effective dates for certain employee?

/bts

The best way is to load the history in ascending order of change date. That way, your date-track mode would only need to be 'UPDATE'. Of course if you are using more than one of the assignment APIs, the second and subsequent ones would probably use the date-track mode 'CORRECTION'.

You can retrospectively fill gaps where some records failed validation, but you need to make sure that the date-track mode is 'UPDATE_CHANGE_INSERT'. Note too that even doing this might mean that certain changes that should have propagated forward from that 'failed' and retried update, might well not be there. The best strategy in my view is to halt processing of assignment history for an assignment as soon as there is an exception. Then, once you have found the specific issue and resolved it, you can rerun your process for the remaining unprocessed changes in 'UPDATE' mode, and everything is consistent.

Thanks for the advice. You have been really of great help.

/bts