ASSIGNMENT LEAVE SPLITS#
Overview#
This feature was created to allow Secondary Assignment records to be split when an employee goes on Leave.
Features#
This process is controlled by whether the customer has the trigger P2K_EASD_ARI in place or not. When in place and a new effective date split happens on the details of the Prime Assignment, a backend job will be launched from P2K_PEGEN.Schedule_Job using the DBMS_SCHEDULER functionality. NOTE: the record must have a date split or this will not work.
The job is necessary as you cannot query against a table from a trigger on that table, it launches with a 7 second delay to ensure all records are committed from the initial processing.
The job executes the procedure P2K_PEGEN.LeaveChangeCheck which will get the Status Type for the new record and for the record that expires one day prior to this new record and checks if one exists for a type of ‘A’ and one is a type of ‘L’ and if so, will call P2K_PEGEN.LeaveSplits.
P2K_PEGEN.LeaveSplits first turns off Work Flow by setting the P2K_PMWRKFLW.bypassWorkFlow flag to ‘TRUE’. Then it sets up and calls the procedure P2K_SMDSCOPY for each of the Non-Prime assignments that are not End Dated. The record is then updated with the new Change Reason and Employment Status. NOTE: This process will NOT touch future records, it will only split the record that exists at the date of the status change.
Setup#
- SYS_UPGRADE.sql must be run to grant new privilege of CREATE JOB to P2K ad P2K_USER.
DB Changes#
- P2K_EASK_ARI_LEAVE_SPLIT.sql contains TRIGGER P2K_EASD_ARI which controls whether this process is in place or not and kicks off the job.
- the fields EASD.LEAVE_DATE and EASD.LEAVE_RETURN_DATE have been added to the process to be updated on the splits of the secondary assignments.
Click to create a new notes page
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation