We have a project where the users sometimes run PMRP per Project PNG and sometimes PMRP for a specific activity. We have a problem to understand the logic regarding MTRs and how they are taken into consideration in these two PMRP jobs.
Activity 1: Demand for 1 pc of Part A. No supply orders or On Hand Qty of Part A within activity 1.
Activity 2: No demand for Part A. Started Shop Order Part A, lot size 1.
- They run “Perform PMRP per project PNG”
Result:
- MTR (connected to the started supply SO) is created to transfer Part A from activity 2 to activity 1.
- No SO Req for Part A created in Activity 1 as the demand will be covered by the MTR.
So far so good..
But then, a couple of days later:
- They run “Perform Project MRP per Activity” for Activity 1.
Result:
- The MTR to transfer Part A from activity 2 to activity 1 is kept (not deleted by the PMRP per activity)
- AND a SO requisition for part A is created in activity 1
So the result is we have supply for Part A from a SO Req and also a MTR. We are aware that “Perform Project MRP per Activity” will not do netting between activities but if the MTR is not deleted by the PMRP why is it not counted as a supply in this case?
If we run “Perform PMRP per project PNG” again we will get the same result as in step 1, in other words a MTR will be the supply for the demand in Activity 1 and no SO Req will be created.
Hope someone can help us understand the PMRP logic in this case.
And for information, they will start using “manual” PNGs for each sub projects to avoid netting between activities in different subprojects. So PMRP per activity will be used much less frequently in the future.
IFS Cloud 24.2.14
