Summary

When you open a roster pay period, default roster timebands are generated for the applicable date range of the pay sequence. PayGlobal also builds allocations if you set Build allocations when opening roster period to Yes on the Periods entity. See Periods - Details.

Note: Allocations are not defined for any one roster period or pay sequence. An allocation is defined for a day and you must ensure that all allocations exist for the period of time the pay sequence covers before you open it.

When you open a roster pay period, PayGlobal performs the following processes for each pay period that you open.

Note: This applies if you have configured PayGlobal to build the allocations when opening the roster.

Requirement Check

The Requirement for each date is checked to see whether it will generate an Allocations record. For each requirement and date, PayGlobal completes the following:

Requirement Tours

PayGlobal completes the following steps:

1. Identifies current Requirement Tours where the dates fall within the period date range.
2. Checks each date in the date range of the Requirement Tour and identifies the date's day number within each Tour. For example, if the Requirement start date is a Monday, the Requirement Tour duration is 7, and the date being considered is a Wednesday, then the current day of the cycle is day 3.
3. Checks if this Requirement is defined on the Requirement Tour | Requirements tab for a valid date that is within the period date range.
4. If the date on the Requirement Tour | Requirements tab is valid for the specified date range, it checks whether an Allocation already exists.
5. If no Allocation exists, builds the allocation in the following order:
   • Requirement Tour Requirement
   • Requirement Tour
   • Requirement

   For example, if a value is not found on the Requirement Tour Requirement, PayGlobal checks the Requirement Tour and then the Requirement.

6. If an override list of competencies is defined for the Requirement, then copies it across to the Allocation.

Stand alone Requirements

PayGlobal completes the following steps:

1. Identifies current Requirements where the dates fall within the period date range.
2. Checks each Requirement in the date range; checks whether an Allocation exists for that Date and Requirement Code and checks that no Requirement Tour is specified.
3. If no Allocation exists, creates an Allocation, deriving it from the Requirement table.

   Note: The stand alone Requirement must have a Shift and Location code. If these fields are blank, the Shift and Location codes of the allocation are derived from the employee's Shift and Location.

4. If an override list of competencies are defined for this Requirement, then copies it across to the Allocation.
5.  

Default Roster

The default roster for every matching employee is generated for each date in the current pay sequence. For each employee and date, PayGlobal completes the following:

1. Loads the employee’s default roster for this date and the previous date.
   • If the date is in a closed sequence, timebands are loaded from the Historical Roster Timeband table.
   • If the date is in an open sequence, timebands are loaded from the Current Roster Timeband table.
   • If the date is in an unopened sequence and records exist for this date:

     - Timebands are loaded from the Employee Timeband Override or the Employee Shift Override table.
     - checks each employee tour in increasing order of rank.
     - loads timebands for the first shift on a tour that:
     a. is active for this date.
     b. has a Tour Shift for the day number that this date.

2. Saves the roster. PayGlobal does the following for each timeband in the day for the employee:
   • Determines if this timeband meets a requirement for this day by comparing the requirement tour and requirement specified for the timeband to the allocation records for the same date. If there is a match, then PayGlobal:

     - Stores the AllocationID in the timeband.
     - Adds a record to the Allocation Allocated table to indicate that one of the allocation’s requirements has been met.

     - Increases the Alloc counter by 1.
     - Sets the From Default Roster field to True.

   • Saves the timeband in the Current Roster Timebands table.
   • Loads availabilities.
   • Saves availabilities.