Scenario :

Procurement has gone live prior to HR.

Problem :

There are a number of employees in the system with a random start date (the date data was entered) to enable them to function as purchasers.

Now the HR data migration has to set the correct hire date.

On the People form you will notice that you can update the "Latest Start Date" field in the bottorm right hand corner with a earlier or later date , save as correction and Oracle adjusts the effective_start_date accordingly.

Is there an API than can achieve this because I cannot find a data pump parameter for setting latest_start_date.

I have tried original_hire_date etc but this just updates the "Date First Hired" field on the Benefits tab

Please let me know if you have encountered this issue.

Any fixes? Thanks for your help

Cheers
Vin

Surely this is the date from the period of service (PPS) row that is being displayed? So it will not appear on any of the people/employee API's.

I can't remember if there is a PPS api lurking? If there is it is probably an internal developer one. In which case you could either hack DP to generate an API interface for the internal API, or write a user-hook onto the employee API to go and do the update of the PPS row.

Of coursse, if it has nothing to do with the PPS record, and you are still stuck with no DP parameter, then the user-hook route may well be your only option.

For historic reference, i remember having this situation at Yorkshire Building Society (Eons ago), when financials went in before HR/Pay. In this scenario (and it pre-dated DP by many years) we ended up hacking the dates as part of the API wrapper script process (ah, those were the days <img src="/ubbthreads/images/graemlins/smile.gif" alt="" /> )

The PERWSHRG form uses the following API to apply the changes made to latest start date field.

hr_change_start_date_api.update_start_date.

However this isn't in the standard supported API documentation

Eg :

hr_change_start_date_api.update_start_date
(p_validate => FALSE
,p_person_id => r_person.person_id
,p_old_start_date => r_person.date_start
,p_new_start_date => l_new_start_date
,p_update_type => 'E'
,p_warn_ee => l_err_msg);

Vin - that might be an oversight in the API doc. Given that the package ends in '_API' and there's a p_validate parameter, that to me suggests it's in the public domain.