Associating Components with Operations
Use the Manufacturing Work In Process (WIP) feature to assign and issue components at the operation level for items you assemble.
Associating components with specific operations can benefit operations that take a long time to complete. Some components may not be required when the work order starts. Therefore, it is not ideal to issue all assembly components during the first operation. If you associate components with specific operations for a routing, components are issued on the day the corresponding operation begins. For example, a work order is set up as follows:
-
The routing includes 4 operations
-
Each operation takes 1 week
-
Operation 4 requires a special component
Work Order -Start Date:
July 1, 2020
Work Order -End Date:
July 28, 2020
Operation 1 -Start Date:
July 1, 2020
Operation 2 -Start Date:
July 7, 2020
Operation 3 -Start Date:
July 14, 2020
Operation 4 -Start Date:
July 21, 2020
-
If the special component is linked to Operation 1, the component issue date is July 1, 2020.
-
If the special component is linked to Operation 4, the component issue date is July 21, 2020.
To associate a component with an operation:
-
Go to Lists > Accounting > Items.
-
Click Edit next to the WIP assembly item you want to work with.
-
Click the Manufacturing subtab.
-
Click the Components Per Operation subtab.
The list displays all components and their corresponding quantities, as defined on the component list of the item record.
Note:To display the Components Per Operation subtab, create a new or edit an existing Manufacturing Routing.
-
Click a Component Line.
-
In the Operations field, select an operation to associate the component with.
-
Click Save.
After you save your work, the operation associations you set up are applied only to new work orders you create.
Associations can also be defined for existing routings on assembly item records. Based on the specified routing, NetSuite updates the associations to components on work orders.
-
One operation can be associated with multiple components.
-
Each component line can be associated with only one operation.
-
One component can be associated with multiple operations if the component is defined on multiple lines.
-
Not all components are required to be associated with an operation. If no operation is defined for a component, that component is issued at the start date for the routing.
Changing or deleting an operation number breaks all associations to the original operation number. For example, any component associated with the previous operation number will not be associated with the new operation number.
Changing or deleting a component also breaks the association to an operation.
Operation Associations and Sub-Assemblies
If you check the Mark Sub-Assemblies Phantom box, the association between the sub-assembly and the operation is broken. The sub-assembly is replaced with its components on the list of available components. The same operation association is applied to the sub-assembly components. You can create new associations for these sub-assembly components. However, you cannot edit the list of components.