MR validation period examples
These examples demonstrate different validation periods that can be configured.
Validate for one year starting on pay period start date
This configuration validates MRs for 365 days starting on the pay period start date. This configuration is useful when MR schedules are published starting on the pay period start date.
| Registry parameter | Value |
|---|---|
| PAYGRP_CUTOFF_DATE | PAYGRP_START_DATE |
| MR_PROCESS_VALIDATION_START_DATE | PAYGRP_CUTOFF_DATE |
| MR_PROCESS_VALIDATION_OFFSET_DAYS | 0 |
| MVS_PUBLISH_LOCK_LENGTH | 365 |
If the pay period start date is January 1, 2019, an MR would be validated from January 1, 2019 to January 1, 2020.
Validate one year from current date with one week offset
This configuration validates MRs for 365 days starting one week after the current date. This configuration validates for schedule compliance issues or conflicts when MR schedules are published one week in advance.
| Registry parameter | Value |
|---|---|
| MR_PROCESS_VALIDATION_START_DATE | CURRENT_DATE |
| MR_PROCESS_VALIDATION_OFFSET_DAYS | 7 |
| MVS_PUBLISH_LOCK_LENGTH | 365 |
An MR processed on January 1, 2019 would be validated from January 8, 2019 to January 8, 2020.
Example: Validate one year starting from two weeks ago
This configuration validates MRs for 365 days starting two weeks before the current date. This can be useful if there are schedule compliance rules restricting the number of consecutive days that may be scheduled.
| Registry parameter | Value |
|---|---|
| MR_PROCESS_VALIDATION_START_DATE | CURRENT_DATE |
| MR_PROCESS_VALIDATION_OFFSET_DAYS | -14 |
| MVS_PUBLISH_LOCK_LENGTH | 365 |
An MR processed on January 1, 2019 would be validated from December 18, 2018 to December 18, 2019.