Hi @Wiktor,

Could you please share a screenpicture of Shop order material line for the part you are trying to Unreserve? (Make sure ‘QPA & Qty reserved are visible)

Further attach an screen picture of ‘Inventory Part in Stock’ and ‘Inventory Part in Stock reservation’ for the given part where we can see Qty on hand and qty reserved.

This would allow us to get a better idea and provide and answer to you!

Regards,

/Vibhu.

Hi @Vibhusitha Jananjaya 

Screenshots below.

There is no visible qty reserved in Shop Order Materials, as the issue has been captured few days ago.

Should we try to repeat the issue to show what is qty reserved?

Hi @Wiktor 

Some technical information regarding this error message...

The above error message is in InventoryPartInStock logical unit. Above error message is raised every time the qty_reserved goes below 0 when an inventory part in stock record is inserted/updated.

IF (rec_.qty_reserved < 0) THEN
   Raise_Qty_Neg_Error___(rec_);
END IF;

Hope the above information will help to narrow down the issue a bit. Further, in ​‘Inventory Part In Stock and Inventory Part In Stock Reservations” window, reserved quantity shows as 0 while “Shop Order Materials” window shows reserved quantity as 1.

If there is no signs of negative reserved quantiles from the application end, its suggested to debug and see, the reason behind this error.

/Shardha

Hi @Wiktor,

The reason for the error message is though the reservation is visible in “Inventory Part In Stock Reservations” window, the reservation is not available in “Inventory Part In Stock ” window. Currently reserved qty in Part in stock screen is ‘0’ and when unreserve the shop order reservation will update as ‘0-1= -1’. This negative value is not allowed, hence you get the error.

This misbehavior of reservation for material has been observed previously, but from tracks like App9 & 8. My gut feeling say’s the solution should be a data repair. But i’m not sure how, Parking of SO has an impact to this.

 As @Shardha Weeratunga suggested best option would be to debug and see what can be done here. Through debugging you can find the exact reason and the solution.

However, I hope this clarify your initial doubts though the final issue is not resolved.

/Vibhu