The purpose of this process is to cause the Replacement Employee Costing Process to skip the creation of timesheets for Priority TOCs (PTOCs) who are dispatched on their regularly scheduled PTOC days. This is desired functionality because these employees are paid via function line for their contractually agreed upon (scheduled) PTOC time, and not by timesheet. Any dates that are NOT in their PTOC schedule, will still have their timesheets created via the costing process. For example, if an employee’s regular PTOC schedule is Monday, Wednesday and Friday, and there are dispatches in the system for Monday and Tuesday, the costing module will not create a timesheet for Monday but will for Tuesday. Monday’s dispatch will be skipped and marked as interfaced.
The immediate purpose of this process is to convert and store the PTOC schedule in a format that is performant enough to access within the Replacement Employee Costing Process.
Important Note: This Replacement Employee Costing module will only reference the PTOC schedule (and perform the PTOC skipping logic) if field 07= SKIP PRIORITY TOC DISPATCHES IN REP EMP COSTING MODULE on page 4 of the SUBSTITUTE/CASUAL DISPATCH PARAMETERS PROFILE is set to Y.
Description of how the Priority TOC Schedule Update Process works:
This program will read through all employees that have an ACTIVE substitute/casual preference record, and who are in the specified employee categories (as per their demographic employee category). If either of these checks fail, and the employee is skipped, their PTOC schedule record will be blanked out so as not to potentially leave an old PTOC schedule in place should their category/substitute-casual preference/assignment/schedule data change.
After the above category/substitute casual preference filtering has taken place, the employee’s assignments will be read. Assignments will be skipped if the assignment:
· Is not current as of the specified start/end date range
· FTE is less than .01
· Hours per day is less than .01
· Has no schedule
· Type is marked as a leave
· Position is not in the specified list of ASSIGNED POSITIONS (10) if at least one specified
· Location is not in the specified list of ASSIGNED LOCTIONS (10) if at least one specified
· Position is not in the specified list of ‘POSITIONS TO INCLUDE IN SCHEDULE’
Any dispatches that fall on PTOC schedule dates will be skipped, marked as interfaced, and show up in the costing exception report with the notation of ‘Priority TOC Dispatch Will Be Skipped And Marked As Interfaced’.
This program should be configured to run on the customer’s system nightly to ensure the PTOC schedule is always up to date.
Note: The program will likely select more employees than match your selection criteria, because it will blank out the schedules of employees that are no longer selected i.e. because their substitute/casual preference, category or assignments have changed since last running the program. For example, if you have a PTOC today, then their PTOC schedule record is created and updated. If something changed on that employee before tomorrow's run, that would exclude them from being selected/updated, then their PTOC schedule record from yesterday would still incorrectly exist. So the program will still process employees like this and blank out schedules for employees that are not really selected.
It is recommend when configuring for new customers to leave the category selection blank, and specify both the ASSIGNMENT POSITION and POSITIONS TO INCLUDE IN SCHEDULE.