I have a problem. For some reason an internal order was processed that created a PO for a non internal vendor, but is treating it like it is an internal vendor. Once we noticed it, we deleted the PO after we tried to change it to an internal vendor, but it would not let us. BUT, when the parts were received, they received under this non-internal vendor PO, creating receipts that I cannot remove from AP since it is creating new receipts every time. I am just not sure what to do here:
PO that is not deleted any longer:
Here is one receipt:
When I try to grab the receipt in AP to remove it, it won’t let me, so I am not sure what to do. It is like it somewhere in between internal and non-internal orders.
Also, after this happened, I verified that the only choice to create an internal vendor for our orders is the M3 Internal Vendors, so SAIA is not a choice. It is odd. Let me know what needs to be done to get rid of the receipts. Other than that it is not causing too much grief.
Thank you for sending this in our way - I agree here this is a really odd case. We typically require the internal vendor associated with PO be internally facing (intercompany = yes).
I’ve dug through the PO you sent over… and it’s got an externally facing vendor associated to it somehow. I’ve been building out cases here to try and reproduce this in a backup, and every internal build order I make forces me to use one of the internal vendors associated with it.
I’m wondering… if maybe this was an order that was converted over to internal order and was originally externally facing?
That aside though - I’m sending this to the engineering team to review how this happened, and to see what we can do about the receipts tied to that PO you sent in.
I’ll be in touch with an update as soon as I have additional details here for you.
Yes, I tried to recreate it also, but to no avail. It could have been an order converted to an internal order, but I am not 100% sure. We don’t do that often. We did delete that PO when we saw it happened and created internal POs, but the system only will use that PO. It is very odd.
I can attest that it is not still happening or hasn’t happened since this situation. I have been watching for it.
I’ve got a ticket in our queue for this issue, and engineering has uncovered something here that they wanted to pass along:
The root cause of the issue here is that the order was “converted to internal”.
When you do so, we have a select box for the vendor for the order - due to a code issue we didn’t set the right vendor even when the internal vendor gets selected.
Kelly we’re working on a fix here that’ll keep this from occurring in the future when converting external orders over to internal orders. We’ll have to test through this, so in the meantime please refrain from converting external orders to internal until we have a resolution in place for you!
I’ll be in touch with another update once I have details here.