The quick answer
Create and release the work order first, then use Create Build to carry its assembly, BOM revision, quantity, location, and component requirements into an Assembly Build. Saving the Assembly Build records the production transaction; it doesn't by itself verify final inventory balances or general ledger amounts.
The screenshots show sample data. Person and operating-company names are fictional. Use your own records and values when following the steps.
Before you start
You need permission to create work orders and assembly builds, an assembly item with an applicable BOM revision, a production location, and sufficient component availability. Confirm the BOM revision is effective for the intended production date and determine whether inventory detail is required for the components. BOM and revision fields depend on the enabled BOM features.
01. Enter the work order settings
On the Work Order form, select the intended subsidiary and assembly, then enter the production quantity and date. Set Status to Released and leave WIP cleared so the order can be completed with an Assembly Build rather than WIP issue and completion transactions.
02. Select the subsidiary
Select the subsidiary that owns the production transaction. In this example, the selected value is Harbor US; your available subsidiaries depend on your account and role.
03. Select the assembly and review the BOM
Select the assembly item and review the populated Bill of Materials, revision, units, and production availability. The example uses Beacon Module with Beacon Standard, Revision C, and units of Ea; verify that the displayed revision is effective for the applicable production or effective date rather than accepting a default without checking it.
04. Review the component requirement
Review the Items section before saving the work order. For six assemblies at two Controller Inserts per assembly, the form displays a required quantity of 12 Ea and availability of 40 Ea at Tacoma with 100% yield. If your account requires bin, lot, serial, or inventory-status detail, confirm those requirements before creating the build. Assign any required inventory detail on the Assembly Build before saving.
05. Open the Assembly Build from the work order
Save the released work order, check Released and Built 0, then use Create Build from that work order. The Assembly Build form carries forward the source work order, assembly, quantity, date, BOM revision, and component requirement. In the example, the source work order is WO-6849 and the planned quantity is 6.
06. Set the build location
Select the location where the finished assembly will be recorded and where the component inventory will be consumed. The example uses Tacoma, and the component line shows 40 available before the build.
07. Save and inspect the recorded build
Review the assembly, quantity, date, location, BOM, revision, and component quantity, then select Save. The saved record displays Assembly Build AB-6850 for six Beacon Modules at Tacoma and shows 12 Ea of Controller Insert. This confirms the saved production transaction, not a separately verified inventory balance, valuation, or general ledger amount.
Check the result
- The Assembly Build shows the intended assembly and quantity of 6.
- The saved build shows the intended location, BOM Beacon Standard, and Revision C.
- The Components section shows Controller Insert with a quantity of 12 Ea.
Common questions
What is the difference between a work order and an assembly build?
A work order records planned production and component requirements; it is generally nonposting. An assembly build records the completed production transaction and normally increases finished-assembly inventory while reducing component inventory, subject to account configuration.
How do I build a released non-WIP work order?
Save the work order with Released status and WIP cleared, verify the BOM revision and component requirements, then select Create Build. Confirm the assembly, quantity, location, date, BOM revision, and any required inventory detail before saving the assembly build; available actions and required fields vary by role, features, form, and account configuration.
Why does the assembly quantity change the required component quantity?
NetSuite scales component requirements from the BOM according to the assembly quantity, units, and yield. For example, if one assembly requires two components, building six assemblies requires twelve components when units align and yield is 100%; rounding, scrap, units, or BOM settings can change the result.
Does saving a work order mean the assembly has been produced?
No. Saving a work order records the production plan, not completed production. Production is recorded only after the assembly build is saved, and the resulting inventory balances, valuation, and accounting impact must be verified separately because they depend on account configuration and transaction details.