Company: Link Technologies
Case No: L12681. Project: 13.40: LinkSOFT Version 13.40
Logged By: Vineshwar Prasad (Edge Business Solutions) on behalf of Sanjay (Link Technologies) on 10 Mar 2022 01:26PM
Priority: Medium
Product: Payroll & HR
Group: Change Request
Time Taken: 29.00 (Weight: 29.00)
Version: 13.40
Assigned To: Development
Circulation: Development, Sanjay, Sitla Sharma, Vineshwar Prasad
Resolve By: Friday, 01 April 2022 11:59 PM [770 days since logged date]
Status: Closed
Subject: Leave values are pushed into Integration when Rollover happens
Summary:    
Section A - Describe what the issue is about. Include Error Message (Include screenshots)

When the Leave Rollover over happens, new dates and values are allocated. The values in the Accrued column get pushed into Integration. This happens for Bereavement, Sick Leave & Others which is Incorrect.

The following was done in the Client Database;
  1. Upgraded Database to v.13.30.0224.GA
  2. Employees 326 & 327 have Anniversary on 24th February
  3. Pay Processed on 25/02/22 - Pay No 1581
  4. The following Leaves are flowing into Integration;
    • BL24
    • FCL24
    • SL 24
Image 1: Showing Leaves included in Integration Journal for Employee 326


Table 1: 
Environment Details where this issue can be seen

Server Name :

LINKQA4

Database Name :

CLIENT-FICAC-LINKSOFT

Application Hosted on :

http://LINKQA2/LinkSOFT

LinkSOFT Version :

13.30.0224.GA

 

Section B. Relevant History Information: Any information that is relevant to this issue, or may have caused this issue.

This is unique to FICAC's Database.

Case L12651, Case Haeder has test results that confirm this does not happen in Demo Database.

Section C. The issue can be reproduced by performing the following steps:
  1. Verify any Employees Anniversary Date falls between the Last Pay & Current Pay
  2. Create & Close the Pay
  3. Verify the Integration Journals
  4. Following leaves will be shown in the Integration File
    • Sick Leave
    • Bereavement Leave
    • Family Care Leave
Audit Notes:Edited by sanjay on 06/04/22 09:13. Edited by sanjay on 04/04/22 15:45. Edited by sanjay on 04/04/22 10:52. Edited by sanjay on 04/04/22 10:52. Edited by sanjay on 04/04/22 10:52. 
11 Mar 202208:30AM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 15-03-2022 10:30 AM
Thanks Vineshwar, I am investigating this and will get back to you by COB today.

