the assembly build lines source the item lines from work order with 0 quantities even though the item quantities on work order lines are filled with quantity

AI generated answer (using internal Slack threads):

Based on the conversations, it appears that the issue of assembly build lines sourcing the item lines from work orders with 0 quantities, even though the item quantities on work order lines are filled with quantity, could be due to a few reasons: 1. User Error: There might be instances where the user accidentally zeroes out a line or makes adjustments when creating the work orders. This could lead to the assembly build showing a quantity of 0 for the components. 2. Order of Field Selection: The order in which fields are selected on the work order could also cause this issue. 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. It is recommended to select sub, location, and then assembly to avoid quantities changing. 3. Commitment Issues: If the full quantity is not available, commitment occurs only when the full quantity is available. If one or more lines show committed as 0 since the component inventory may be low, NetSuite builds the assembly anyways as that is an allowed action with zeroed qty lines. This could lead to the assembly build showing a quantity of 0 for the components. 4. Backordered Components: If the components are backordered because the inventory is either out of stock or it's committed to other orders already, the user might be entering the committed quantity or 0 quantity while trying to build for the full quantity. This could lead to the assembly build showing a quantity of 0 for the components. 5. Rounding Issues: There might be instances where NetSuite uses massive floating point values for display/calculations, leading to discrepancies in the component usage. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******