Last Phoned/Worked Update

The Last Phoned/Worked Update will read through all the dispatches for current date and update both the last phoned and last worked dates attached to substitute/casual preference records with the current date and time.

This process only needs to be run if you are sorting dispatch employees by either last phoned or last worked dates. This process becomes important when you have the situation where an employee is dispatched for several days at a time. The example below will attempt to show the relevance of this process.

We have decided to sort qualified replacement employees by last phoned date so that all employees will have an equal opportunity to work.

Employee 1 is dispatched for 5 days beginning Monday January 9th and ending Friday January 13th. When the dispatch is made this employee's preference record will be updated with the last phoned date of the time the dispatch was created. Let's say this was 09-Jan-1999.

Two days later Employee 2 is dispatched for a single day beginning and ending on Wednesday January 11. When the dispatch is made this employee's preference record will be updated with the last phoned date of the time the dispatch was created. Let's say this was 11-Jan-1999.

The following Monday January 15th we need a replacement employee to fill an absence. Both employees 1 and 2 are qualified and available. Without running this process, the last phoned date of each employee is as follows:

Employee        Last Phoned Date

1                      09-Jan-1999

2                      11-Jan-1999

Because we chose to sort all qualified available employees by last phoned date, the system will sort and find employees based on this date, earliest date first. This, under normal conditions, will give all employees equal opportunity. In this case however, employee 1 has the earliest last phoned date and will be selected first even though he/she worked more recently than employee 2.

The Last Phoned/Worked Update process will remedy this problem by updating each employee's preference record with the last date they worked as opposed to when they were called. Thus, because employee 1 worked on Jan-13-1999, this date will be placed on the employee's preference record so that employee 2 will be selected before employee 1.

For this process to be effective, it must be run every working day before you begin the day's dispatching. Please call ATRIEVEERP on information on how this process can be set up to run automatically every morning before you come into work.

Employee Categories

Include Eligible Substitute/Casual/Both/Neither

Dispatch Positions

Dispatch Position Subjects

Enter up to 10 subject codes. Only dispatches that have a position containing as its first subject, the subjects entered here will display on this report. Search for valid subject codes. If you do not specify any subjects, dispatches will be selected regardless of their position subjects.