Re-validating schedule compliance based on non-MVS changes

Schedule compliance can be re-validated for non-MVS changes. These include changes to an employee's schedule that are made outside of MVS (for example, due to a change in the employee's shift pattern) and employee profile changes that affect schedule compliance.

Note: To re-validate schedule compliance based on non-MVS changes, the administrator must set the REVALIDATE_NON_ADV_SCHED_CHANGES registry parameter to true. By default, this parameter is set to false (schedule compliance is not re-validated for non-MVS changes.). See REVALIDATE_NON_ADV_SCHED_CHANGES" in the Infor Workforce Management Registry Parameter Reference Guide.

If enabled, the schedule compliance re-validation is triggered whenever an applicable change is made outside of MVS (see Applicable changes). You can then view the up-to-date schedule compliance violations by viewing employee schedules in the ASV.

Applicable changes

These non-MVS changes can affect an employee's schedule:

  • Changes to an employee's shift pattern on the Employee Basic Information - Override page, if default records exist before the schedule change. If default records do not exist for the date range being calculated, the employee's schedule will not be updated until default records are created.
  • Schedule overrides on an employee's timesheet. These include all 400-level overrides except Schedule Detail, which is already used by MVS to trigger schedule compliance.

When an employee's profile is updated though the Employee Basic Information - Override page or the Employee Import, changes to any of these attributes can affect schedule compliance:

  • Employee's age
  • Employee EMP_VAL values
  • Employee EMP_FLAG values
  • Employee's calculation group

These attributes correspond to the core schedule compliance filters, which determine the set of schedule compliance rules that are applicable to an employee.

Date range for re-validation

An override that changes an employee's attributes or schedule has effective dates.

When schedule compliance is re-validated for non-MVS changes, the start date is the effective start date of the override incurring the change, or the current date, whichever is later. The end date is the effective end date of the override incurring the change, or the latest schedule date of the employee, whichever is earlier.

For example, an employee's EMP_FLAG5 attribute is updated with effective dates of June 1, 2018 to January 1, 3000. If the current date is March 28, 2018, and the latest date on which the employee has a schedule is March 27, 2019, then the re-validation date range is June 1, 2018 to March, 27, 2019.

Note: Schedule compliance violations are not reported for dates in the past. Adjustments to schedules to return employees to compliance should be made only for future schedules.

Skipping error rules

The automatic schedule compliance re-validation skips any rules configured at the error level and therefore does not report any schedule compliance errors. This prevents an employee's schedule from going into a "deadlock" situation, where a compliance error prevents any further schedule transactions. There could be situations where a schedule would require multiple shift transactions to become compliant again.

You will be notified of error situations when you make your next schedule edit. You can then update the schedule to make it compliant again, or work with the system administrator to temporarily disable the compliance rules just to make the schedule adjustments to return the schedule to a compliant state.