Company: Link Technologies
Case No: L09334. Project: 10.10: LinkSOFT Version 10.1
Logged By: Vineshwar Prasad (Edge Business Solutions) on 11 Jun 2018 11:03AM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 24.00 (Weight: 24.00)
Version: 10.155.0117
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna, Sanjay, Vineshwar Prasad
Resolve By: Tuesday, 12 June 2018 12:00 AM [2145 days since logged date]
Status: Closed
Subject: Partial Close of a shift prints incomplete data in the "Shift Close Report".
Summary:    
Hi Alvis, 

Issue: Partial Close of a shift prints incomplete data in the "Shift Close Report".

Steps to Replicate

  1. Open a shift and process below transactions.
    1. Sale of $30.00 with payment as Cash.
    2. Sale of $30.00 with payment as Cheque. Surcharge $2.00
    3. Sale of $40.00 with payment as Eftpos.
  2. Partial Close the shift. Refer to Figure 1 for shift close amounts. 
  3. Print the shift close report at closure. The report is not correct. Refer to Figure 2.
    1. System value not updated upon Partial Close
    2. Till value not updated upon Partial Close
    3. Till Amount is updated however reconciliation of funds require a breakdown of different methods of Payments received
Figure 1: Partial Shift Close


Figure 2: Shift Close Report


Test Environment

  • Version 949 GA
  • LINKSOFTDEMO-UAT on QA1
  • Shift - SH000006
Thanks
Vineshwar and Rashna




Audit Notes:Edited by sanjay on 05/03/19 09:44. 
20 Jul 201809:09AM Comment 1 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 23-07-2018 12:00 AM Time Taken: 1.00

Hi Alvis, 

The case header has been updated with the details. Please address the case.

Thanks
Rashna


27 Jul 201810:05AM Comment 2 by Alvis (Link Technologies) Case 9334 added to project 09.5
15 Aug 201802:00PM Comment 3 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 15-08-2018 02:00 PM Time Taken: 1.00

Hi Sanjay,

I have gone through the POS design and found that shift partial close has the following flaws:

  1. Each partial close does not have a unique number to identify which partial close this is. for example, if a shift can have multiple partial closes. Data for each partial close is not stored separately.
  2. Reprint of partial close is not possible to get the correct information due to 1. above.
  3. Date and time partial close was done are not captured.
  4. When a full closure is done, all partial close previously done is overridden.
  5. We do not have a clear definition of what is the core purpose of a partial close.

Can we remove the partial close feature from the POS until we resolve these issues?

regards
Alvis


20 Aug 201802:53PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 20-08-2018 02:53 PM

Vineet to discuss with Tappoos Airport and Pharmacies to get an explanation on why we need Partial Close Shifts. 

We can also look at changing "Partial Close" to do the following:

  1. Perform a full close
  2. Create a new shift with the extension {Partial closed shift no.}"-1"

21 Aug 201806:40PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 21-08-2018 06:40 PM
Proceed with development based on comment 4

23 Aug 201802:42PM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 23-08-2018 02:42 PM Time Taken: 2.00
Development work for this case has been completed.
The change will be available in version: 9.5 beta3

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

  1. Added fields in ShiftDetails table to handle multiple partial closes. Added CloseNumber, CloseDate and CloseAuthroisedBy. CloseNumber increments by 1 for each partial close.
  2. Changed shift report to show all partial close entries.
  3. Changed shift reprint and search screen to search the close date and open date.
  4. Full close is allowed when all payment types are chosen to be reconciled.

