| Subject: | When allocating Leave to Employee, some Leave Codes do not get a "Leave Start Date" and "Leave End Date" allocated. |
| Summary: | Hi Team,
When allocating Leave to Employee, some Leave Codes do not get a "Leave Start Date" and "Leave End Date" allocated.
Issue Description
New Company was created 1008
Setup Calendar from July 2023 to June 2024 (2024 Fin Year) to test Leave Rollover.
Start Date | End Date | Year | Period | Description | Period Closed | Year Closed | Status | 01/07/2023 | 31/07/2023 | 2024 | 1 | Jul-23 | FALSE | FALSE | Open | 01/08/2023 | 31/08/2023 | 2024 | 2 | Aug-23 | FALSE | FALSE | Open | 01/09/2023 | 30/09/2023 | 2024 | 3 | Sept-23 | FALSE | FALSE | Open | 01/10/2023 | 31/10/2023 | 2024 | 4 | Oct-23 | FALSE | FALSE | Open | 01/11/2023 | 30/11/2023 | 2024 | 5 | Nov-23 | FALSE | FALSE | Open | 01/12/2023 | 31/12/2023 | 2024 | 6 | Dec-23 | FALSE | FALSE | Open | 01/01/2024 | 31/01/2024 | 2024 | 7 | Jan-24 | FALSE | FALSE | Open | 01/02/2024 | 28/02/2024 | 2024 | 8 | Feb-24 | FALSE | FALSE | Open | 01/03/2024 | 31/03/2024 | 2024 | 9 | Mar-24 | FALSE | FALSE | Open | 01/04/2024 | 30/04/2024 | 2024 | 10 | Apr-24 | FALSE | FALSE | Open | 01/05/2024 | 31/05/2024 | 2024 | 11 | May-24 | FALSE | FALSE | Open | 01/06/2024 | 30/06/2024 | 2024 | 12 | Jun-24 | FALSE | FALSE | Open | 01/07/2024 | 31/07/2024 | 2025 | 1 | Jul-24 | FALSE | FALSE | Open |
Setup - Created Employee E001 (Start date - 26/09/2022).
- Created Leave Codes: AAL12, INSL, LWOP, TBL, TSL.
- Upon allocation below is how leave allocation dates are reflected;
Leave Code | Rollover Method | Start date | End date | Annual Leave Executive - 12 [AAL12] | Anniversary | 26/09/2025 | 25/09/2026 | Inpatient Sick Leave [INSL] | Calendar | Not picked | Not picked | Leave without Pay [LWOP] | Calendar | Not picked | Not picked | Bereavement Leave - TIDH [TBL] | Calendar | Not picked | Not picked | Sick Leave - TIDH [TSL] | Calendar | Not picked | Not picked |
Summary as below in reference to case E03263; - Company 1007 (Fin Year 2027)
After the test, leave accrual for AAL, rollover for AAL, ABEAV and ASL did not happen - Company 1008 (Fin Year 2026)
After the test, leave accrual for AAL, rollover for AAL, and ASL successfully happened
Rollover for ABEAV did not happen as Calendar year was configured in leave code setup - Another employee 14035 was created in Company 1008
After the test, leave accrual for AAL, rollover for AAL, ASL and ABEAV successfully happened. Company 1008 (Fin Year 2024) Upon leave allocation, leave allocation dates are not reflected correctly
Company 1008 Setup is replica of Company 1006 of Reddy Enterprise Machine 2 LINKSOFT-DSS-MTR |
| Audit Notes: | Edited by sanjay on 04/08/26 17:25. Edited by sanjay on 04/08/26 17:25. Edited by sanjay on 04/08/26 17:23. |
| 27 Jul 2026 | 03:54PM Comment 1 by Monica Wati (Edge Business Solutions) Comment removed by sanjay |
| 04 Aug 2026 | 09:42AM Comment 2 by Sitla (Edge Business Solutions) Comment removed by sanjay |
| 04 Aug 2026 | 09:45AM Comment 3 by Monica Wati (Edge Business Solutions) Comment removed by sanjay |
| 04 Aug 2026 | 05:17PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 05-08-2026 04:43 PM Time Taken: 4.00 |
| Hi Monica, the reason you are having this issue is because your Calendar in company 1008 is not setup or the current year. All leave types that are of type "Calendar" will try and line up the Leave Start and Leave END dates with the current calendar. Aniiversary Leave Types are ok because it uses the Employee Start date instead of the current year. |
|
| 04 Aug 2026 | 05:22PM Comment 5 by Sanjay (Link Technologies) Case L13274 added to project 16.04 |
| 05 Aug 2026 | 02:06PM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 05-08-2026 08:01 PM Time Taken: 12.00 Notes: ETC extended from: 04/08/2026 to 05/08/2026 |
| PART A - Development work for this case has been completed. 1. The change will be available in version: 16.04 and Patch: 16.03.260805 2. The following changes were made (Include Database object names, Program classes, and any other relevant information): - When allocating leave, if the "Leave Date From" or "Leave Date To" defaults are unavailable, we make the date fields editable.
- When Saving a Leave Allocation, we now require a VALID "Leave Date From" and "Leave Date To"
3. Affected Areas: - Leave Allocation - Add new Leave to employee
4. The issue was caused by: - In some cases, if the Pay Calendar is not setup, the Default values are not available, or empty.
5. Other Relevant Notes:
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT
|
|
| 10 Aug 2026 | 09:33AM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 10-08-2026 03:31 PM Time Taken: 2.00 Notes: ETC extended from: 05/08/2026 to 10/08/2026 |
| *** Teams message from Monica ***
Hi Sanjay, Just a clarification for case E03271 All leave types that are of type "Calendar" will try and line up the Leave Start and Leave END dates with the current calendar. The current Calendar is July 2023 - June 2024 and Fin year is 2024. So are you saying the system will pick 2026 or the system will pick this year (2024)? What will happen if we setup a company and bring in history data? How will that be handled if the system is looking at the current Calendar which is 2026 *** Sanjay ***
Hi Monica, Usually we use the "Opening Balance" for the current year, that's how we have done it in the past. But you make a good point. I will look into using the "Pay Control Year" as the date.
I will reopen case L13274 and add this change in. |
|
| 10 Aug 2026 | 03:03PM Comment 8 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 10-08-2026 08:58 PM Time Taken: 18.00 Notes: Edited by sanjay on 12/08/26 10:19. |
| PART A - Development work for this case has been completed. 1. The change will be available in version: 16.04 and 16.03.260812 2. The following changes were made (Include Database object names, Program classes, and any other relevant information): - When adding leave allocation, we determine the DEFAULT Leave Dates based on the current "Pay Control" period.
- If any of the dates are not valid or cannot be determined, we allow the user to EDIT the fields manually.
- Added validation to ensure the Employee's Pay Team is in a valid Pay Calendar
3. Affected Areas: - Employee Leave Allocation
4. The issue was caused by: - Previously, if the Calendar was not setup for the current year, we could get dates that are invalid.
- Previously, we used the current date to determine Anniversary Leave defaults. We have changed this to use "Pay Control" to allow for History Pay Processing.
5. Other Relevant Notes:
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT
|
|
| 11 Aug 2026 | 01:12PM Comment 9 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-08-2026 07:12 PM |
| UAT completed by DEV team. |
|