How To Fix PLM_SE_PRS_MESSAGES087 - Insufficient authorization to create milestone

SAP Error Message - Details

• Message type: E = Error

• Message class: PLM_SE_PRS_MESSAGES - Message class for PS services

• Message number: 087

• Message text: Insufficient authorization to create milestone

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message PLM_SE_PRS_MESSAGES087 - Insufficient authorization to create milestone ?

  The SAP error message PLM_SE_PRS_MESSAGES087 indicates that a user does not have sufficient authorization to create a milestone in the Project Management module of SAP. This error typically arises when a user attempts to perform an action that requires specific permissions that they do not possess.
  Cause:
  
  Authorization Issues: The user lacks the necessary roles or authorizations assigned to their user profile to create milestones.
  Role Configuration: The roles assigned to the user may not include the necessary transaction codes or object authorizations related to milestone creation.
  Project-Specific Restrictions: There may be restrictions or settings at the project level that prevent certain users from creating milestones.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction code SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that they include the necessary authorizations for project management and milestone creation.
  
  
  
  Review Authorization Objects:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization objects were checked and failed.
  Common authorization objects related to project management include:
  
  C_PROJ (Project Management)
  C_PRPS (Project Definition)
  
  
  Ensure that the user has the necessary authorizations for these objects.
  
  
  
  Role Adjustment:
  
  If the user lacks the necessary authorizations, work with your SAP security team to adjust the roles or create a new role that includes the required permissions.
  Ensure that the role is properly assigned to the user.
  
  
  
  Testing:
  
  After making changes to the user roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Attempt to create the milestone again to verify that the issue is resolved.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization's internal guidelines for specific authorization requirements related to project management and milestones.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder) and CJ02 (Change Project) to understand where milestones are created and managed.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance on authorization problems.
  User Training: Ensure that users are trained on the processes and requirements for creating milestones in SAP to minimize errors related to authorization.
  
  If the issue persists after following these steps, it may be necessary to engage with your SAP Basis or security team for further investigation.