Company: Link Technologies
Case No: L08624. Project: 08.20: LinkSOFT Version 8.2
Logged By: Vineet (Link Business Solutions) on 20 Jun 2017 11:14AM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 13.00 (Weight: 13.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Development, Rashna, Vineet
Resolve By: Tuesday, 06 June 2017 12:00 AM [2496 days since logged date]
Status: Closed
Subject: Customer credit limit is not rolled over
Summary:    
1. Issue Description (Current behaviour and expected behaviour): 

Customer emailed and advised that the customer balances are not rolling over. The rollover is set to occur every month.

2. Environment Details: (Application version and Patch and any other information that will help identify the issue)

Version 811




3. Next Step
- Customer support will assist with resolving the issue and will contact you within the next working day.
- If the issue requires immediate attention, please call our office on: 3382136. 


4. TO BE COMPLETED CLOSING THE CASE
Has the problem been solved?:
Has the final solution review been done with the customer? (Yes/No)  
Notes from discussion with customer
:
Audit Notes:
20 Jun 201711:17AM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 20-06-2017 11:17 AM Time Taken: 1.00

Add to project 8.13 to investigate credit limit rollover and how it works overnight.

  1. Happens to some customers only
  2. Running "recompute customer balance" resolves the issue.



20 Jun 201711:17AM Comment 2 by Alvis (Link Technologies) Case 8624 added to project 8.13
21 Jun 201701:43PM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 21-06-2017 01:43 PM Time Taken: 2.00
Development work for this case has been completed.
The change will be available in version: 8.13
Documentation update required(Yes/No. Add change details below)
QA required(Yes/No.Include areas that require testing): Yes

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

  1. Credit limit rollover currently occurs in the "customer recompute balance" process. This process runs when replication queue is settled. 
  2. I have created a new process "POS Customer Rollover Credit Limit Process" that updates the customer credit limit rollover. This is scheduled to run at midnight every day.

Documentation details:
  

03 Jul 201711:53AM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 03-07-2017 11:53 AM Time Taken: 1.00
System test completed, please proceed with UAT. 

04 Jul 201711:18AM Comment 5 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 04-07-2017 11:18 AM Time Taken: 2.00

Comment 3 explained further:

Development work for this case has been completed.
The change will be available in version: 8.13
Documentation update required(Yes/No. Add change details below): YES
QA required(Yes/No.Include areas that require testing)Yes

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

  1. Credit limit rollover currently occurs in the "customer recompute balance" process. This process runs when replication queue is settled. 
  2. I have created a new process "POS Customer Rollover Credit Limit Process" that updates the customer credit limit rollover at midnight every day.
Important notes:
  1. In a standalone setup, there is a potential for the rollover to fail. This can happen if the process is disabled.
  2. In a replicated environment, if a branch is not connected during the recompute process, the rollover available balance will be incorrect.


Test case 1: (Simple setup to understand process)

  1. Set-up a standalone environment using DEMO
  2. Configure fleet setup and set rollover type to daily. Customer has zero Credit limit with rollover type to NONE

Test case 2 - OTGL Equivalent 

  1. Setup fleet card with daily rollover amount of 100
  2. Disable branch 2 replication
  3. Sell $100 from Branch 1. 
  4. Sell from Branch 2 on the same day - Fail (Desired result ?)
  5. Sell from branch 2 on the next day - Fail
Client Response
  1. What caused the issue - In previous versions, the "Process to compute balance" was running every day. This process rolled over the fleet customer balance. This process has been changed to run when the queue is settled.
  2. Can this issue happen again - Yes - if the process stops or if the branch is not connected to the server
  3. How/When will the correction be delivered 
    1. Patch 8.13 needs to be applied to all client installations and the Database update applied once to each database.
    2. Enable the process name "POS Customer Rollover Credit Limit Process" on Head Office
  4. Discuss TEST CASE 2 with the customer

05 Jul 201701:45PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 05-07-2017 01:45 PM Time Taken: 2.00
1. Was this test completed using Demo / New / Other database? Demo with 813 Beta 1
2. Did the test pass or fail? Failed 
3. Tab order, spelling, alignment, font size consistency, screen size etc checked? N/A
4. Data verified, saved, edit, delete/void? N/A 
5. Documentation update required? No
Additional Details (Risks, issues, special conditions required for this test to pass etc):

Test Case 1 (Standalone Setup) - Passed

  1. Created Customer with Customer Limit as 1000 and Fleet Limit as 500.
  2. Rollover was set as daily
  3. Processed Fleet sale of 250 on the 04/07/2017.
  4. Processed Credit sale of 150 on the 04/07/2017.
  5. Executed the ""POS Customer Rollover Credit Limit Process" on the database on 05/07/2017.
  6. Rollover was successful.

Test Case 2 (Replication Setup) - Failed

  1. Created Customer with Customer Limit as 1000 and Fleet Limit as 500.
  2. Rollover was set as daily
  3. Processed Fleet sale of 250 on the 04/07/2017.
  4. Processed Credit sale of 150 on the 04/07/2017.
  5. Executed the ""POS Customer Rollover Credit Limit Process" at HQ on 05/07/2017.
  6. Balance was only updated at HQ.
  7. Rollover did not occur at the branch.

05 Jul 201701:47PM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 05-07-2017 01:47 PM Time Taken: 1.00

Hi Rashna,

I have added "Execute as Login = LINKADMIN" to the rollover procedure. This will now push data into the replication queue.

regards
Alvis


06 Jul 201701:14PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 06-07-2017 01:14 PM Time Taken: 2.00
1. Was this test completed using Demo / New / Other database? Demo with 813 Beta 2
2. Did the test pass or fail? Passed
3. Tab order, spelling, alignment, font size consistency, screen size etc checked? N/A
4. Data verified, saved, edit, delete/void? N/A
5. Documentation update required? Yes
Additional Details (Risks, issues, special conditions required for this test to pass etc): 

Test Case 2 (Replication Setup) - Passed

  1. Created Customer with Customer Limit as 1000 and Fleet Limit as 500.
  2. Rollover was set as daily
  3. Processed Fleet sale of 250 on the 04/07/2017.
  4. Processed Credit sale of 150 on the 04/07/2017.
  5. Executed the ""POS Customer Rollover Credit Limit Process" at HQ on 05/07/2017.
  6. Balance was only updated at HQ.
  7. Rollover over was updated at branch

07 Jul 201709:04AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 07-07-2017 09:04 AM Time Taken: 2.00
Documentation completed on the case.

Documentation updated at POSWeb - Administration -- Processes 

If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L08624 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