NS work order — Path 1 · from sales order

WO created FROM Sales Order

Path 1 covers the case where one or more lines on a customer SO require assembly. A Work Order is created FROM the SO (workorder.createdfrom = so.id) preserving the SO ↔ WO link end-to-end. Components are reviewed at the correct location, production runs, the Assembly Build is entered in NetSuite (Mike approves at /assembly-build.html), finished goods are added to inventory, then the SO is fulfilled. Item Fulfillment fires the ★ automation alert to Finance; Finance reviews, invoices, monitors terms, applies payment, and closes the order.

Shortcut: if the FG is already on hand at the correct location, fulfill the SO from inventory and close the WO marked unused.

Diagram: ns-work-order-path-1-from-sales-order.html. Master wiki: wiki-ns-work-order-master.html. Other path: Path 2 inventory build. Workflow contract: wo_lifecycle_from_sales_order_path (risk 3).

Trigger

• SO master classifies a line as assembly_item; SO Path 2 (assembly) dispatches WO Path 1 to actually build it.
• Direct WO entry in NetSuite linked to an existing SO via createdfrom = so.id.

Driscoll Melt Mates kit

From SO assembly-line to WO close (8 stages)

1. SO assembly-line detected — intake operator (or auto-classifier) flags a SO line where the item is an Assembly Item. Path 1 dispatched.
2. WO created — WorkOrd record: createdfrom = so.id, assemblyitem = SO-line item, quantity = SO-line qty, memo (TBD = SO.otherrefnum). HITL gate: WO creation through proposed_actions per ADR-031.
3. Component review — BOM lookup against inventoryitemlocations at WO.location. If shortage: hold + escalate (see Failure modes). If OK: advance.
4. Production runs — crew completes assembly on the floor. Waste, labor hours, line time captured manually (kiosk/scanner is STUB).
5. Assembly Build approval — Mike reviews at /assembly-build.html; HITL via proposed_actions. On approve, NS posts AsmBuild: createdfrom = wo.id, item, quantity, custbody_waste (TBD), location, trandate.
6. Component issue — WkOrdIss rows created per BOM component (createdfrom = wo.id). Inventory decrements at component level.
7. FG credit — inventory_balance.quantityavailable += quantity at WO.location for the finished assembly item.
8. WO closed + SO fulfilled — WO.status = 'Built'. ItemFulfill created against SO (NOT WO): createdfrom = so.id, otherrefnum inherits from SO. ★ Universal Finance handoff fires (planned R594 automation).

What is true after Path 1 completes

• The customer's SO is fulfilled with a build-to-order assembly that did not exist in inventory before.
• Records linked end-to-end: SO.id ← WO.createdfrom, WO.id ← AsmBuild.createdfrom, WO.id ← WkOrdIss.createdfrom, SO.id ← IF.createdfrom, SO.id ← CustInvc.createdfrom.
• Customer PO# (SO.otherrefnum) traceable end-to-end through IF + CustInvc; WO carry-through pending the memo TBD resolution.
• Inventory math: components decremented per BOM × quantity at WO.location; finished assembly item incremented by the build quantity.
• Variance audit: if |actual_built − estimated| / estimated > 5%, a HITL proposed_actions row is staged for review.
• Reflexion writes a quality score: build success, component accuracy, lead time vs. estimate. Used to improve future scheduling.

What can go wrong + recovery

Adjacent flows + diagrams

Code paths + invariants

Dated trail

Path 1 sub-contract spec

Sub-contract: wo_lifecycle_from_sales_order_path · risk 3 · dispatched by WO master when origin = from_sales_order.

Path 1 NS records (field-level)

Path 1 verify_checks

When Path 1 breaks

Open questions for Path 1

• TBD
  WO customer PO# field

  Mike to confirm. Expected bodyFields.memo threaded from SO.otherrefnum. Every Schema reference flagged TBD until confirmed.

• STUB
  NS workflow for Finance alert

  Platform event fires; NS workflow trigger on itemfulfillment.status='Shipped' still pending build.

• OPEN
  FG on-hand shortcut auto-detection

  Operator decides "fulfill from inventory + close WO unused" today. Could auto-detect at WO creation.