Figure 10.1 — The Work Order form. Drawing to be produced after the UI/UX pass: the work order annotated — product and BOM, target quantity, the issue and receive warehouses, and, below, the requirement lines a release creates: component, required, issued, remaining, issued value.
- Code — from the work-order sequence; leave blank to take the next number. The code follows the order everywhere: its journals, its stock movements, and the lot code of its lot-tracked output all carry it.
- Date — the order's date.
- Product — what is being made; a manufactured product. Release refuses anything else.
- BOM — the recipe to execute (§10.6, below). A product has one active BOM, and the form offers it.
- Target quantity — how many units of the product this order exists to make, in the product's stocking unit. The explosion, and so the whole order, scales from this number.
- Branch — the branch the order belongs to, where branches are tracked.
- Issue warehouse — where components are drawn from.
- Receive warehouse — where finished goods land. The two may be the same warehouse; they are separate fields because on a real floor they often are not.
- Notes — the order's free text.
On release, the form gains the order's requirement lines — component, quantity required, quantity issued, quantity remaining, issued value — a read-only snapshot of the recipe as released. The record also shows the standard cost snapshotted at release, the quantity received so far, the status, and the stamps of when the order was released, completed and closed.