I have a strange situation where if I go CHANGE an SRM local PO that has already been ordered, let's say I increase the quantity or price and click the "CHECK" button I sometimes get errors like the following:
This purchase order has back-end errors No instance of object type PurchaseOrder has been reated. External reference: PO header data still faulty External document number 3200000240 already assign d
But the really weird thing is if I click on check again a couple of time the errors eventually dissappear and I can order the PO.
And this error seems to only happen sometimes...very ad hoc.....
I do have the BBP_DOC_CHECK_BADI active but the code inside the custom development has NOTHING to do with these errors above.
Why on earth would it be trying to assign that PO number in the backened anyway if it is already created in the backend?
And ideas on this strange problem?
NOTE: We are on SRM 5.0
Any help would be greatly appreciated 😉