Company: Link Technologies
Case No: L08889. Project: 08.20: LinkSOFT Version 8.2
Logged By: Fariha Kauser Tafsil (Link Fiji) on 01 Nov 2017 03:56PM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 18.50 (Weight: 18.50)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Fariha Kauser Tafsil, Rashna, Sanjay
Resolve By: Thursday, 02 November 2017 12:00 AM [2814 days since logged date]
Status: Closed
Subject: Difference in Total amount and Banking amount in Shift Close Report
Summary:    
1. Issue Description (Current behaviour and expected behaviour): 
Vatau via Viber asked for the explanation in the Difference in amounts between "Banking amount" and "Total amount".

2. Environment Details: (Application version and Patch and any other information that will help identify the issue)
Version 8120.00
Audit Notes:
01 Nov 201704:20PM Comment 1 by Fariha Kauser Tafsil (Link Fiji) Assigned To: Alvis (Link Technologies) Followup Date: 02-11-2017 12:00 AM Time Taken: 1.00 Reference: System Issue

Hi Alvis,

I have replicated this case in version 8180.00 in LINKSOFT Demo database.

Steps to replicate:

  1. Set float as 0
  2. Log in POS as POSADMIN
  3. Enter cash sales worth $447.50
  4. Enter credit sales worth $529.9.
  5. Receive account payment worth $270.00
  6. Process refund of $250.00
  7. Close shift
  8. Enter till amount as $469.50
  9. Close All

After the above was performed, the following Shift close report was generated, the Banking amount is incorrect as it includes the refund amount and Total banking should only be Cash sales + Payment received  - Refund:



Please if you could address this case.

Regards,
Fariha.


03 Nov 201709:19AM Comment 2 by Fariha Kauser Tafsil (Link Fiji) Assigned To: Sanjay (Link Technologies) Followup Date: 03-11-2017 09:19 AM Time Taken: 0.50
Hi Alvis,

Set up is in QA2, Database - LINKSOFT, Shift ID - LTSH0000000012

Regards,
Fariha

03 Nov 201709:48AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 03-11-2017 09:48 AM Time Taken: 2.00

Hi Fariha,

The issue has been resolved in 8.19.

regards
Alvis


03 Nov 201709:49AM Comment 4 by Alvis (Link Technologies) Case 8889 added to project 8.19
15 Nov 201703:59PM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 16-11-2017 12:00 AM Time Taken: 3.00
QA for product and Patch Releases
Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test
Step 2 - Product expert allocated by Consulting Manager for Product QA.
               Consulting Manager to allocate resource
               Consulting Manager to sign off on UAT and Generic Test

STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below.

Table 1 - Summarised list of issues
NoIssue Description Resolved? 
1
  •  Float = 0
  • Cash Sale $200
  • Credit Sale $50
  • Credit Sales of $20.00 and $5.00 Payment
  • Account Payment and Allocation of $10.00
  • Account Payment of $50.00
  • Payment refund of $15.00
  • Void Payment $50.00
  • Foreign Curry $5.88 AUD
  • EFTPOS $10.00
  • Cheque $27.00
  • Credit Card $12.06
  • Returns $10.00
  • LayBy $10.00 with $1.00 Deposit

Total cash should be $241.00

Total Amount should be $300.06

Banking Should be $277.99

Passed

2 
  •  Float = 200
  • Cash Sale $200
  • Credit Sale $50
  • Credit Sales of $20.00 and $5.00 Payment
  • Account Payment and Allocation of $10.00
  • Account Payment of $50.00
  • Payment refund of $15.00
  • Void Payment $50.00
  • Foreign Curry $5.88 AUD
  • EFTPOS $10.00
  • Cheque $27.00
  • Credit Card $12.06
  • Returns $10.00
  • LayBy $10.00 with $1.00 Deposit
 

Total cash should be $441.00. 

Total Amount should be $300.06

Banking Should be $277.99, however banking is $477.99. Failed. Refer to image below

Figure 1: Shift Close report


WORKFLOW:

  1. Original case assigned to Development
  2. When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
  3. If system test passes, assign case to Consulting Manager for UAT
  4. If UAT Passes, Assign case for Documentation or close case

    16 Nov 201711:04AM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 16-11-2017 11:04 AM Time Taken: 8.00

    The shift report has been amended as the report does not clearly show an analysis of the shift close process.

    We have made the following changes to improve the shift report. refer to figure 1 below:

    1. Added a "Till Transaction Summary" title
    2. Changed the till total to reflect the actual transaction flow
    3. Added a "Funds Received Summary" title
    4. Added "Float + Cash IN - Cash OUT" line for banking
    5. Change "Till Cash" to "Till Total"
    6. Changed "Nett Till Cash" to "Funds Received" as this amount includes all payment types.
    7. Changed the input parameters to standard reports format
    8. Moved the report from "POSReports" to "Reports" folder so this report can be printed from POS-WEB
    9. Moved the report rules from "global configuration" to "POS Report Rules" which can be found in "Report Maintenance -> Details" section of POS-WEB
    10. Combined "Shift Report" and "Shift Report Logo". Print logo can be controlled in Report Rules in 9.above
    11. Added data migration scripts for the report location path changes.

    Customized shift close reports will need to be amended.

    Figure 1: Shift Report



    18 Nov 201710:32AM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 18-11-2017 10:32 AM Time Taken: 1.00

    Hi Alvis, 

    We have tested the case in QA1 with database LINSOFT with Beta 2.

    We created a demo DB and also upgraded it to test the report.

    We generated the shift close report but system generated the old shift close report. refer to Figure 1.


    Figure 1: Shift Close Report




    20 Nov 201708:04AM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 20-11-2017 08:04 AM Time Taken: 1.00

    Hi Rashna,

    We have updated the title sections of the shift report.

    regards
    Alvis


    20 Nov 201701:46PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 20-11-2017 01:46 PM Time Taken: 1.00
    Tested in QA2, working as expected. proceed with UAT.

    20 Nov 201703:22PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 20-11-2017 03:22 PM Time Taken: 1.00
    QA for product and Patch Releases
    Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test
    Step 2 - Product expert allocated by Consulting Manager for Product QA.
                   Consulting Manager to allocate resource
                   Consulting Manager to sign off on UAT and Generic Test

    STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below.

    Tested case in QA1 with database LINKSOFT. Version 819 Beta 1. Passed. 

    Table 1 - Summarised list of issues Test Plan


    Figure 1: 


    WORKFLOW:

    1. Original case assigned to Development
    2. When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
    3. If system test passes, assign case to Consulting Manager for UAT
    4. If UAT Passes, Assign case for Documentation or close case

      09 Oct 201908: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
      If you have any queries regarding this support incident, please email Support@LinkTechnologies.com.au and include the Case No: L08889 in the subject line of all emails regarding this issue.

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