Auto-placement

PayGlobal can perform the following processes for each pay sequence that you open, if you configure the required settings:

• Runs a Requirement Check.
• Sets up the Default Roster.

Requirement Check

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

1. Checks that the Requirement is active for this date.

   If a start date is defined for the Requirement, the date being considered is only accepted if it is:

   • An even multiple of days after the start date.
   • Attached to a Requirement Tour.

   For example, if the Requirement start date is a Monday, and the Requirement frequency is 7, then an Allocation is only generated if the date being considered is also a Monday.

2. Checks that each Requirement Tour is active and uses the start date to determine the current day of the cycle. 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. If this Requirement is defined on the Requirement Tour | Requirements tab for day number 3, PayGlobal creates an Allocation record for this date and Requirement.

   Note: If an override list of timebands, qualifications, and/or competencies are defined for this requirement, they need to be copied into the Allocation Override table.

Default Roster

The default Roster for every matching employee is generated for each date in the current pay sequence. For each employee code 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 pay sequence, the timebands are loaded from the Historical Roster Timeband table.
   • If the date is in an open pay sequence, the timebands are loaded from the Current Roster Timeband table.
   • If the date is in an unopened sequence and records exist for this date, PayGlobal:
     • Loads timebands from the Employee Timeband Override table

     -or-

     • Loads timebands from the Employee Shift Override table.
   • If the date is in an unopened sequence and no records exist for this date, PayGlobal checks each employee Tour in increasing order of rank and loads timebands for the first shift on a Tour that is either:
     • Active for this date
     • Has a Tour Shift for the day number that this date occurs in the employee's Tour cycle.
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. If it does, the Allocation is included.
   • Determines the effective Requirement and Requirement Tour for the timeband.
   • If this Requirement and Requirement Tour have an Allocation, PayGlobal:
     • Stores the Allocation in the timeband.
     • Adds a record to the Allocation Allocated table to indicate that one of the allocation’s requirements has been met.
     • Sets the From Default Roster field to 'True'.
   • Saves the timeband in the Current Roster Timebands table.
   • Loads Availabilities.
   • Saves Availabilities.

Topic: 13507