11 Mar 202210:08AM Comment 2 by Sanjay (Link Technologies) Assigned To: Vineshwar Prasad (Edge Business Solutions) Followup Date: 15-03-2022 10:30 AM Time Taken: 4.00
Hi Vineshwar, the journal is part of the pay close process, not rollover. So I can investigate further, Can you set the two employees in your example in the DEMO database using the same codes and dates (https://linktechnologies.com.au/DEMO-LinkSOFT-EDGE/), set up the three leave allocations and do pay close, then a Year rollover? this will show the same journals as in Ficac database. I can then investigate what is different

11 Mar 202212:47PM Comment 3 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 15-03-2022 02:18 PM Time Taken: 2.00 Notes: Edited by vineshwar on 11/03/22 12:50. ETC extended from: 11/03/2022 to 15/03/2022
Hi Sanjay, I'm able to replicate the issue in the Demo Environment.

Table 1: Environment Details where this issue can be seen

Application Hosted on :

https://linktechnologies.com.au/DEMO-LinkSOFT-Edge

LinkSOFT Version :

13.30.0224.GA

Company :

1001 - Link Technologies - Demo

Pay Team :

FTN - Fortnightly

Payrun ID :
456

 

Section B. The issue can be reproduced by performing the following steps: 

Created Employees as below;

Emp ID

Emp Name

Start Date

Rate

326

Emp 1

24/02/2021

    18,000.00

327

Emp 2

24/02/2021

    18,000.00


Setup Leave Codes as below;

Leave Code

Description

Privilege

One Time Accrue

Rollover

Rollover Method

Allow Carry Over

AL24
Annual Leave
504.00
No
Yes
Anniversary
9999.00

SL 24

Sick Leave

288.00

Yes

Yes

Anniversary

-   

BL24

Bereavement Leave

72.00

Yes

Yes

Anniversary

-

ISL24

Inpatient Sick

1440.00

Yes

Yes

Anniversary

-
FCL24
Family Care
120.00
Yes
Yes
Anniversary
-

Scenario
  1. Created Pay for February 2021
    • ID: 456
    • Payrun Date: 25/02/2021
    • Employe: 326 & 327
Result from FMIS Integration Journal

Leave Status

Result

AL24 - Annual Leave values in FMIS Integration

Correct

SL 24 - Sick Leave values in FMIS Integration

Incorrect

BL24 - Bereavement Leave values in FMIS Integration

Incorrect

ISL24 - Inpatient Sick Leave values in FMIS

Incorrect

FCL24 - Family Care Leave values in FMIS

Incorrect


Regards
Vineshwar

11 Mar 202203:41PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 15-03-2022 03:53 PM Time Taken: 4.00
Skype Conversation
Hi Vineshwar, re: Case L12681. It says the issue is when you "Rollover", however, this is the case for All leave, except "Leave Without Pay" is accrued into FMIS.

Can you confirm your issue is not Rollover related?
At the moment, we hardcode "Leave Without Pay" as the only leave type that doesn't flow into FMIS. We should Either add a Flag "FMIS Integrate" or use the "GL Code Exists in component"

Vineshwar, 2:42 PM
When Pay is processed, only AAL flows into FMIS which is fine.
When Rollover happens and Pay is processed, All Leave flows in FMIS.

We need a flag to stop/allow which leaves to flow to FMIS.

2:48 PM
I checked as far back as V12 and we have always sent all leave except "Leave Without Pay" into FMIS. I can do a patch for Sick leave but will need Sitla to validate this
@Sitla, the following are leave categories in the current version. Can you confirm which ones should go to FMIS? I would Imagine All except Leave Without Pay and SIck Leave

Annual
Bereavement
Leave without Pay
Long Service
Maternity
Others
Sick Leave

Vineshwar, 3:00 PM
We have 4 scenarios here;
1. Which Leaves should go or not go on Leave Accrual
2. Which Leaves should go or not go on Leave Rollover
3. Which Leaves should go or not go on Leave Adjustment
4. Which Leaves should go or not go on Leave Allocation

3:10 PM
@Vineshwar, I have applied a change to your demo environment, can you confirm this is what you are after? we should have a conference call to discuss other impact

Vineshwar, 3:11 PM
ok

3:11 PM
I haven't removed Bereavement from the FMIS
let me remove Bereavement then you can check
@Vineshwar Removed Bereavement, check now


Sitla, 3:19 PM
Hi, only AAL is a liability for company so accural in FMIS should be captured.
All other leave types should only flow in FMIS when taken to the dedictaed GL account.

Linksoft should allocate and rollover on calender/ anniversary for all other leave types but not send to FMIS. Only when taken


3:26 PM
ok, so we need to document how the current system works and what needs to be changed so we can properly test this.

We cannot hard code as some countries may have Long Service, and other leave that may need accrual, so we have to use either a FMIS Flag, or the GL Account on the Leave Maintenance

11 Mar 202203:43PM Comment 5 by Sanjay (Link Technologies) Assigned To: Vineshwar Prasad (Edge Business Solutions) Followup Date: 15-03-2022 05:41 PM Time Taken: 2.00
Next steps: - Vineshwar to review and comment on change applied on https://linktechnologies.com.au/DEMO-LinkSOFT-Edge

14 Mar 202202:09PM Comment 6 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 15-03-2022 04:05 PM Time Taken: 1.00
Results are correct in the FMIS Integration Journal

14 Mar 202202:20PM Comment 7 by Sanjay (Link Technologies) Assigned To: Vineshwar Prasad (Edge Business Solutions) Followup Date: 15-03-2022 04:18 PM Time Taken: 1.00
Thanks Vineshwar, can you confirm Accrual, Rollover, Adjustment and Allocations is also ok so I can release a patch for 13.30 and add the new checkbox in 13.40?

30 Mar 202203:28PM Comment 8 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 01-04-2022 05:24 PM Time Taken: 8.00 Notes: Edited by vineshwar on 30/03/22 15:30. ETC extended from: 15/03/2022 to 01/04/2022
Test results as below;

TaskTestDetailsAnnualBereavementSickLWOPLong ServiceMaternityOtherTest ResultCommentsScenario
1AllocationFMIS Journal created when New Leave is Allocated - with No ValuesNoNoNoNoNoNoNoPass  
 AllocationFMIS Journal created when New Leave is Allocated - with Values in Brought Forward columnYesNoNoNoYesNoNoFailAnnual & Long Service didn't flow in FMISA scenario where employees leave was not allocated initially, and later done
 AllocationFMIS Journal created when New Leave is Allocated - with Values in Accrued columnYesNoNoNoYesNoNoFailAnnual & Long Service didn't flow in FMIS 
 AllocationFMIS Journal created when New Leave is Allocated - with Values in Taken columnYesNoNoNoYesNoNoFailAnnual & Long Service didn't flow in FMIS 
             
2AccrualFMIS Journal created on AccrualYesNoNoNoYesNoNoPass  
             
3AdjustmentFMIS Journal created for Adjustment done to Allocation columnNoNoNoNoNoNoNoFail Annual & Long Service flows in FMIS 
 AdjustmentFMIS Journal created for Adjustment done to Brought Forward columnYesNoNoNoYesNoNoPass  
 AdjustmentFMIS Journal created for Adjustment done to Accrued columnYesNoNoNoYesNoNoPass  
 AdjustmentFMIS Journal created for Adjustment done to Taken columnYesNoNoNoYesNoNoPass  
             
4TakenFMIS Journal created for Leave TransactionsYesYesYesNo
YesYesYesPassLWOP reduced the Gross Pay
 
             
5RolloverFMIS Journal created on RolloverNoNoNoNoNoNoNoPass  


31 Mar 202202:13PM Comment 9 by Sanjay (Link Technologies) Case L12681 added to project 13.40
04 Apr 202210:52AM Comment 10 by Sanjay (Link Technologies) Assigned To: Vineshwar Prasad (Edge Business Solutions) Followup Date: 05-04-2022 12:44 PM Time Taken: 2.00 Notes: Edited by sanjay on 04/04/22 10:55. Edited by sanjay on 04/04/22 10:54. 

Hi Vineshwar, The examples don't tell me what leave codes are used in your setup. The setup of the leave codes determines how they flow. 

I will have to remove comment 8 from V13.40 as I will be moving into release prep this Friday and we are moving very slow with this case.

Next step:

  1. Create a new case for these issues as we need to move this into release prep
  2. Define precisely what codes are used in the scenario so we can work out how they flow based on the settings for each code
  3. State the environment used

04 Apr 202210:52AM Comment 11 by Sanjay (Link Technologies) Case L12681 removed from project 13.40
04 Apr 202210:52AM Comment 12 by Sanjay (Link Technologies) Case L12681 added to project 13.40
04 Apr 202210:53AM Comment 13 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 05-04-2022 10:53 AM
Assigned for UAT

04 Apr 202203:45PM Comment 14 by Sanjay (Link Technologies) ETC was changed from 01/04/2022 to 01/04/2022
05 Apr 202201:35PM Comment 15 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 06-04-2022 01:28 PM Time Taken: 5.00

The following changes have been made as a temporary solution while the complete workflow is being analysed:

  1. In previous versions, we only prevented "Leave Without Pay" to go to FMIS. We have included Sick and Breavemnent leave as well
  2. Move the check of "Integration Leave Codes" to a function (IsGLIntegrationLeaveCode) so we can easily patch this in later versions

SYSTEM TEST COMPLETED WITH THESE THREE Leave Types.


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

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