when using a item source: phantom, the assembly is not getting committed, how do I fix this?

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 you're facing with the phantom assembly not getting committed might be due to the way NetSuite handles phantom assemblies. Phantom assemblies are typically used as components in a larger assembly build, but they can also be used to create stock items. However, they are not designed to reduce raw material stock when there is a Sales Order on that Phantom Assembly Item, nor to calculate the COGS from the Phantom Assembly Item. If you want the field to show up on the transaction item line on work orders, you might need to add a custom line field sourced from the item. However, this could be duplicative as the item source field is a native NetSuite field and should already be on the work order. If you're trying to achieve a reduction in raw material stock when there is a Sales Order on that Phantom Assembly Item, but not maintaining the assembled item stock, and you want to calculate the COGS from the Phantom Assembly Item, you might want to consider using a Kit instead of a Phantom Assembly. Remember, the phantom assembly won’t work the way you are describing. The phantom features only work on a work order.