Hi ​@Sumedha,

If I understand the logic correctly here this should be the reason:

MS does not look at project-specific demands unless you run it for the project and set the supply option to PMRP.

If the supply option is set to MRP, but the part is defined as a Master Scheduled (MS Level 1) part as well, MRP ignores it (because the system expects the demand to flow through MS for supply generation since you have defined it as a MS part), and MS also ignores it (because it's a project demand). This creates a conflict Therefore, both planning engines do not pick up the demand. 

Hi Yathartha,

Thank you for the reply. You understood the problem correctly. However, I think MS should at least give a message to user from either of planning tools that this set up does not generate any supplies despite you can see the misc demand in the IPAP. It seems like IFS do not have a solution currently for this scenario where the finish goods are planned by MS and demands are raised through any project. If we are to use PMRP, it consider only the MS connected project PNG but not all.

Best Regards,

Sumedha

Hi ​@Sumedha,

Having some form of user feedback or warning in such cases would certainly improve usability and prevent confusion.

It may be worth raising this as an idea. It is a good enhancement request to be considered in future releases.

Thank you for the reply..!

Hi Sumedha and Yathartha,

I agree, it would be good to be able to load MS Level 1 with demand from Project Misc Demand - standard planned items. Since we are talking a new demand source, it should not be a huge amount of implementation hours to get that into Core. (It is often more tricky when adding a new open supply source)

Cheers,

Mats at RnD

Thanks Mats for looking into this. I will create an idea.

Hi Mats,

I noted one more issue with regards to MRP where it does not creates demands against Request work tasks. If this is not a potential bug in the system, may I know the reason to exclude that please?