This particular item 167290 has two delivery notes totaling 92 but another delivery note reversed this quantity (-92).
On the Inventory transaction, it shows two “On Order” quantity which I want to cancel.
But these two transactions have an Output Order which the Functions/End Inventory Order is greyed out. How can I cancel this transaction? Pls help me on this. Thank you
Hi, I have set the parameters: End output inventory order in Inventory Management setup, yet it is not working because this item already Posting- picking list registration with status completed.
You need to remove it through the order. There is no reason code on the deliver remainder - have you customized this? You would need to show us the inventory transactions and explain the process steps of how you got there.
Press deliver remainder, it shows you the balance of the line, you define the quantity to delete and press cancel quantity - outstanding amount is reduced, status of lines updated if applicable.
I have experienced some strange behavior in this area. Check the two On Order transactions. Is there anything populated in the Inventory Reference, Inventory number, & Picking route fields? If so, are any of them blank? I have had situations where I could not End the Output order but deleting it solved the problem. I have also had situations where I had to go through the AOT to InventTrans and clear out values from TransChildRefId because the Output Order was already ended but was still on the transaction for some reason. Though we also have a lot of modifications in this area that could be causing interference.
I realized that the user had a dimension batch no n location filled during posting that particular item in SO and they reversed the same item without the dimension batch no n location being set up.
You cannot reverse it as standard without these dimensions - they are transaction defined by the item - I would look into debugging the process, understand the loophole then investigate if it can be rectified.
by my technical person’s advise, only data patching can help through to resolve this. but Im not sure where to find that particular item in Table>data dictionary…