2. The issue was caused by:

  1. Partial close did not store sufficient data

    3. Next Step

    1. UAT

    07 Sep 201803:58PM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 07-09-2018 03:58 PM Time Taken: 1.00
    System test completed. proceed with UAT. 

    25 Sep 201808:56AM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 25-09-2018 08:56 AM Time Taken: 2.00

    Updated documentation.

    An issue was identified where cash amounts were showing incorrect amounts after a partial close was done.

    This issue was caused by refunds and other payment methods that involved in giving change and these were not reconciled with the cash payment.

    In verison 10 beta 5, this issue has been resolved by adding a flag to payment lines table to mark change given as reconciled.

    For Example:

    Payment TypeAmount ReceivedCashoutTotal Cash
    Cash100 100
    EftPOS2005050
    Partial close payment type cash is $50   
    Cash200 200
    EFTPOS15010190
    Partial close payment type cash is $190   
        
    Add a flag on payment line so we can mark eftpos cashout and any other cash movement in a partial close
    Refunds are not required to be marked as there is 1 line per refund in the payment table
    Refunds are treated as change, and change is always in the form of cash.


    27 Sep 201801:46PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 27-09-2018 01:46 PM Time Taken: 1.00

    System test completed. Performed the following:

    Payment MethodDescriptionAmountAmount ReceivedChangeTotal Till Cash
    CashFloat2002000200
    CashSale5010050250
    EFTPOSSale105040210
    Partial close CASH     
    CashSale2002000200
    CashPayment1001000300
    EFTPOSpayment1001000300
    CashRefund50050250
    partial close cash     
    Cashsale1010010
    EFTPOSsale101555
    Partial close EFTPOS
         
    CASHsale4040045
    EFTPOSsale10201035
    Full Close     

    Shift Close Report:


    28 Sep 201812:52PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 28-09-2018 12:52 PM Time Taken: 1.00

    Hi Sanjay, 

    I have tested the case. 

    Issues Identified 

    1. The "Till Amount" is not correct on the "Partial" shift close report. Refer to Figure 1.
      1. Till Amount = Cash - Returns + Payments - Refunds
      2. Till Amount = 717.18 -100 +61 - 30 = $648.18. But the report shows $250.00.
      3. Steps to Replicate
        1. Process sales as per the table 1 below.
        2. Process partial close.
    2. The Natural amount accumulates to a negative figure after the first partial close. Refer to Figure 2.
      1. Process a sale of $10.
      2. Open the shift close screen

    Table 1: Transactions.

    Figure 1: Incorrect Till Total


    Figure 2: Shift Close

    Environment

    1. Version - 10 BETA 5
    2. Database - LINKSOFT-DEMO-10-RASHNA
    3. Server - 10.0.0.10
    4. Shift - SH000005

    28 Sep 201801:56PM Comment 11 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 28-09-2018 01:56 PM Time Taken: 3.00

    Hi Alvis, 

    Sanjay and I diagnosed the case. Test Plan on google drive.

    Please address the case.

    Thanks


    02 Oct 201804:45PM Comment 12 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 02-10-2018 04:45 PM Time Taken: 8.00
    Development work for this case has been completed.
    The change will be available in version: 10.6

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

    1. Removed Till Transaction Summary from Shift Close Report
    2. Added Reconciled/Closed Shift Summary
    3. Added Unreconciled Shift Summary
    4. Tidied shift close report to have consistent fonts and lines
    5. Renamed Funds Received Summary to Shift Summary
    6. Corrected shift summary section amounts to correctly display values for partial and open shifts.

    2. The issue was caused by:

    1. Incorrect amounts are shown due to partial close changes

      3. Next Step

      1. UAT

      03 Oct 201809:24AM Comment 13 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 03-10-2018 09:24 AM Time Taken: 1.00
      System test completed. proceed with UAT

      04 Oct 201808:00AM Comment 14 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 04-10-2018 08:00 AM Time Taken: 3.00
      Hi Sanjay
      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
      1Test the shift close as per the test plan in the comment 11Pass
      2Validate that the Till Amount is correctly calculated at shift partial and full closePass
      3Validate that shift amount does not calculate a negative amountPass

      Environment Details

      1. OS version: Windows Server 2012
      2. Application version: 10 Beta 6
      3. Setup: Demo
      4. Server : 10.0.0.10
      5. Database: LINKSOFT-DEMO-10-RASHNA

      Steps to reproduce failed scenarios: N/A

      Next Step: for closure


        04 Oct 201804:03PM Comment 15 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 04-10-2018 04:03 PM
        Thanks Rashna 

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

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