By any chance, have you come across migration of following business objects?
• Employee contract details (can be accessed through ‘Extra Details of Service’ on Assignment screen)
• Employee work schedule
If yes, could you please let me know the API name or any alternate method you used to migrate the data.

Hi stranger!

pqp_aat_api.create_assignment_attribute will load your contract type info - will also do work pattern

Work schedule, I am not sure about - what's the base table for that data, would you know or be able to find out? Or a screen navigation path?

Hello - thanks for that this is great!

There seems to be more than one base table:
CAC_SR_SCHDL_OBJECTS ,
CAC_SR_PUBLISH_SCHEDULES and
CAC_SR_SCHDL_DETAILS

navigation path:HRMS Manager
Assignment>others>assign schedules

It's a self service screen

Hmm, I don't see that menu path here... is this some sort of custom taskflow?

hello - well after further investigation it seems that our local funkie has used a US form to capture workschedules...need I say more.

On another note - There are two procedures in HR_ASSIGNMENT_API for uploading employee assignment: update_emp_asg and update_gb_emp_asg

Should I be using the GB specific one or can I use the generic update_emp_asg?


Any advice would be great

Ahh, bless... some attitude re-engineering needed then, by the sound of it. Just make sure you him him where he won't bruise externally...

As far as the api is concerned, it kind of depends if you are wholly uk legislation I guess. In any case, you can use either, as I believe update_gb_emp_asg ultimately calls the core update_emp_asg anyway, once it's done a check that the relevant business group is of a UK legislation.

Thanks for this perfect! just a little confused as to why Oracle did not provide 'assignment_status' parameter in GB.

Cheers

Actually, assignment status changes are handled via a different API : hr_assignment_api.activate_emp_asg (for changing to some shade of 'ACTIVE_ASSIGNMENT' status), and suspend_emp_asg (for changing to some shade of 'SUSPEND_ASSIGNMENT')

Edit: To clarify, the activate_emp_asg and suspend_emp_asg APIs deal with switching to a different SYSTEM_STATUS, e.g. from SUSPEND_ASSIGN to ACTIVE_ASSIGN, and vice versa. The parameter p_assignment_status_type_id in the update_emp_asg API deals with switching to a new user_status, but still the same system_status.

As for why it's not a parameter in the update_gb_emp_asg, I can only presume that the parameter is a recent addition to the core API, and they missed a trick with making the same change to the GB wrapper. I can't think of a logical reason for wanting to exclude UK legislation from changing it.