What could be causing the following error message when a user tries to update a Sales Order before partially fulfilling?

One or more lines on this sales order cannot be committed due to a lack of item lot availability. The first sales order and item encountered in this situation is: Sales Order-12345, Item-Sample Thingy, Location-Warehouse 13, Quantity-42, On Hand-30, Available-0, Please review the uncommitted sales orders and line(s) and confirm/adjust lot availability before re-committing the sales order(s).

This error does not occur if the user fulfills without editing the Sales Order.

AI generated answer (using internal Slack threads):

The error message you're encountering is due to a lack of available lot quantity for the item you're trying to commit on the sales order. In NetSuite, the available quantity of an item is calculated as the on-hand quantity minus the committed quantity. The committed quantity is the quantity that has been allocated to sales orders, transfer orders, or intercompany transfer orders that are pending fulfillment. In your case, the item 'Sample Thingy' has an on-hand quantity of 30, but none of it is available. This suggests that all 30 units are committed to other sales orders. When you try to update the sales order before partially fulfilling it, NetSuite checks the available quantity of the item and throws an error if there isn't enough to fulfill the order. To resolve this issue, you can review the uncommitted sales orders and adjust the lot availability. You can do this by navigating to the 'Reallocate Items' page in NetSuite, which will show you what transactions the item is committed to. From there, you can uncommit the item from those orders if necessary. Remember, if you're using multi-location fulfillment, you need to ensure that the 'Inventory Location' field is set correctly on the sales order line, not just the 'Location' field in the body of the sales order. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******