how to use the work in process work for lot costing item

AI generated answer (using internal Slack threads):

To use the Work in Process (WIP) work for lot costing item in NetSuite, you would need to follow these steps: 1. Create a Lot Numbered Assembly: This is the item that you will be manufacturing. It should be set up with "Lot Numbered" as the costing method. This means that each lot will have a specific cost. 2. Enable “Mark Sub-Assemblies Phantom” in the Item Attributes: If your item components have nested Sub-Assemblies and Inventory Items which are also Lot Numbered, you can enable this option. This will allow the system to pull materials from the appropriate lots when a Work Order is opened for the top-level assembly. 3. Set Picking Preferences: You can set your picking preferences to FIFO (First In, First Out), FEFO (First Expired, First Out), or receipt date. The system will then choose the lot by the received date in the order designated. 4. Create a Work Order: When you create a Work Order for the finished good item (the lot numbered BOM), it will go through and manufacture the item. 5. Manage Inventory Details on Sales Orders: When you put the manufactured item on a sales order, you will need to select which lot number you want to use on the Sales Order. This is done on the fulfillment side. 6. Check Commitment of Lots: If the item goes to back order after saving the Sales Order, it could be that the whole lot is committed to other Sales Orders. You can check this by looking at the assembly record to see what your On Hand, Available, Committed and On Order shows. Remember, if the assembly is marked as a special order, NetSuite will create a new Work Order for that line on the Sales Order and that exact Work Order needs to be built in order for that line to be committed. Even if you do a standalone Work Order for a large quantity of that item, it will not commit until the linked Work Order is built. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******