How Can We Help?
Real question from the floor
“I have one order with one line item, quantity 10. When it was scheduled the system
generated ten separate requisitions of qty 1 instead of one requisition for qty 10.
Why — and what setting controls it?”
“I have one order with one line item, quantity 10. When it was scheduled the system
generated ten separate requisitions of qty 1 instead of one requisition for qty 10.
Why — and what setting controls it?”
This is expected behaviour for assembly parts, and it is controlled by one company
preference together with a per-part flag. When an order is scheduled, the system decides for
each part on the item whether to raise one requisition per unit or one consolidated
requisition for the whole quantity.
When you get one requisition per unit (N rows of qty 1)
The per-unit split happens only when the part is an assembly part and either of
these is true:
- the company preference Consolidate Assembly Reqs
(consolidateAssemblyReqs) is OFF — this is the default; or - the part’s own Unit Allocations flag (on the Stock Record) is ON — this
forces per-unit requisitions even when consolidation is switched on.
Each per-unit requisition also gets its own assembly barcode / reference, which is what
lets the individual units be scanned and tracked separately on the production floor. So a
quantity-10 assembly line becomes ten qty-1 requisitions, each barcoded.
This is intentional for assemblies
Per-unit requisitions are a feature, not a fault — they give each physical assembly its own
trackable, scannable demand. Only consolidate if your process doesn’t need per-unit tracking.
Per-unit requisitions are a feature, not a fault — they give each physical assembly its own
trackable, scannable demand. Only consolidate if your process doesn’t need per-unit tracking.
When you get one consolidated requisition (1 row of qty N)
- the part is not an assembly part — non-assembly parts always raise a single
requisition for the full quantity; or - the part is an assembly part, Consolidate Assembly Reqs is ON, and the
Stock Record’s Unit Allocations flag is OFF.
Recommended fix — how to get one requisition of qty 10
| Step | Where |
|---|---|
| Turn ON the Consolidate Assembly Reqs preference. | Administration → Company Preferences. Search forconsolidateAssemblyReqs, tick the checkbox, Save. (The preferences screenlists every setting by name and shows an ⓘ tooltip for each.) |
| Make sure the part’s Unit Allocations flag is OFF. | On the Stock Record for the assembly part. If it is on, it overrides the preference and keeps splitting per unit. |
| Re-schedule / re-generate the order’s requisitions. | The row count is decided at generation time, so the change takes effect on the next scheduling run for that order — existing requisitions are not retro-merged there. |
Also merged at PO time
With Consolidate Assembly Reqs ON, matching assembly requisitions are additionally merged
when a purchase order is raised — so even already-generated rows can be combined onto a single PO
line for that part.
With Consolidate Assembly Reqs ON, matching assembly requisitions are additionally merged
when a purchase order is raised — so even already-generated rows can be combined onto a single PO
line for that part.
Decision summary
Per-unit rows (N×qty 1) require: assembly part AND
(Consolidate Assembly Reqs OFF OR Unit Allocations ON).
Everything else yields one consolidated row of qty N.
Per-unit rows (N×qty 1) require: assembly part AND
(Consolidate Assembly Reqs OFF OR Unit Allocations ON).
Everything else yields one consolidated row of qty N.