Company: Link Technologies
Case No: L09067. Project: 09.40: LinkSOFT Version 9.4
Logged By: Rashna (Edge Business Solutions) on 22 Jan 2018 03:32PM
Priority: High
Product: Point of Sale
Group: New Feature
Time Taken: 11.00 (Weight: 11.00)
Version: 9.496.1128
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, AwaitingApproval, Development, Rashna, Sanjay, Sanjeet
Resolve By: Tuesday, 23 January 2018 12:00 AM [2286 days since logged date]
Status: Closed
Subject: VMS - Submit Buyer TIN with B2B transactions
Summary:    

FRCS has come back to us with the Preliminary Findings with VMS deployment by Link.

The below  has been highlighted

  1. Buyer’s TIN is not submitted to E-SDC for B2B invoices. These are any transactions made by a selecting a customer.
Changes Required
  1. Add a field on the customer screen to record customer TIN numbers. TIN number should be made mandatory.
  2. Output the buyer TIN on receipts with B2B invoices. This includes all transactions by a selecting a customer:-
  1. Cash Sales
  2. Credit Sales
  3. Layby
  4. Quotation
  5. Return.
Receipt component to be updated.


Test Plan 
Test NoDescriptionResults
1.There should be an option to enter the TIN number on the customer screen.
2.Create a customer as "John" save the TIN number as 12-18141-0-6.
3.Select Customer and process a cash sale, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. 
4.Select Customer and process a credit sale, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. 

5.Select Customer and process a return of the cash and credit sale above, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.

6.Select Customer and process a layby, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.

7Select Customer and process a quotation, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.


Audit Notes:
23 Jan 201808:05AM Comment 1 by Alvis (Link Technologies) Case 9067 added to project 8.3
23 Jan 201808:20AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 23-01-2018 08:20 AM
We have added a field for TFN on customer master file and added this to VMS.

06 Feb 201811:26AM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 06-02-2018 11:26 AM
Hi Rashna, this change is ready for UAT in LinkSOFT Versio 8.3.000 which is on our FTP site at this address: \\10.0.0.9\ftp\LinkSoftware\LinkSOFT\83  

08 Feb 201811:41AM Comment 4 by Sanjeet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 08-02-2018 11:41 AM Time Taken: 1.50
QA Results
Step 1 - Developer will perform test based on test cases provided
Step 2 - Product expert to complete Product QA based on test cases.

Test cases are provided on the case header before the case is approved for development.

Test Results Summary

Table 1 - Summarised list of issues

QA Environment Details

est NoDescriptionResults
1.There should be an option to enter the TIN number on the customer screen. TFN added on Customer FormPass
2.Create a customer as "John" save the TIN number as 12-18141-0-6.Pass
3.Select Customer and process a cash sale, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. Pass
4.Select Customer and process a credit sale, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. 
Pass
5.Select Customer and process a return of the cash and credit sale above, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.
Fail
6.Select Customer and process a layby, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.
Pass
7Select Customer and process a quotation, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. - Pass

  1. OS version:
  2. Application version:
  3. Database (Demo/New/Client):  Demo DB

Steps to reproduce failed scenarios:



    08 Feb 201812:48PM Comment 5 by Sanjeet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 08-02-2018 12:48 PM Time Taken: 0.50

    Steps to Produce Failed Scenario - Returns

    1. Perform VMS Cash Sale
    2. Perform Return of Cash Sale in 1 above
    Get a Error message

    "The remote server returned an error:(400) Bad Request"

    Have Uploaded DB on QA4 as "LINKSOFT-SANJEET-83B1"


    08 Feb 201802:54PM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-02-2018 02:54 PM Time Taken: 4.00
    The issue is caused by the Return Reference Number. I need Ivan to clarify how to handle transactions without this value, i.e. History transactions.

    I noticed that this cases all return transactions to fail.

    ----

    Hi Ivan,

    When we perform a return transaction, we place the "ReferentDocumentNumber" value as the original transaction reference.  This works well for transactions that were processed after SDC is implemented.

    What happens with clients that return transactions before SDC is implemented?.

    When I place an Empty, Null or any other value in this field, I get a BAD Request.  How do we perform a return for transactions that do not have a ReferentDocumentNumber value?

    Regards

    Sanjay Singh
    B Sc, PGDTE, MCSD, MIT
    Mobile:+ 61(0) XXX-XXX-XXX

    08 Feb 201802:59PM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-02-2018 02:59 PM Time Taken: 2.00
    Hi Ivan,

    This issue is also applicable to Reprints.  What value do we place if the original transaction did not have an SDC reference number?

    Regards

    Sanjay Singh
    B Sc, PGDTE, MCSD, MIT
    Mobile:+ 61(0) XXX-XXX-XXX

    09 Feb 201808:35AM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 09-02-2018 08:35 AM Time Taken: 2.00

    I have added the reference number for history transactions and tested this with Returns and Reprints.

    This update will be available in Beta 2.

    --- Email Ivan and Sanjay ---

    Thanks Ivan, 

    I have tested this and it all works well for history transactions.

    Regards

    Sanjay Singh
    B Sc, PGDTE, MCSD, MIT
    Mobile:+ 61(0) XXX-XXX-XXX

    On 8 February 2018 at 20:32, <ivan.pavlovic@dti.rs> wrote:

    Hi Sanjay,

     

    Put XXXXXXXX-XXXXXXXX-1 as refdocno

     

    Ivan



    13 Feb 201801:19PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 13-02-2018 01:19 PM
    Please proceed with UAT

    14 Feb 201811:49AM Comment 10 by Sanjeet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 14-02-2018 11:49 AM Time Taken: 1.00
    QA Results

    Test NoDescriptionResults
    1.There should be an option to enter the TIN number on the customer screen. TFN added on Customer FormPass
    2.Create a customer as "John" save the TIN number as 12-18141-0-6.Pass
    3.Select Customer and process a cash sale, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. Pass
    4.Select Customer and process a credit sale, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. 
    Pass
    5.Select Customer and process a return of the cash and credit sale above, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.
    Pass
    6.Select Customer and process a layby, 12-18141-0-6 should be printed under the Buyer TIN on the receipt.
    Pass
    7Select Customer and process a quotation, 12-18141-0-6 should be printed under the Buyer TIN on the receipt. - Pass


    QA Environment Details

    1. OS version:
    2. Application version:
    3. Database (Demo/New/Client): 

    Steps to reproduce failed scenarios:



      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 admin@linktechnologies.com.au and include the Case No: L09067 in the subject line of all emails regarding this issue.

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