Company: Link Technologies
Case No: L09223. Project: 09.40: LinkSOFT Version 9.4
Logged By: Rashna (Edge Business Solutions) on 20 Mar 2018 02:45PM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 9.00 (Weight: 9.00)
Version: 9.496.1128
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna, Sanjay
Resolve By: Wednesday, 21 March 2018 12:00 AM [2228 days since logged date]
Status: Closed
Subject: Purchase Order HOME AMOUNT is incorrect when some PO Lines are updated in certain scenarios
Summary:    

Hi Sanjay,

Client has reported cases where the "Home Amount" on the Purchase Order is incorrect.

We were unable to replicate the case neither on the Demo or Client database.

We had set an audit in the client database on site. 

A backup with the issue and audit results has been restored on QA4 as "CLIENT-XXXXX-LINKSOFT818".

Client has replication set on site.

Example

  • PO Number = 0005326
  • Refer to line item 2, Product Code - I0006947
  • Unit Price = $33.688
  • Order Quantity = 60.
  • Ext Price = $1010.64 (60*33.688)
  • Tax Amount = $90.96 (1010.64*1.09)
  • Home Amount = $36.718., this is incorrect. Home Amount should be $1101.54 (Ext Price + Tax Amount)

The above is  being reported once very week for 1 or 2 Purchase Orders created in a day.

Audit Notes:
20 Mar 201802:50PM Comment 1 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 21-03-2018 12:00 AM Time Taken: 1.00

Hi Alvis,

Can you please, reveiw this case.

Thanks

Rashna


21 Mar 201803:01PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 21-03-2018 03:01 PM Time Taken: 1.00

Hi Rashna,

I have investigated the issue and it seems back-office application has changed the value after the record was initially saved.

This is an issue that has always existed in the product.

To resolve this, we will need to move back-office code from the application to SQL procedure as the PowerBuilder code as a lot of redundant and complex structures.

regards
Alvis



21 Mar 201803:02PM Comment 3 by Alvis (Link Technologies) Case 9223 added to project 9.4
26 Mar 201808:10AM Comment 4 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 26-03-2018 08:10 AM

Please proceed to changeover to use Stored procedures for Purchase Orders.


27 Mar 201810:44AM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 27-03-2018 10:44 AM Time Taken: 4.00
Development work for this case has been completed.
The change will be available in version: 9.4

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

  1. Created SQL procedures "LT_PUR_PurchaseOrderHeader_UPDATE" and "LT_PUR_PurchaseOrderLine_UPDATE"
  2. Changed back-office Purchase Order Entry screen to use procedures created in 1.above
  3. Tested purchase order entry and confirmed SQL procedures are now used to save data.



30 Apr 201802:37PM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 30-04-2018 02:37 PM Time Taken: 1.00

System test completed. 

Since this case cannot be reproduced, I have used SQL Trace to scan any manual updates done outside of the SQL Stored procedures.

There were some traces found that purchase order header values and detail line values were updated from the back-office application outside of the SQL stored procedure. 

These have been identified and cleaned.

Re-test system UAT on beta2


09 May 201809:29AM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 09-05-2018 09:29 AM Time Taken: 1.00

System test completed.

Verified the following:

  1. Created a purchase order.
  2. Verified SQL trace for any updates done to LBS_PO_HD and LBS_PO_DET tables. Could not find any updates done outside of the SQL procedures.

regards
Alvis


15 May 201803:00PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 16-05-2018 12:00 AM Time Taken: 1.00

Hi Sanay

This case has been successfully tested.

Documentation on the case is not required.

Test Environment

  • Version 9400 Beta 2
  • Database - LINKSOFT on QA1
  • Application on QA1
  • OS - Windows 7

Test Plan Since, the issue could not be replicated.  I tested general PO creation

Test NoDescriptionStatus
1Create a PO for local Supplier. Item PNT01, the cost is $3.00. Quantity is 3. Ext Price should be $9.00 and Home Amount should be $9.81 Pass
2Create a PO for International Supplier. Item PNT01, the cost is $3.00. Quantity is 3. Ext Price should be $9.00 and Home Amount should be $18.00 
Pass

Purchase Orders will be further tested in General QA.

Thanks

Rashna


16 May 201803:45PM Comment 9 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 16-05-2018 03:45 PM
Thanks Rashna 

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

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