A requisition was released and approved for $10K. Somewhere and somehow, the unit cost in PO20 increased to $30K. We use the PO100 job, and was picked up from PO23. No manual changes occurred, and there is only one line.
Thoughts? Thanks teams.
What type of item (I, N, X, S)? What is the cost source on the PO Line? What is the cost source on the Requisition? you can drill to both get both of these.
Brenda, Did you drill around and look at the Audit to make sure it wasn't changed by a buyer?
Hi Brenda - I have seen this happen in the past on specials and possibly on service. If that same exact value was used for a previous PO (for example, Item entered as 12-789 in both requisitions) then the previous cost for the special carried over to the new PO as sort of a last cost default.
I'd check PO63 for that company and 'item' if it was a special to see if my theory holds. We had that happen fairly often in S3 with specials.
But in that case wouldn't last cost apply to the req line as well? We definitely need to know the cost source on the req line and PO line. But I'm guessing that the cost source is "entered" on both and the unit cost was changed in PO23 prior to the line being added to the PO. There won't be an audit on that.
I'm not saying it's logical, I'm just saying that I've seen it before.
Jon, thanks. This- PO23- was my thought as well. Typically when the line source of "last PO cost," will change it on the req. We are all stumped... my concern is we have caught it on this PO, but are there others? Especially in the myriad of patchces and updates in recent months.
Hi, yes, first place we looked. The audit record only shows buyer to buyer, but no cost changes.
Hi, thanks Pam. The source was last cost, but this did not change on the Req. That is the odd thing. The req went through approval as the original (intended) amount, but once it went to PO status, the cost changed. Thus, the req still reflects the processed as $10K, but the PO says $30K.
On PO63 - did the last purchase have a buyer message that got released? I would suspect bad timing or someone messing with qty on PO23 to make it try to do math.
