Hi all,
The IFS Cloud documentation for Project MRP (About PMRP) gives this netting hierarchy:
- Within the demand activity
- Within valid project netting groups
- Standard inventory
I’m seeing PMRP results that don’t seem to follow step 1, and I’d like to understand how the netting actually works.
Scenario (one project, one site, PMRP run with project-level netting / project PNG)
| Activity | Demand | Supply | Date |
|---|---|---|---|
| WF0 | none | 7 pcs on hand in project inventory (surplus) | Available now |
| WF1 | Material Req 10 | Released PO line 1: 10 | 19/02/2027 |
| WF4 | Material Req 10 | Released PO line 2: 10 | Demand 20/05/2027, PO 19/05/2027 |
WF1 and WF4 are each already balanced by their own PO line. The only excess is the 7 on hand at WF0.
PMRP result (Inventory Part Availability Planning)
- Planned MTR: WF0 → WF1, qty 7, due 19/02/2027
- Planned MTR: WF1 → WF4, qty 7, due 20/05/2027
So PMRP moves the WF0 stock into WF1, which pushes 7 of WF1’s own PO quantity into surplus, and then plans a second MTR to move that surplus on to WF4.
Questions
- If netting is “within the demand activity” first, why isn’t WF1’s demand covered by WF1’s own PO before PMRP looks at WF0’s stock?
- Does PMRP actually net at project/PNG level in date order (earliest supply to earliest demand, regardless of activity) and then create MTRs to rebalance between activities? If so, what does “within the demand activity” mean in practice?
- Does pegging or reservation status matter here? The PO lines show Pegged = 0. Would pegging the PO line to the activity demand change the result?
- Is this the expected design, or a defect? If it’s expected, what’s the recommended setup to get a single MTR (or none) when activities are already balanced? The options I know of are per-activity PMRP, “Generate MTR for Planning Only” on the PNG, and Excluded Parts.
- Second test: I increased WF4’s demand from 10 to 17, so after its own PO line there is a real shortage of 7 at WF4. Following the documented hierarchy, I expected a single MTR from WF0 to WF4 for 7. Instead, PMRP again created two MTRs: WF0 → WF1 for 7 (due 19/02/2027) and WF1 → WF4 for 7 (due 20/05/2027), even though WF1 is fully covered by its own PO. Why doesn’t PMRP transfer WF0’s surplus straight to the activity that’s short?
Version: 26R1
Thanks in advance.