How To Fix CN502 - You do not have authorization to change milestone &1

CN502 - Overview

• Message type: E = Error

• Message class: CN - Meldungen für Netzpläne

• Message number: 502

• Message text: You do not have authorization to change milestone &1

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.

CN502 - Details

• The SAP error message CN502, which states "You do not have authorization to change milestone &1," typically occurs when a user attempts to modify a milestone in a project but lacks the necessary authorization to perform that action. This error is related to the authorization checks in the SAP system, specifically within the Project System (PS) module.
  
  Cause:
  
  Authorization Issues: The user does not have the required authorization object to change milestones in the project.
  Role Configuration: The user's role may not include the necessary permissions for the specific project or milestone.
  Project Status: The project or milestone may be in a status that restricts changes (e.g., locked or completed).
  Organizational Level Restrictions: The user may not have access to the organizational units associated with the project.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user's