Skip to Content

MRP Controller defined at person level


My client is using projects with WBS elements and networks. They want security to prevent project managers to be able to edit another project manager’s project. At WBS element level, Person Responsible can be used for this. However, unfortunately, WBS element security is not inherited to network level, and another object needs to be used. We’ve thought of using MRP Controller for this, defining as many as project managers. I was advised that defining MRP Controller at person level isn’t really recommended by SAP, because it implies changing customizing every time a new project manager is incorporated.

Do you think is this a bad practice? Is there any workaround to address this issue? We are trying to avoid implementing ACL for this (which we know could help with the problem). Any suggestions?

Thanks in advance!


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • May 08 at 01:35 PM

    PS ACL is specifically designed to do what you are asking.

    Using MRP Controller or Person Responsible for this doesn't sound like a good solution. Neither of these fields are designed to control access to project objects. You will need to create authorization customization.

    What's wrong with ACL?

    Add comment
    10|10000 characters needed characters exceeded

  • May 08 at 04:03 PM

    As Ken Said ACL is the right option. I don't know what constraints you are facing with ACL.

    You can refer my below blog to restrict user on PS Objects


    Akash Khandelwal

    Add comment
    10|10000 characters needed characters exceeded