| Subject: | Receiving inventory items with ZERO quantity updates the item cost to Zero |
| Summary: | In version 12.42, when an item is received with 0 quantity, the system adjusts the last cost to 0. Consider the below example. - PO: NAPO013544 corresponding receiving HQPR201779, item CO18030797 which was ordered was not received.
- However, after posting this receiving, a cost update was passed for item CO18030797, as shown in Figure 1.1 below.
- Review figure 1.2 which is a snap of the Purchase Order Received a report of the corresponding Purchase Order.
The system should not adjust cost if the received quantity is 0 for an item in a particular Purchase Receive.
*** Sanjay - Removed Images as they contain client-specific data **** |
| Audit Notes: | Edited by sanjay on 08/12/21 16:32. Edited by vineet on 08/12/21 16:29. Edited by vineet on 08/12/21 16:21. |
| 06 Dec 2021 | 10:20AM Comment 1 by Vineet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 10-12-2021 10:00 AM Time Taken: 1.00 Notes: Edited by vineet on 08/12/21 16:27. |
| Bula Team OTG We have managed to reproduce the same on your copy of the database using the same steps: - Created Purchase Order for Supplier TAP01. location NAD01 adding 2 items PG01100013, CO18030797. PO: HQPO006075.
- At the time of PO create the last cost for item PG01100013 was 2.60 and the last cost for item CO18030797 was 0.5991.
- Approved the PO
- Received only item PG01100013 via receiving number HQPR201928.
- After receiving verified cost on Product Master for these items for location NAD01. The last cost for item CO18030797 which was not received was 0 now.
Regards
Vineet Ram
222 0085 |
|
| 08 Dec 2021 | 10:26AM Comment 2 by Vineet (Link Business Solutions) This comment has been removed |
| 08 Dec 2021 | 04:36PM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-12-2021 06:32 PM Time Taken: 4.00 |
| Hi Vineet, refer to case L12305. This issue was resolved in LinkSOFT Version 12.44. I have created a patch for 12.42.1208 with this issue resolved. |
|