Pay period cutoff date in MR and OTS

MR and OTS perform validations to ensure that certain actions can only be performed after a specified cutoff date. The cutoff date is associated with a pay group. This prevents changes to an MR or OTS from creating retroactive changes to employee timesheets in pay periods that have passed.

These validations include:

Users may edit shifts in an OTS before the cutoff date. When an OTS schedule is processed, the schedule is published from the start date to the end date of the OTS schedule. It is important to note that any retroactive shift edits before the cutoff date would be published to the timesheet when an OTS is processed.

Users may activate row versions in an MR before the cutoff date, but the short-term publishing task uses the cutoff date as the starting point for publishing schedules from an MR. Edits to shifts in an MR are not published to the timesheet before the cutoff date.

The pay group and the type of cutoff date to use are configured in the registry. The pay group used to determine the cutoff date is configured using the PAYGRP_NAME registry parameter. The default pay group (value "0") must be updated using one of the client's actual pay groups. Because this configuration affects all MR or OTS schedules, it is recommended to use the pay group where the specified cutoff date occurs earliest.

The cutoff date is configured using the PAYGRP_CUTOFF_DATE registry parameter. The default value is PAYGRP_HANDS_OFF_DATE, which uses the hands off date. The cutoff date can be changed to a different date, such as the adjust date or pay period end date, if required by the client.