Component quantity not sourcing properly when creating assembly build in netsuite

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the issue of component quantity not sourcing properly when creating assembly builds in NetSuite could be due to a few reasons: 1. The quantity of a line on the work order is set to zero. This can carry over into the assembly build and allow the build to be completed even if the quantity is zero. 2. The committed amount is zero. This could happen if the inventory that needs to be committed is no longer available because the work order has been built. 3. Changes are made to the work order. For example, if the assembly is selected first or pre-filled in from another process, then setting the sub and location can cause the form to reset and values at the line level can change. To avoid quantities changing, it's recommended to select sub, location, and then assembly. 4. The work order is created automatically from the PO. If the full quantity is not available, the commitment will be zero even if there is a partial quantity of the component available. This could lead to a situation where the assembly is built with zeroed qty lines. 5. The components are backordered because they are either out of inventory or it's committed to other orders already. In this case, the user might be entering the wrong quantity amount when trying to make the assembly build. It's also worth noting that if the assembly build is showing zero consumed, it could be because those components were not available for use since they were committed to another work 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. ******