We have an assembly item flagged Special Work Order Item on its item record. This item is a component of several non-printed kit/package items ("Print Items" unchecked on the kit).
When the kit is sold on a Sales Order and this component is short on stock, the kit line shows the shortfall as backordered - expected. But we can't find any way to actually resolve it:
- The "Create WO" column on the Sales Order line (which the item's Special Work Order flag is supposed to default to checked, per the field's help text) is greyed out/uneditable on the kit's summary line — there's no line for the individual kit member to carry that checkbox.
- No Work Order is ever auto-generated for the order, unlike a Special Order/Drop Ship purchase item, which does auto-generate a linked PO on save.
- Manually creating a standalone Work Order for the same assembly produces real inventory, but there's no field anywhere on the WO (Customer, Related Records, etc.) to link it back to the originating Sales Order — so the SO's commitment logic never recognizes that supply as satisfying it.
- Unchecking "Special Work Order Item" on the item record and adding a brand-new kit line to the SO afterward still results in the new line showing backordered — suggesting the kit itself may be storing its own snapshot of the component's special-order-type behavior (analogous to how
kititemmember.dropshipmember doesn't stay in sync with the item's live Drop Ship Item flag — a related, separate issue we ran into with a different item).
What we're trying to figure out:
- Is there a supported way to link a manually-created Work Order to a specific Sales Order so its supply counts toward that order's commitment?
- Does a kit/package item capture a per-member snapshot of settings like Special Work Order Item or Drop Ship Item at the time the component is added — separate from the live item record — and if so, is there a supported way to refresh that snapshot short of removing and re-adding the member on the kit?
- Is "Special Work Order Item" simply not supported for kit/package components at all (i.e., this flag is only meaningful for items sold on a standalone line), and if so, is that documented anywhere?
Any pointers to relevant SuiteAnswers articles, or confirmation this is expected/unsupported behavior, would help - we're trying to decide between removing the flag (losing dedicated per-order production tracking for standalone sales of this item) versus creating a separate kit-safe duplicate SKU.