Allow MRP and MPS to be run by item — single, multiple, or range — in addition to the current by-Site-only behavior, with correct low-level-code BOM explosion and a safeguard for shared components. This would dramatically cut run times, free up batch windows, and give planners the fast, surgical replanning they need without sacrificing accuracy.
How it should work
Add product selection criteria to both the MRP (net requirements) and MPS calculation functions, alongside the existing Site selection — supporting a single item, a range, or a discrete list of item codes (ideally with a product-category filter as well).
Honor full BOM explosion for the selected item(s): when MRP runs for a finished good or sub-assembly, it must cascade through the complete component tree at the correct low-level codes, so dependent demand on components and raw materials is regenerated accurately.
Provide the capability in both interactive (on-demand) and batch (scheduled) modes, and support both regenerative and net-change processing.
Preserve all existing planning parameters (reorder policy, lead times, safety stock, lot sizing, planning horizon) — this is a scoping change to the calculation, not a change to planning logic.
Safeguard shared components: because a selected component may also be consumed by parents outside the selection, the calculation should either (a) optionally pull in all where-used parents of in-scope components, or (b) clearly flag that requirements for shared components reflect only the selected scope. This prevents partial or misleading net requirements.
Guest
