Company: Link Technologies
Case No: L09077. Project: 09.40: LinkSOFT Version 9.4
Logged By: Rashna (Edge Business Solutions) on 25 Jan 2018 11:54AM
Priority: Medium
Product: Point of Sale
Group: Software Defect
Time Taken: 12.00 (Weight: 12.00)
Version: 9.496.1128
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna, Sanjay, Sanjeet
Resolve By: Friday, 26 January 2018 12:00 AM [2273 days since logged date]
Status: Closed
Subject: Improvements to receiving FOC items with UOM conversion
Summary:    

When FOC quantity is entered in Decimal for receiving, the quantity is not correctly calculated. The decimal figure is not taken into account. Consider the below business scenario

Business Scenario
When customers buy 10 cartons of Milk (12 Packets in 1 carton), suppliers give 5 packets FOC. The system does not cater for this exact quantity to be received in the system.

Setup

  • Create item AAA01 with "UOM" as "Each"
  • Create a "UOM" as "PACKOF40"
  • Set the "UOM" conversion for "PACKOF40" to "Each" with a conversion factor of 40.

Scenario 1 (Correct functionality)

  • Create a PO for AAA01 with UOM as PACKOF40
  • On the receiving screen enter FOC as 3.
  • Receive the PO.
  • 519 is updated as 40 after receiving PO.
  • Inventory adjustment is created for 120 items (40*3).
  • The above is correct.

Scenario 2 (Functionality to be improved)

  • Create a PO for AAA01 with UOM as PACKOF40
  • On the receiving screen enter FOC as 2.5. The user has received 2 and a half cartoons free.
  • Receive the PO.
  • 519 is updated as 40 after receiving PO.
  • Inventory adjustment is created for 80 items (40*2).
  • 0.5 is not considered.

Improvement.

Option 1: If receiving for FOC items is made with decimals, use it to calculate FOC quantity
Option 2: If above is difficult to achieve, introduce a new field for UOM of FOC quantity

Audit Notes:
21 Mar 201809:40AM Comment 1 by Sanjay (Link Technologies) Case 9077 added to project 9.4
26 Mar 201808:28AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 26-03-2018 08:28 AM
Proceed with development in version 9.4

26 Mar 201809:29AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 26-03-2018 09:29 AM Time Taken: 1.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. Corrected the back-office purchase receive screen to save the full decimal amount for FOC items.
  2. Added Adjustment Date for FOC adjustment entry to be same as receive date.

2. The issue was caused by:

  1. The receiving screen in back-office was converting the decimal to the whole number. This caused incorrect FOC data to be saved when the purchase was received.

25 Apr 201806:28AM Comment 4 by Sanjeet (Link Business Solutions) Assigned To: Development Followup Date: 25-04-2018 06:28 AM Time Taken: 6.00

Wrong comment on wrong case


30 Apr 201802:23PM Comment 5 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 30-04-2018 02:23 PM Time Taken: 1.00

System test completed. The following were done:

  • Create item AAA01 with "UOM" as "Each"
  • Create a "UOM" as "PACKOF40"
  • Set the "UOM" conversion for "PACKOF40" to "Each" with a conversion factor of 40.
  • Create a PO for AAA01 with UOM as PACKOF40
  • On the receiving screen enter FOC as 2.5. The user has received 2 and a half cartoons free.
  • Receive the PO.
  • 519 is updated as 40 after receiving PO.
  • Inventory adjustment is created for 100 items (40*2.5). Posted Adjustment. Inventory was updated to 140 available.

Note that on Category, Sub-category and UOM screen, a validation message is displayed when New button is clicked. This has been resolved in beta2.


01 May 201809:33AM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 02-05-2018 12:00 AM Time Taken: 2.00

Hi Alvis,

Below is the test results.

When are unable to enter amounts that is greater than 3 digits as the FOC items. Refer to item 6.

Test Environment

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


Thanks

Rashna


01 May 201810:07AM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 01-05-2018 10:07 AM

Hi Rashna,

The current design only allows for 2dp in FOC. If you need to change the screen design, please log a new case.

There is a new case in version 9.5 that will allow for FOC items to be entered in PO entry screen as a separate line.

regards
Alvis


01 May 201802:07PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 01-05-2018 02:07 PM Time Taken: 1.00

Hi Sanjay, 

This case has been passed as per comments 6 and 7.

As per the discussions with Vineet and I.

  1. For scenarios where conversion rate is more than 2 digits. Users can round the receiving FOC quantity nearest to 2 dp.
  2. This will create an adjustment where the qty can be altered before receiving.
  3. For example, referring to item no 6 in the comment 6, 0.175 can be converted to 0.18. The adjustment will be created with quantity 7.20 instead of 7.
  4. Users can edit the qty before posting adjustments.

Thanks 

Rashna 


02 May 201808:37AM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 02-05-2018 08:37 AM
Hi Rashna, has documentation been updated?. If so, go ahead and close this case.

04 May 201810:14AM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 07-05-2018 12:00 AM Time Taken: 1.00

Hi Sanjay, 

I have documented the case under 

Backoffice -- Purchasing -- Receive PO.

The details have been added

  1. Steps to receive PO.
  2. Details of the contents on the PO screen.

Thanks

Rashna


07 May 201806:15PM Comment 11 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 07-05-2018 06:15 PM
Thanks Rashna. 

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

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