Company: Link Technologies
Case No: L08480. Project: 08.20: LinkSOFT Version 8.2
Logged By: Alvis (Link Technologies) on 21 Apr 2017 10:20AM
Priority: High
Product: Point of Sale
Group: Enhancement
Time Taken: 5.00 (Weight: 5.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna
Resolve By: Friday, 21 April 2017 10:19 AM [2557 days since logged date]
Status: Closed
Subject: Improvement to Sales order processing
Summary:    

We have identified the issue with returns rounding and made the application correction in 8.11 refer to case 8396.

Data correction

  1. We have created a utility that will resolve rounding issues where the rounding factor is 0.05. The procedure name is LT_POS_Utility_CorrectSalesOrderRounding. Consultants are NOT to use this procedure without consulting the development team.
  2. Data issues caused by demo environment has been corrected individually. There were 250 lines with this issue.

The following additional corrections need to be implemented in 8.12:

  1. Add a unique index on reference number in sales order
  2. Add system health check where POSCASH balance is not equal to zero.
Audit Notes:
21 Apr 201710:19AM Comment 1 by Alvis (Link Technologies) Created from case 8479
21 Apr 201710:19AM Comment 2 by Alvis (Link Technologies) Case 8480 added to project 8.12
24 Apr 201701:55PM Comment 3 by Alvis (Link Technologies) Case 8480 removed from project 8.12
24 Apr 201701:55PM Comment 4 by Alvis (Link Technologies) Case 8480 added to project 8.13
14 Jun 201704:23PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-06-2017 04:23 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. Created unique index on reference number field in LBS_POS_Order table
  2. Changed column from Nullable to NOT nullable.
  3. Created a system health check entry when POSCASH customer has balance.

Documentation details:
  

03 Jul 201710:00AM Comment 6 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 03-07-2017 10:00 AM Time Taken: 1.00
System test complete, please proceed with UAT.

05 Jul 201711:21AM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 05-07-2017 11:21 AM Time Taken: 2.00
1. Was this test completed using Demo / New / Other database? Demo with 813 Beta 1 in Qa1
2. Did the test pass or fail? Pass
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?
Additional Details (Risks, issues, special conditions required for this test to pass etc):

The following tests were done

Test Case 1 

  1. Processed Sales, verified "Reference Number" in LBS_POS_Order, the reference numbers were unique.
  2. Tried to save a used reference number under global. System did not allow save.

Test Case 2

  1. Set the next receipt number as blank. (Logged case to disallow save of blank reference numbers)
  2. Sale was not successful in POS.

Test Case 3

  1. Enabled the POS health check 
  2. Alert was sent with outstanding balance for POSCASH customer.


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

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