Schedule compliance validation on MR processing
MR schedules are validated before processing for schedule compliance issues and schedule publishing conflicts. With this validation, you can revise the schedule to correct compliance errors, review warnings, and resolve conflicts before publishing any shifts.
You can also configure the validation date range used during MR processing to ensure that only relevant dates are validated.
These registry parameters determine the validation date range:
- MR_PROCESS_VALIDATION_START_DATE
- This registry parameter determines the baseline start date for MR processing validation. You can set it to PAYGRP_CUTOFF to use the same cutoff date that is used for schedule editing in MVS. This is the same cutoff date set in the PAYGRP_CUTOFF_DATE registry parameter. You can also set MR_PROCESS_VALIDATION_START_DATE to CURRENT_DATE to use the current date. The start date is determined by the date specified here plus the number of offset days specified in MR_PROCESS_VALIDATION_OFFSET_DAYS.
- MR_PROCESS_VALIDATION_OFFSET_DAYS
- This registry parameter determines how many days to offset the validation start date. Validation starts on the date specified in MR_PROCESS_VALIDATION_START_DATE plus the number of days specified in this parameter. You can set the to 0 to use the exact start date.
- MVS_PUBLISH_LOCK_LENGTH
- This registry parameter determines the number of days that are validated before processing an MR, starting on the start date defined by the other registry parameters. This also determines how many days of employee schedules are locked when publishing MR schedules.
Note: You must set the validation date range to match or exceed the date range used for the MR publishing tasks. To ensure full coverage of the publishing period, align the validation start date with the start date of the short-term publishing tasks.