| Subject: | Incorrect change amount on sale completion |
| Summary: | Issue: An issue has been reported by our client XXXXX supermarket where system gives an incorrect change amount or does not create payment lines for some of the transactions. Few examples below:
- Receipt number LTK10000573006, Transaction amount was $46.00, Payment received was $100. No Payment line was created for this transaction.
- Receipt number LTK10000571113, Transaction amount was $21.43 Payment received was $50. No Payment line was created for this transaction.
- Receipt number LTK10000570918, Transaction amount was $253.95 Payment received was $300. Payment line created with AmountNAT as -$46.05. Customer Paid amount was $300 and Customer Change given was $346.
I have reviewed the Event log for the transaction id's of the above sales and it does not have any errors. It shows that these transactions were successfully processed within 3 to 5 seconds. We have not had this issue reported in prior version and it may have to do with the changes made as per case 9058. Can we please schedule time to review what may have caused this problem. Below are the environment details:
- Server: LINKQA4
- DB:CLIENT-XXXXX-LINKSOFTPOS
- Database Version: 9.3.3.004
Regards
Vineet Ram
|
| Audit Notes: | |
| 18 May 2018 | 06:50AM Comment 1 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 23-05-2018 12:00 AM Time Taken: 2.00 |
| Hi Team, I worked to replicate the case internally. However, I was unable to replicate the mentioned issue. Test Environment - Version 933. Patch 4 - DEMO setup.
- Database on 192.168.0.12
- The sales were made from two client machine.
- Client 1
- OS - Windows 7
- Processor - i5
- RAM - 4GB
- Client 2
- OS - Windows 10 Pro
- Processor - 2.50GHz
- RAM - 4GB
Thanks Rashna |
|
| 18 May 2018 | 10:37AM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Development Followup Date: 21-05-2018 12:00 AM Time Taken: 1.00 |
| We have discussed the case in the development meeting with Sanjay, Alvis, Sanjeet and Rashna. It seems like the issue is caused due to transaction rollback. Case assigned to the development team for further investigation and resolution. Thanks Rashna |
|
| 23 May 2018 | 03:58PM Comment 3 by Alvis (Link Technologies) Case 9291 added to project 09.4 |
| 23 May 2018 | 05:16PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 23-05-2018 05:16 PM Time Taken: 12.00 |
| Hi Sanjeet, we have tried to trace the cause of this issue and cannot find anything that will result in incorrect "change" values no the order header. We will continue to investigate further tomorrow, however, it would be helpful if you can set-up an environment on your end and see if you can reproduce the issue by trying what the client says they are doing when this issue comes up. I would also suggest you station someone on site to monitor and record what is happening when errors are raised in the client's environment. |
|
| 24 May 2018 | 10:09AM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 24-05-2018 10:09 AM Time Taken: 6.00 |
| We are unable to reproduce the issue reported. The database procedures and business rules have been checked and rechecked. The main issue seems to be relating to the Payment Record that is not created despite the order and "order detail" lines are created. This can only happen under two circumstances: - Failure of SQL Server Transaction Management system
- Manual Update of Order table values
To address Item 2, we have added standard audits on all transactional tables to identify deleted transactions. We can also record UPDATES but this would consume lots of space. This can be enabled for a specific period of time by the consulting team to capture the update process. We have also created a utility procedure (LT_POS_Utility_VerifyOrder) to view transaction and log details for a specific Reference Number. Next step: - Upgrade client to 9.4
- Review the audit log
- Provide development with a backup if the issue cannot be explained
|
|
| 24 May 2018 | 10:42AM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 24-05-2018 10:42 AM |
| We have also added an Integrity check to the POS order system as follows: - Cash sale cannot have an outstanding balance
|
|
| 24 May 2018 | 03:44PM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjeet (Link Business Solutions) Followup Date: 24-05-2018 03:44 PM Time Taken: 1.00 |
| System test completed. We have verified the POS order process and added an integrity check. Please apply this update to the customer site and log a new case for any issue. regards
Alvis |
|
| 08 Jun 2018 | 12:48PM Comment 8 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 08-06-2018 12:48 PM |
| Please proceed with UAT |
|
| 11 Jun 2018 | 03:01PM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 12-06-2018 12:00 AM Time Taken: 1.00 |
| Hi Sanjay,
This case has been successfully tested. Documentation is not required for the case. Test Environment - Version 9400 Beta 5
- Database - LINKSOFTQA on LINK008
- OS - Windows
Test Plan Since we were unable to replicate I have processed the following - Cash Sale
- Credit Sale
- Layby
- Quotation
- Returns.
We did a select using the following query. There were no records found "select * from LBS_POS_Order where CustomerID like '%pos%' and Balance <> 0 and Status in ('PRSD','CLOD')" |
|
| 11 Jun 2018 | 03:49PM Comment 10 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-06-2018 03:49 PM |
| Thanks Rashna |
|
| 09 Oct 2019 | 08:14AM Comment 11 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 |