A revision must show retained, removed and added items while preserving earlier withdrawals and return decisions.
Index
A bill of materials can change after components have been picked; replacing the entire list hides what staff already prepared.
The rule that changes the scope
A revision must show retained, removed and added items while preserving earlier withdrawals and return decisions.
An ERP can maintain orders; a custom extension compares list revisions with physical project picking.
A revised list can increase an item's quantity without changing its code. Comparison must find that difference rather than only new and removed products. When picked material remains on the bench, record who performs physical reconciliation. Demonstrate a revision arriving during picking: some items have already left while others remain pending. The system should produce proportionate actions instead of requiring staff to restart every movement from the beginning.
Specify operational deliverables
- Associate picking with the bill-of-materials version used during withdrawal.
- Show the difference between still-required material and items already picked.
- Record authorized returns without erasing the movement that created the withdrawal.
Test the exception before acceptance
In a hypothetical scenario, a component leaves the list after being picked; staff must receive a return task rather than lose the item from the record.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring two list versions and a picking check performed between them.