Update the Item Vendor Field 6 Last Purchase Cost When PO Line Item FOB Cost Is Changed

Update the Item Vendor Field 6 Last Purchase Cost When PO Line Item FOB Cost Is Changed

Release Date: 12/05/2022
Version: 8.5 & Up

Q - When users enter and prints a PO and there is an Item Vendor Record, Elliott updates field 6. See sample screen below:

But if users change the PO cost, this field is not being updated. I understand it has to do with situations where there might be another PO for the same item and a different cost. I see the point, but the discrepancies that are created because of the cost in field 6 are worse than the benefits. I suggest updating field 6 if the PO line cost is changed, or at least have a Global Setup option that will allow users to do it.

A - It is a timing issue.  I remember it used to work the way you'd like it to. That is to say, when a changed PO was printed, the Item Vendor file, "6. Last Purchase Cost" was also updated. Then we received complaints from users that the Last Purchase Cost value was incorrect in some situations. Here is an example: On 1/1/21, a PO for item A has a purchase cost of $100. On 1/1/22, another PO for item A has a purchase cost of $110. The Item Vendor file field "6.Last Purchase Cost" is $110 at this moment. With the old logic, if we go ahead change the older PO on 1/1/21, we may or may not change the line item FOB cost.  The result of printing the changed older PO is that item A's last purchase price is now changed back to $100 and this causes problems.

Obviously, you can argue this either way. But I believe the old logic is more damaging than helpful. Having a Global Setup flag does not necessary solve the problem. The likely scenario is that we will spend time  investigating for unhappy users why the value in "6. Last Purchase Cost" is “wrong.”

To really solve this problem, we need a sophisticated logic to check if this changed PO line item is the last PO of item A for this vendor. Since there’s no existing index to support this operation, it will result in performance problems. This might be a V9.0 improvement we can consider.

The solution in this scenario is that the user can cancel the old PO or PO line item with the wrong cost, then add a new PO or PO line item. Then the new PO cost will be updated to the Item Vendor’s “6. Last Purchase Cost.”


EMK


    • Related Articles

    • Feature - Allow to Mass Update PO Line Item Cost & Synchronize to Current FOB Cost

      Release Date: 7/9/21 Versions 8.5 & Up This feature is useful when your vendor raises a price and new price is applicable to an outstanding purchase order. It allows your buyer to bring up the affected PO one line item at a time to synchronize that ...

    • FOB Cost Will Not Be Changed Because It Was Manually Overridden

      Release Date: 02/17/2022 Version: 8.5 & Higher Q - We sometimes run into the warning message shown below when changing cost on PO line items that have previously been changed by using the import method to change the cost. The discount percentage will ...

    • PO1501 Purchase Order and Receiving Item Vendor File Maintenance

      Item Vendor File Maintenance Application Overview This application provides the means whereby the Purchase Order and Receiving package keeps track of the vendors who provide particular items, and it allows the vendor's identifying number for an item ...

    • Feature - Support Negative PO Line Item Unit Cost

      Release Date; 5/25/2018 It has been suggested that if we can enter a negative unit cost for a Purchase Order Line Item, then we can use it to represent deposits paid on the purchase order, which would be very helpful. We did an internal test of this ...

    • Feature - PO Export by Vendor EDI Profile

      Date Released: 9/8/21 Updated: 3/30/22 Version: 8.5 and Above This feature is added to provide better support of EDI 850 in the PO module. In PO -> Utility -> Purchase Orders Export, this function will now behave based on the Vendor EDI Profile if ...