[FR] Add Build Order ↔ Purchase Order demand traceability to prevent duplicate ordering #11226
Description
Problem / Motivation
When multiple Build Orders require the same part, there is currently no automatic or visible way to trace which Build Order(s) generated a Purchase Order, or whether an existing “parts on order” quantity already covers a specific Build Order line item.
This creates a real risk of duplicate ordering, especially when purchasing decisions are made from the Manufacturer Part / procurement view, where only aggregated stock and “on order” quantities are visible.
Current behavior
Build Order view
-Build Orders show “Parts on order” as a global aggregated quantity
-This value is not contextual to a specific Build Order or line item
-It does not indicate whether the current Build Order line actually generated the purchase request
Example:
Build Order line requires: 4
System shows: 100 on order
From this, the user cannot tell:
-If those 100 were ordered because of this Build Order
-Or if they were ordered for other builds or for stock
-As a result, “Parts on order” behaves like a number, but not a state.
Observed limitation
Users need to know:
-Did this Build Order line generate a PO?
-How much of the “on order” quantity applies to this line?
Currently this requires:
-Manual notes
-Checking PO references
-Process discipline and memory
Proposed behavior
- Build Order line–level demand attribution (informational)
When a Purchase Order is generated from a Build Order line item that line item should record that it generated demand
This should be visible in the UI as a clear indicator or state, e.g.: Parts ordered
This distinguishes between:
“Parts on order somewhere in the system”
“Parts ordered specifically for this Build Order line”
Contextual “on order” quantities per line item
Instead of only showing a global value, show contextual coverage for the specific line item if that line item generated the purchase Request
Example:
Required: 4
On order: 80 / 100
if the part did not generate the purchase request line item it makes it immediately clear that:
-The existing PO already covers the demand for this line and No additional ordering is required, instead the demand should be merged to the already made purchase order and subtract from it.
behavior when merging or adding to existing POs
When generating a PO from a Build Order line item and choosing Merge or Add to existing PO:
Example:
Existing PO: 100 on order , 80 are needed for other build orders
Build Order line requires: 4
UI should clearly show intent:
If merged (no order quantity increase):
84 / 100 on order
If added as additional quantity:
84 / 104 on order
This makes it explicit:
-Whether demand was already covered
-Whether the PO quantity increased
-Why the final PO quantity changed
with the status veiw in manufacturer tab you can clearly see if a build order is pending or that it has parts ordered.
i have tried to look for similar suggestions but couldn't find similar ones
any suggestions ?