Previous page

Next page

Allocation Process

Summary

When you open a Roster period and you have set Build allocations when opening roster period to Yes, PayGlobal generates timebands for employees based on their default roster. PayGlobal populates each timeband’s Requirement Tour Code and Requirement Code from the employee’s default roster.

The Open Roster process has two phases for each date:

  • Phase 1 determines which of the employee’s default roster tables to use.
  • Phase 2 determines the value for each timeband field.

Process Flow

Allocation Process

Phase 1

You can store an employee’s default roster in the following tables:

  • Employee Tour
  • Employee Shift
  • Employee Timeband Overrides.

When you open a Roster period (or view the employee’s default roster in Daily View for an unopened roster period), PayGlobal derives the roster from these three tables. The employee’s roster can be specified in three places so they may have more than one roster for the same date. PayGlobal uses a hierarchy to determine which roster has priority.

When PayGlobal creates the roster timebands, it uses data in the following order:

  • Employee Timeband Overrides
  • Employee Shift
  • Employee Tour.

For example, if the Employee Timeband Override has a record for 10 May 2009, and the Employee Tour has a record for the same date, then PayGlobal uses the roster in the Employee Timeband Override, and disregards the roster for the same date in the Employee Tour.

Phase 2

After PayGlobal determines which table it will source roster data from for each date, it can generate the timebands. However, the value for each field on the timeband can be specified at several levels.

Phase 2 – Employee Timeband Override

If the roster timeband(s) for a particular date come from the Employee Timeband Override, then PayGlobal uses only Employee Timeband Override values for the timeband fields.

If you specify the employee’s roster in the Employee Timeband Override table, then you must also specify the Requirement Tour and the Requirement that it will fulfill.

Phase 2 – Employee Shift Override

If the roster timeband(s) for a particular date come from the Employee Shift Override, then PayGlobal uses values from the following records for the timeband fields (in hierarchical order):

  • Shift timeband record(s)
  • Employee Shift Override record.

If you specify a timeband in the Employee Shift Override table, then you must specify the Requirement Tour and the Requirement that it will fulfill on either of the following:

  • Shift timeband record(s) (applies to all employees using this Shift)
  • Employee Shift Override record (applies to this employee only).

Phase 2 – Employee Tour

If the roster timeband(s) for a particular date come from the Employee Tour, then PayGlobal uses values from the following records for the timeband fields (in hierarchical order):

  • Shift timeband record(s)
  • Tour Shift makeup record
  • Employee Tour record.

If you specify a timeband in the Employee Tour table, then you must specify the Requirement Tour and the Requirement that it will fulfill on either of the following:

  • Shift timeband record(s) (applies to all employees using this Shift)
  • Tour Shift makeup record (applies to all employees using this Tour)
  • Employee Tour record (applies to this employee only).

Previous page

Next page