Company: Link Technologies
Case No: L13127. Project: 15.70: LinkSOFT Version 15.70
Logged By: Sanjay (Link Technologies) on 21 Mar 2025 04:52PM
Priority: Low
Product: Payroll & HR
Group: Enhancement
Time Taken: 10.00 (Weight: 40.00)
Assigned To: Development
Circulation: Development, Sanjay, Sitla
Resolve By: Friday, 28 March 2025 07:47 AM [12 days since logged date]
Status: Closed
Subject: Leave Code should not be allowed to change after there are transactions
Summary:    

Leave Code should not be allowed to change after there are transactions.

example. If ASL is initially a "ONE TIME" leave, then gets changed to "Accrual - Calendar", the leave transactions will be incorrect for employees that already have ASL allocated before the change.

We should not allow the following fields to change:

  1. Category
  2. Privilege
  3. Minimum Service Years
  4. Entitle after years
  5. Years Valid
  6. One Time Accrual
  7. Accrual Type
  8. Max Accrue
  9. Rollover
  10. Rollover Method

Review "Years Valid"

Audit Notes:Edited by sanjay on 25/03/25 14:16. Edited by sanjay on 21/03/25 16:52. 
22 Mar 202508:46AM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 28-03-2025 07:47 AM Time Taken: 8.00 Notes: ETC extended from: 21/03/2025 to 28/03/2025
PART A - Development work for this case has been completed.

1. The change will be available in version: 15.70 and Patch 15.60.250322

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

  1. Added validation so you cannot update a leave code that has been used.
  2. Leave code is defined as "Used" if it has transactions that are not VOID
  3. The following fields cannot be edited if a leave is used:

1.  Category

2.  Privilege

3.  Minimum Service Years

4.  Entitle after years

5.  Years Valid

6.  One Time Accrual

7.  Accrual Type

8.  Max Accrue

9.  Rollover

10. Rollover Method


3. Affected Areas:

  1. Edit Leave Codes in menu "Leave Management ~> Leave Code"

4. The issue was caused by:

  1. Leave liability report does not match Transactions when transaction parameters are changed

5. Other Relevant Notes
6. Next Step
(Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT


PART B -
Development Reference (Place descriptor for objects changed)
:


25 Mar 202502:15PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 04-04-2025 02:14 PM Time Taken: 2.00
UAT completed on EBS DEMO Environment by Sitla and Sanjay

If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L13127 in the subject line of all emails regarding this issue.

Document size: 5.3 KB
For call complaints, please contact the Managing Director of the company using this form