Why does assigning lots to work order with phantom assemblies the buildable quantity is 0 and removes lots added when creating assembly build

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** The issue of assembly builds showing a quantity of 0 for the components and removing lots added when creating assembly build with phantom assemblies could be due to several reasons: 1. Work Order Adjustments: If adjustments are made to the work order, such as zeroing out the quantity of a line, it will carry over into the assembly build and allow the build to be completed even with a quantity of 0. 2. Order of Field Selection: 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's recommended to select sub, location, and then assembly to avoid quantities changing. 3. Inventory Commitments: If the committed amount is 0, it might be because the inventory that needs to be committed is no longer available. This could be due to the inventory being committed on different orders or the inventory being low. If a work order is showing 0 committed, then the assembly build is going to show 0 consumed. 4. User Errors: There could be instances where the user is entering incorrect quantities while creating the assembly build. For example, if the components are backordered and the user is trying to build for the full quantity but only a part of it is committed so far to the work order, the user might be entering the committed quantity or 0 quantity. When the component quantity is 0, NetSuite lets you save the assembly build without needing to put inventory detail for that component line. In the case of Lot Numbered Assemblies with the “Mark Sub-Assemblies Phantom” enabled, if you set your picking preferences to FIFO, FEFO, or receipt date the system will choose lot by the received date in the order designated. Depending on if you have NS WMS, rf smart, or perhaps advanced manufacturing you can direct production staging pick tasks in the same manner. The purpose being to eliminate the need for a material handler to choose a lot number. As for the issue of Assembly Builds randomly changing the component usage, it could be due to how NetSuite handles floating point values for display/calculations.