The quick answer
Open a released, non-WIP Work Order and select Create Build. Check the assembly, build quantity, location, BOM, and component quantities, then save the Assembly Build. On the saved build, open GL Impact and compare the finished-goods debit with the component-inventory credits. Return to the Work Order to verify its Built quantity and linked build.
This example builds 8 Aurora Control Units from WO-7421 at Reno. The build consumes 16 Sensor Boards and 8 Enclosures. Amounts and the person and operating-company names in the screenshots are fictional example data.
Before you start
This procedure applies to a non-WIP work order with Assemblies and Work Orders enabled. Confirm that the order is saved and Released, has quantity remaining to build, and uses a valid assembly, components, location, subsidiary, and effective BOM or revision for the build date. Check component availability and any required bin, lot, serial, or inventory-status detail for the components and finished assembly. Your role needs access to the work order, Assembly Builds, and GL Impact. The posting period must be open or your role must be allowed to use the applicable override. WIP orders instead use issue and completion transactions and usually a close transaction.
01 · Check the non-WIP work order
Find and open WO-7421 from the work-order list or a linked transaction. It shows Aurora Control Unit, quantity 8, location Reno, status Released, WIP No, and Built 0. For this revision and quantity, its BOM calls for 16 Sensor Boards and eight Enclosures. The work order can affect planning and commitments, but Released status itself does not transfer inventory or post to the GL.
02 · Record the Assembly Build
Click Create Build if the order is eligible and has remaining quantity. On the Assembly Build, confirm Created From is WO-7421, assembly is Aurora Control Unit, intended build quantity is 8, location is Reno, and the BOM is Aurora Standard Revision B where displayed. Review the transaction’s component quantities for 16 Sensor Boards and eight Enclosures; yields and permitted edits can change what the build consumes. Supply required inventory detail for both components and the finished assembly, then save.
03 · Inspect GL Impact
On the saved Assembly Build AB-7422, open GL Impact. This controlled example debits Finished Goods Inventory $720, credits Sensor Board Inventory $560, and credits Enclosure Inventory $160. Confirm total debits and credits both equal $720. Allow inventory costing to complete before treating the amount as final. Accounts and values depend on costing methods, cost layers, transaction timing, component yield, units, negative inventory, and configured charges. If values differ from the applicable component costs, inspect those inputs and any later costing adjustment before treating the difference as an error.
This example has no labor or overhead components, so the illustrated GL Impact contains only component inventory costs. Other accounts may include labor, overhead, or manufacturing-charge lines through their item, BOM, and costing configuration.
04 · Reconcile the work order
Return to WO-7421. Its Built quantity increased by the saved build quantity and is now 8. Related Records links to AB-7422 in this example; a different form may present a Builds subtab. The example order shows Built status after the full quantity is built. Check the status and remaining quantity assigned in your account.
Check the result
- Production: AB-7422 is linked and Built is 8.
- Accounting: the displayed GL debits and credits balance at $720 in this example, after costing completes.
- Scope: the Work Order planned production; the Assembly Build recorded it.
Common questions
Does a released non-WIP work order post to the GL?
No. It can affect planning and commitments, but releasing the work order does not itself post inventory or a GL entry. In this example, saving AB-7422 records the build and its accounting impact.
What should I check before saving an Assembly Build?
Confirm the source work order, assembly, intended build quantity, location, and effective BOM or revision where displayed. Review the component quantities and any required inventory detail for the components and finished assembly. The example builds eight Aurora Control Units using 16 Sensor Boards and eight Enclosures.
Why might the GL Impact differ from the example’s $720?
The $720 is illustrative. Actual values depend on the item costing method, component costs, cost layers, transaction timing, units, yield, and configured charges. Wait for inventory costing to complete, then compare the posted accounts and values with the saved build’s quantities and applicable costs.
Does a non-WIP Assembly Build include labor or overhead?
It can when those costs are represented by configured items, BOM components, charges, or costing rules. This example has no labor or overhead lines, so its GL Impact shows only the illustrated component inventory costs.
How do I reconcile the build with the work order?
Verify the saved Assembly Build number, quantity, location, and components. Check that its GL Impact balances after costing completes, then return to the work order. WO-7421 shows Built 8 and links to AB-7422 in Related Records in this example. Other forms may show a Builds subtab or different status.