Company: Link Technologies
Case No: L09703. Project: 11.40: LinkSOFT Version 11.4
Logged By: Rashna (Edge Business Solutions) on 15 Nov 2018 07:51AM
Priority: Medium
Product: Point of Sale
Group: Enhancement
Time Taken: 15.50 (Weight: 15.50)
Version: 11.3.0902
Assigned To: Sanjay (Link Technologies)
Circulation: Development, Rashna, Sanjay
Resolve By: Friday, 16 November 2018 12:00 AM [1960 days since logged date]
Status: Closed
Subject: Relook at transaction numbers when transactions rollback.
Summary:    

Hi Sanjay, 

A support case has been logged stating that when a transaction is not valid it rolls back. The transaction number of the rollback transaction is missing from the system.

Clients have reported that there are missing transaction numbers in the system and require justification why it is missing.

Steps to Replicate

  1. Set the default transaction as "Credit Sales".
  2. Configure the wholesale machine and next wholesale number (WS000004)
  3. Login into POS.
  4. Load an item.
  5. Click on Save. This will open the customer search screen.
  6. Search for customer POSCASH.
  7. Complete Sale.
  8. The system does not allow the credit sale for a POSCASH  customer. Ok to that
  9. Select the credit customer and process the sale. Verify the LBS_POS_Order, reference number is updated as WS000006. 
  10. WS000005 is missing from the database.

In addition, the transaction numbers are also missing when POS times out.

Version : 10.1.2.3

Next Step:

  1. Please review and explain the current design.
  2. Can the system generate the transaction number only if a transaction is valid?

Thanks
Rashna

Audit Notes:Edited by sanjay on 08/12/20 09:17. Edited by sanjay on 28/02/19 14:55. Edited by rashna on 15/11/18 07:51. 
19 Nov 201811:31AM Comment 1 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 19-11-2018 11:31 AM Time Taken: 2.50

Hi Rashna,

The log will have the details of why the transaction fails. In some cases, we cannot re-use the transaction number as this will cause confusion between successful and failed numbers.

Are you saying there is a situation where the transaction fails and the log does not have the failed details?

Regards
Sanjay


27 Nov 201808:43AM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Development Followup Date: 27-11-2018 08:43 AM Time Taken: 3.50

As per the meeting with Sanjay, Alvis and Rashna

All lost transactions are logged in the Event Log.

  • In the event of an audit, the auditor will provide a list of transaction numbers with anomalies. Authorized users can validate the "Event Log" to verify what happened to the transaction number.
  • All failed transaction is updated with "reason" why the transaction has failed or rolled back. This information is also updated in the POS Log in the install file.
  • Loss of transaction ID can be accepted, however, loss of reference number needs to be reviewed. The reference number should be sequential. The development team will review this in the next release.

Thanks
Rashna




27 Nov 201808:43AM Comment 3 by Rashna (Edge Business Solutions) Case 9703 added to project 10.2
13 Mar 201904:45PM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 13-03-2019 04:45 PM Time Taken: 5.50

Development work for this case has been completed.

The change will be available in version: 11.0.1303

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

  1. Moved the "Reference no" allocation to the "Order Insert" area where we wrap the process in a transaction. If there is a failure, we will retain the Reference number, however, we will still lose the "Transaction ID". The transaction ID is logged in the event log.

2. The issue was caused by:

  1. When we implemented SDC, we moved the Reference Number outside the transaction to performance reasons

3. Next Step:

  1. UAT

18 Mar 201910:51AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 19-03-2019 12:00 AM Time Taken: 2.50
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

Set the next wholesale number as WS000001.

  1. Process a credit sale for customer "0002". This should be successfully completed. Reference Number should WS000001. 
  2. Process a credit sale for customer "POSCASH". This transaction should fail. Event log should be updated with the failed transaction ID.
  3. Process the sale in 2 above for a customer. The sale should be successfully completed. Reference Number should WS000002. 
Pass

Figure 1: Sequential Reference Number

Figure 2: Event Log Update

Environment Details

  1. OS version: Windows Server 2012
  2. Application version: 11.0.0314
  3. Setup: Demo
  4. Server : 10.0.0.14
  5. Database: LINKSOFT_REPORTNOTES

Next Step: for closure


    28 Mar 201910:29AM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 28-03-2019 10:29 AM Time Taken: 1.50
    Thanks Rashna 

    09 Oct 201908:14AM Comment 7 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: L09703 in the subject line of all emails regarding this issue.

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