How To Fix /PLMI/CR_BO005 - You are not authorized to create change records

/PLMI/CR_BO005 - Overview

• Message type: E = Error

• Message class: /PLMI/CR_BO -

• Message number: 005

• Message text: You are not authorized to create change records

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.

/PLMI/CR_BO005 - Details

• The SAP error message /PLMI/CR_BO005 indicates that a user is not authorized to create change records in the system. This typically occurs in the context of SAP's Change Request Management (ChaRM) or similar functionalities where specific authorizations are required to perform certain actions.
  
  Cause:
  
  Authorization Issues: The user does not have the necessary authorizations assigned to their user profile to create change records.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for the specific transaction or action they are trying to perform.
  Missing Authorization Objects: The required authorization objects for creating change records may not be included in the user's roles.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which specific authorization is missing.
  
  
  
  Review User Roles:
  
  Go to transaction SU01 to view the user’s profile and check the roles assigned to the user.
  Ensure that the