How To Fix /PLMI/BO_RSP036 - You are not authorized to display the &1 of specification &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/BO_RSP -

• Message number: 036

• Message text: You are not authorized to display the &1 of specification &2

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 /PLMI/BO_RSP036 - You are not authorized to display the &1 of specification &2 ?

  The SAP error message /PLMI/BO_RSP036 indicates that a user does not have the necessary authorization to display a specific object or specification in the system. This error typically occurs in the context of SAP PLM (Product Lifecycle Management) or similar modules where access control is enforced.
  Cause:
  The error is caused by insufficient authorization for the user trying to access the specified object or specification. This can happen due to:
  
  Missing Authorization Roles: The user may not have the required roles assigned that grant access to the specific object type or specification.
  Authorization Object Restrictions: The authorization objects related to the specific transaction or data may not be properly configured for the user.
  Incorrect User Profile: The user profile may not be set up correctly, leading to restricted access.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the necessary roles for accessing the specific object or specification are included.
  
  
  
  Review Authorization Objects:
  
  Identify the relevant authorization objects that control access to the specifications in question. Common authorization objects in PLM include C_PROD (Product) and C_MAT (Material).
  Use transaction SU53 immediately after encountering the error to see which authorization checks failed. This will provide insight into what is missing.
  
  
  
  Modify Authorizations:
  
  If you have the necessary permissions, you can modify the user’s roles or create new roles that include the required authorizations.
  If you do not have the necessary permissions, contact your SAP security administrator to request the required access.
  
  
  
  Testing:
  
  After making changes to the user’s roles or authorizations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Documentation:
  
  Ensure that any changes made to user roles or authorizations are documented for future reference and compliance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  SU53 - Display Authorization Check
  PFCG - Role Maintenance
  
  
  Authorization Concepts: Familiarize yourself with SAP's authorization concept, including roles, profiles, and authorization objects.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorization in PLM or the specific object type you are working with.
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.