Scrap & Rework Management

An operator discovers defective parts during an operation and enters a scrap transaction specifying quantity, scrap reason code (e.g., dimensional out-of-spec, surface defect), and the responsible operation. The system posts the scrap to the scrap expense account, reduces WIP, and generates a nonconformance report (NCR). A quality inspector evaluates the scrapped parts and selects a disposition: rework (creates a rework sub-order), use-as-is (requires deviation approval), or scrap (final). If rework is chosen, the system creates a rework work order with a modified routing for the repair operations, consuming additional labor and materials. Upon rework completion, parts are re-inspected and accepted quantity is moved back into the main work order's good quantity. Scrap cost is accumulated by reason code and work center for Pareto analysis.

scrap_transactions { txn_id: string, work_order_id: string, op_id: string, quantity: numeric, reason_code: string, employee_id: string, amount_minor: int64, currency_code: char(3), external_id: string };
ncrs { ncr_id: string, scrap_txn_id: string, status: enum, disposition: enum, rework_wo_id: string, external_id: string };
(reference, product may differ).

POST /v1/scrap-transactions { work_order_id, op_id, quantity, reason_code } -> 201 { txn_id, ncr_id };
POST /v1/ncrs/{id}/disposition { disposition: REWORK|USE_AS_IS|SCRAP } -> 200;
POST /v1/ncrs/{id}/rework-order -> 201 { rework_wo_id };
emits scrap.recorded, ncr.created events;
idempotent via external_id.

NCR: OPEN -> UNDER_REVIEW -> DISPOSED;
terminal CLOSED;
rework sub-order follows standard work_order ST;
guard: USE_AS_IS disposition requires deviation approval before closing NCR.