When the "Pay Calendar" is incorrectly set up, the "Month End" and "Year-End" processes can fail and cause record Locks, However, data is not affected.

We need to add the following validation to the Pay calendar:

The purpose of this validation is to ensure that the calendar for all periods that the employee started is properly setup.

This is used in the month/year rollover process to carry forward leave.

Calendar rules:

1. "Start Date" must be the first day of the month.

2. "End Date" must be the last day of the month.

3. Next period "Start Date" must be 1 day after the current period "End Date".

4. All years in the pay calendar needs to be valid.

As part of the upgrade, we need to add a correction script to correct the pay calendar if it is invalid.

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0111

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. Added a new function to check if all the calendar entries are correctly set-up using the following rules:
   1. "Start Date" must be the first day of the month.
   2. "End Date" must be the last day of the month.
   3. Next period "Start Date" must be 1 day after the current period "End Date".
   4. All years in the pay calendar needs to be valid as the Rollover checks leave has correctly rolled over since the Employee started work.
2. When closing a period, we validate the "Pay Calendar" and let the user know if the calendar is invalid. The user is then required to contact their reseller to correct the issue. We do not expect this to happen due to item 3 below.
3. We have added an upgrade script that will recreate the calendar correctly if there is an issue
4. A log entry will be created stating the change journal.

3. Affected Areas:

1. Pay Calendar
2. Upgrade to V12.30 when the calendar is invalid

4. The issue was caused by:

1. TLTB reported a system issue when closing 2020 Year

5. Notes: 
6. Next Step: System test and UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N): Y

2. Variations to the approved design: N/A

We have reviewed the design and decided that automatically changing/correcting the Period dates will cause confusion.

The new design agreed is:

1. When an entry in the Pay Calendar is invalid, users with edit access to Pay Calendar will be able to correct the "Start and END" dates
2. Period Close will check if the pay calendar is valid and instruct the user to correct this before closing the period.

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0112

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. Enabled EDIT of Pay Calendar START and END dates when the Pay Calendar has invalid dates
2. Added check to prevent Period CLOSE if the pay calendar is invalid
3. The message will indicate the invalid period.

3. Affected Areas:

1. Pay Calendar Period Close

4. The issue was caused by:

1. Fix of Pay Calendar Invalid Periods

5. Notes: 
6. Next Step: UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N): Yes

2. Variations to the approved design: NA

UAT by Alvis and Sanjay

UAT Notes

1. Created an environment where Period 12 for 2021 is incorrect (30/12/2021)
2. Tried to close a period. Pay calendar validation message received
3. Incorrect periods are displayed in RED and the Period Dates are editable
4. Edited period 12 and corrected the date
5. Closed pay period successfully