![]() |
![]() |
|
This section outlines the Requirement Tour Requirements | Details tab.
The fields on this tab page are optional. Complete them only if you need to override the default settings.
Field |
Description |
|---|---|
Day number |
The day number in a Requirement Tour that this Requirement occurs. For example, the record could relate to day four of a seven-day cycle. |
Requirement Code |
A Requirement may be associated with the day selected above, within a Requirement Tour. |
Date |
Date the Requirement Tour starts. |
Frequency |
Frequency should always be 1. |
Effective end date |
The last date for a day within a Requirement Tour (if known). |
Rank |
This field allows you to set a rank for multiple Allocations generated for a Requirement on the same day. The Rank controls which shifts on a particular day take priority. For example, when you rank one shift higher than another, PayGlobal will attempt to roster employees for the day to the higher priority shift first. When you use auto-placement, Allocations for the same day are filled in ascending order of rank. Rank is only used to differentiate between Allocations for the same day. |
Note: If you regenerate Allocations using Maintain Allocations, the rank of the previous instance of the Allocation is retained — even if it was reset. |
|
Break |
The unpaid break applicable to a Requirement Tour day. For example, Lunch. |
Shift |
The Shift that will apply to the Requirement Tour day. |
Reason |
To associate a reason code to a Requirement day. |
Placement Criteria |
Placement Criteria filters employees so that only employees who are suitable to fill the Requirement are displayed. |
Placements required |
The number of employees needed to fill the Requirement. If you want to specify the number of employees required in each Requirement, leave this field blank. PayGlobal checks for information in the following order: You should specify data at the lowest level to avoid duplicate entries and to reduce future editing. |

|
|
Topic: 13043