Update the Item Vendor field 6 with the last PO cost
When user enter and prints a PO and there is an Item Vendor Record, Elliott updates field 6. But if user changes the PO cost, this field is not being updated. From the conversation with Roger, I understand it has to do with audit trail on the PO line and a situation that there might be another PO for the same item and a different cost. I see the point but the discrepancies that are created because the cost in field 6 are worse than the benefit. I suggest to update field 6 if the Po line cost is changed, or at least have a global setup that will allow to do it.
Avi Weissbard - Cybermac software LLC
shared this idea
AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
responded
I remember it used to work the way you wanted. That is to say, when a changed PO is printed, the item vendor file, "6. Last Purchase Cost" is also updated. Then we received complaints from users that the Last Purchase Cost value is incorrect in some situation. Here is an example, on 1/1/21, a PO of item A has a purchase cost of $100. On 1/1/22, another PO of 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 cause problem.
Obviously, you can argue this either way. But I consider the old logic is more damaging than helpful. Having a global setup flag does not necessary solve the problem. The likely scenario is we will spend time to investigate for an unhappy user on why the value "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 problem. This maybe something we can consider in V9.
The solution in this scenario is that user can cancel the old PO or PO line item of the wrong cost, then add a new PO or PO line item. Them the new PO cost will be updated to item vendor’s “6. Last Purchase Cost”.