We are using the standard create_person_absence to load SSP absence records but because we have no NIable pay history no SSP will be created. We want to load a default Average Earnings how can we load this default through an API? . .We also need to override any stoppages created is this possible? If so how. . .Normal sexual favours.....

To the best of my memory (such as it is) it's something to do with the table SSP_AVERAGE_EARNINGS or summat like that. No standard API as far as I am aware.

You could always try the aincent standby of: . ."bung the stuff in manually you dumbass users cos you ain't got millions of them and 10 days of your time is much less than 2 days of <insert name>'s time" . .Avg earningn and stoppages can be entered neatly throught the form

Mr Farrar as ever a valid point eloquently put. I trust you are well btw. . .One thing to be aware of though. regardless of how you enter these values: . .If you create any open-ended (e.g. long term) sickness absences then what you will end up with is a shed-load of ssp payments element entries (that are historical in nature) created in the current pay period. Unless you cancel them out with a user-defined stoppage reason they will be processed. Which might make for a highly amusing parallel run.

Col . .We have used the following.... . .ssp_ern_ins.ins and ssp_ern_upd to populate ssp_ernings_calculations - you have to reset session date to be the absence date as you call this code to prevent the problem CT mentioned. . .This is due to triggers on the ssp_ernings_calculations table call the ssp_smp_support_pkg.recalculate_ssp_and_smp (insert) and ssp_smp_pkg.earnings_control that create the element entries. . .Also used the ssp_stp_upd to update stoppages. . .Your only problem with setting a default value will be when a user hits the 'Recalc' button in the absence form then the app will use payroll results to calc average earnings or when they enter a new absence? We had to migrate avg earnings into a custom table and then run a custom job to recalc earnings before each payroll runs which took into account history and values calculated by oracle. . .HTH . .Jay

Jay . .Thanks for that will give it a whirl. With regards the users hitting the 'Recalc' button we'll just tell them not to!! . .Col.

Col . .That should cover it - just make sure they don't enter new absences until there is enough payroll history in Oracle to calc avg earnings. . .Jay