NetSuite supports Assembly Items, which are build-to-stock Inventory Items, typically created using Work Orders.

A Work Order specifies how many of the Assembly Item units should be built (that is, manufactured), and which Component Items will be consumed (that is, used). Component Items are typically Inventory Items but could be Assembly Items if in a multi-level bill of material (BOM).

For example, suppose a Work Order specifies building 100 units of assembly item A Each assembly item A is built using two units of inventory item B and two units of inventory item C. When 100 assemblies of A are built, 200 units of B, and 200 units of C, will be consumed.

You can do build transactions directly in NetSuite, or in the ShipHawk WMS. A Build is a single transaction that both creates the Assembly Item and consumes the Component Items. A Build does not need to specify a Work Order, but typically does. (Note: an Un-Build or Disassembly transaction can also be initiated in NetSuite or in the ShipHawk WMS).

Processing Work Orders

To process work orders, from the main menu, first choose Adjust/Transfer/Build. Next, picking a work order is the same as picking other orders.

For the work order, on the Inventory Adjustment/Transfer screen, for Action to be Taken, click Build, and for Reason, select Manufacturing:

Click Continue.

Next, on the Inventory Build screen, set Build Action to Assemble (the default) and enter the Item ID. The Item ID field will auto-populate (if the item ID is valid).

Click Continue.

Next, on the Inventory Build screen, enter where and how much to build. Only valid work orders that are for this item ID will display in the Work Order no drop-down:

Next, on the Inventory Build screen, complete the following fields:

• Quantity to Assemble

• Consume Components from Bin

• Assemble Finished Goods at Bin ID

• Container ID (Optional)

Click Save Build.

The work order is complete:

The quantity built and consumed will now be displayed on the Administration screen for the work order.

Work Order WIP (Issue/Completion)

Process manufacturing requires a distinction between component issue and finished good completion for a Work In Progress (WIP) work order.

The ShipHawk WMS supports process manufacturing workflows in your ERP system (such as NetSuite) by providing a way to declare separately the consumption of raw materials and the creation of finished goods for a work order in the ShipHawk WMS.

While a Build is a single transaction that creates the Assembly Item and consumes the Component Items, the Work Order WIP (Issue/Completion) approach includes two transactions:

1. An Issue transaction against the Work Order.

2. A Completion transaction against the Work Order once the manufacturing process has been completed.

An Issue transaction reduces component inventory during a manufacturing process and moves it to an in-process status.

A Completion transaction declares the new inventory has just been created by the manufacturing process.

Processing Work Order WIP (Issue/Completion)

From the ShipHawk TMS main menu, select Workflow, and then Issue Raw Materials.