Company: Link Technologies
Case No: L10172. Project: 10.10: LinkSOFT Version 10.1
Logged By: Aarti Pooja Gayaneshwar (Link Business Solutions) on 15 Feb 2019 03:23PM
Priority: High
Product: Payroll & HR
Group: Software Defect
Time Taken: 6.00 (Weight: 6.00)
Version: 10.155.0117
Assigned To: Sanjay (Link Technologies)
Circulation: Aarti Pooja Gayaneshwar, Alvis, Rashna, Sanjay
Resolve By: Saturday, 16 February 2019 12:00 AM [1897 days since logged date]
Status: Closed
Subject: Projected Hours in Negative - Leave Liability Report
Summary:    

Bula Vinaka Team,

When the Leave Liability Report is generated as at 31/12/2018, the projected leaves for some staff goes in Negative. Refer below example for one employee:

Attachment Removed for security reasons

Please assist us to identify how does this occur.

Steps to generate the report:

  1. Go to Leave Liability
  2. Date To: 31/12/2018
  3. Company: 1001
  4. Leave From: AAL
  5. Leave To: AL20D
  6. Employee example: E0048

Database Details:

  1. Upgraded to V10.039
  2. Restored in QA4 as: CLIENT-FBC-LINKSOFT
Please advise.

Regards
Aarti Gayaneshwar

Audit Notes:Edited by sanjay on 05/03/19 08:47. Edited by rashna on 21/02/19 09:16. Edited by aarti on 15/02/19 15:23. Edited by aarti on 15/02/19 14:57. 
21 Feb 201909:16AM Comment 1 by Rashna (Edge Business Solutions) Case 10172 added to project 10.1
21 Feb 201909:28AM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 21-02-2019 09:28 AM Time Taken: 2.00

Development work for this case has been completed.

The change will be available in version: 10.141

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

  1. Corrected the projected leave balance function to portion the leave balance on the accrual amount from the next pay

2. The issue was caused by:

  1. When the next pay had leave taken transactions, the projected leave balance function was incorrectly calculated.

3. Next Step:

  1. UAT

4. Notes: Please test the following reports:

  1. Leave Liability
  2. Leave Liability Analysis - Detail
  3. Leave Liability Analysis - Summary
  4. Leave Liability Summary (Show data)

22 Feb 201909:10AM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 25-02-2019 12:00 AM Time Taken: 1.00 Notes: Edited by rashna on 22/02/19 09:12. 

Hi Alvis, 

After applying updates for 10.141, the system is calculating incorrect accruals.

The following was done in the Demo database

  1. Created a new employee (E069) with pay frequency as FTN. The start date was set to 01/01/2018.
  2. Allocated leave "AAL" with privilege as 160. Leave dates 01/01/2018 to 31/12/2018.
  3. Created and updated first pay for the employee on 13/01/2018.
  4. Verified the accrual figure. System calculated accrual as 5.70. However, the accrual should have been 6.15 (160/26).

Setup Details

  • Version - 10.141
  • Database - RASHNA-LINKSOFT-DEMO-10
  • Server - 10.0.0.14


25 Feb 201910:27AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 26-02-2019 12:00 AM Time Taken: 3.00
 QA Results
Tests carried out according to requirements specified on the case header

Test Results Summary

Table 1 - Summarised list of issues
NoTest DescriptionPass/Fail
1

Create a new employee with pay frequency as FTN and Annual leave allocation as 160.

  • Create the first pay for the employee. Pay date is 13/01/2018. Accrual should be 160/365 *13 = 5.70.
  • Create second pay on the 27/01/2018. Accrual should be 160/26 = 6.15
Pass
2Project leave till 31/12/2018. Projected hours should be 148.15Pass
3

Create a leave entry with date 10/02/2018. Process this in the pay with date 01/03/2018.

  • Project Leave till 28/02/2018 – Accrued should be 16.16  (5.70+ (6.15*3) -8) and projected should be 160/365 * 4 = 1.75
  • Project leave till 31/03/2018 – Accrued should be 28.45 (5.70+ (6.15*5) -8) and projected should be 6.15/14 * 30 = 13.17
Pass
4

Create the pay for December (01/12/201) and process leave for date 11/11/2018

  • Project Leave till 31/11/2018 – Accrued should be 133.08 (5.70 + (6.15*22)-8). Last pay date was 17/11/2018. Projected Leave should be 160/365*13 = 5.69
  • Project Leave till 31/12/2018 – Accrued should be 131.15 (5.70 + (6.15*23)-16). Last pay date was 01/12/2018. Projected Leave should be 160/365*30 = 13.15
Pass
5

Create the pay for December (01/12/2018) and process leave for date 11/11/2018

  • Project Leave till 31/11/2018 – Accrued should be 133.08 (5.70 + (6.15*22)-8). Last pay date was 17/11/2018. Projected Leave should be 160/365*13 = 5.69
  • Project Leave till 31/12/2018 – Accrued should be 131.15 (5.70 + (6.15*23)-16). Last pay date was 01/12/2018. Projected Leave should be 160/365*30 = 13.15
Pass
6

Perform “End of Year”.

Create the pay for January 2019 (12/01/2019) and process leave for date 27/12/2018

  • Project Leave till 31/01/2019– Accrued should be 141.70 (5.70 + (6.15*26)-24). Last pay date was 17/11/2018. Projected Leave should be 6.15/14 * 19 = 8.35
  • Project Leave till 31/12/2018 – Accrued should be 143.54 (5.70 + (6.15*25)-16). Last pay date was 29/12/2018. Projected Leave should be 6.15/14 *2 = 0.88
Pass

Environment Details

  1. OS version: Windows Server 2012
  2. Application version: 10.2 
  3. Setup: Demo
  4. Server : 10.0.0.14
  5. Database: RASHNA-LINKSOFT-DEMO-10
Documentation updated under Pages out of TOC - 315 Leave Accrual

Steps to reproduce failed scenarios: N/A

Next Step: for closure


    25 Feb 201903:26PM Comment 5 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-02-2019 03:26 PM
    Thanks Rashna

    09 Oct 201908:14AM Comment 6 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019
    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L10172 in the subject line of all emails regarding this issue.

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