Skip to main content
Question

PMRP and Standard Inventory Usage

  • November 18, 2025
  • 1 reply
  • 34 views
aberrant
Do Gooder (Customer)
Forum|alt.badge.img+2

Hello,

I’m looking for guidance on an issue I’m encountering with PMRP and the use of standard inventory.

I have a project configured to use standard inventory and to automatically generate MTRs. The parts involved are within their lead times, and I’ve confirmed that MTR creation should be possible. However, when I run PMRP by Activity for the entire project (leaving Activity Sequence blank), only one activity receives an MTR. The other three activities generate purchase requisitions instead—even though I know sufficient excess exists in standard inventory.

If I run PMRP on each activity individually, or if I use a Planned Netting Group, all activities generate the expected MTRs. This leads me to believe that when PMRP is executed for the full project, only the final activity processed is considered for standard inventory availability.

Has anyone experienced this behavior or know what configuration or process I might be overlooking?

Thank you.

Andrew

    1 reply

    T
    Do Gooder (Partner)
    Forum|alt.badge.img+7
    • TntAnnmaS
    • Do Gooder (Partner)
    • December 24, 2025

    PMRP is behaving as designed: when run for the whole project, it nets all activity demands together against surplus, so only one activity (usually the last/aggregated one) ends up with MTRs while earlier activities get PRs; when run per activity or PNG, the logic/sequence is different so each activity sees surplus and gets its own MTR. The “only last activity gets MTR from standard inventory” symptom is a known side‑effect of how PMRP does project‑wide netting.​

    Why this happens

    • PMRP with netting per project totals demand and supply across all activities for that project.​

    • When standard inventory surplus usage is enabled at project site, PMRP generates a standard‑inventory supply source (MTR from standard inventory) only for surplus beyond the sum of demands; how that surplus is allocated depends on run logic and sequence.​

    • In the reported behaviour, PMRP appears to assign the standard‑inventory MTR to the last activity processed and covers earlier activity demands via purchase requisitions instead of separate MTRs, even though you know there is enough standard inventory for all.​

    So when you run PMRP by Activity for the whole project (Activity blank), all activities are netted together and the surplus is effectively consumed by the last activity, whereas individual runs or a Planned Netting Group make each activity see the surplus independently and generate MTRs as expected.
     

    Practical ways to get consistent MTRs

    Given current behavior, these are the viable approaches:

    • Operational workaround

      • Continue to run PMRP per Activity (or by Planned Netting Group) for activities that must consume standard inventory via MTR instead of PR; this matches the behavior you already observe.​

    • Planning design

      • Group activities that should share standard inventory into a Planned Netting Group and run PMRP on that PNG only, which can improve how surplus is allocated compared with whole‑project runs.​

    • Escalate as behavior clarification/bug

      • Document the test case (same project, 4 activities, enough standard surplus, different outcomes for “full project” vs “per activity/PNG”) and log an IFS support case referencing this PMRP standard‑inventory behavior.​

      • Support can confirm whether your release has a known issue or if a configuration (e.g. netting option, lead‑time handling, activity sequence sort) can be adjusted so all eligible activities get MTRs when running PMRP by project.

    Terms & ConditionsCookie settingsAccessibility statement