How To Fix /PLMI/DIR_BO055 - There is at least one document you have no authorization to display

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/DIR_BO -

• Message number: 055

• Message text: There is at least one document you have no authorization to display

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/DIR_BO055 - There is at least one document you have no authorization to display ?

  The SAP error message /PLMI/DIR_BO055 indicates that a user is attempting to access a document for which they do not have the necessary authorization. This can occur in various SAP modules, particularly in document management systems or when dealing with business objects.
  Cause:
  
  Authorization Issues: The user does not have the required authorization to view the specific document or documents. This could be due to missing roles or permissions in the user's profile.
  Document Status: The document may be in a status that restricts access (e.g., archived, deleted, or locked).
  Object-Specific Restrictions: There may be specific restrictions set on the document type or the folder in which the document is stored.
  User Group Restrictions: The document may be restricted to certain user groups, and the user does not belong to those groups.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization checks failed. This will provide insight into what specific authorizations are missing.
  Review the user's roles and authorizations in transaction PFCG to ensure they have the necessary permissions to access the document.
  
  
  
  Adjust Authorizations:
  
  If the user lacks the necessary authorizations, a security administrator can adjust the roles assigned to the user or create a new role that includes the required permissions.
  Ensure that the user is part of the correct user groups that have access to the document.
  
  
  
  Document Status Review:
  
  Check the status of the document to ensure it is not restricted. If it is archived or locked, you may need to change its status or provide the user with the necessary access.
  
  
  
  Consult Documentation:
  
  Review the documentation related to the specific SAP module or application you are using to understand the authorization requirements for accessing documents.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot determine the cause, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU53: Display authorization check.
  PFCG: Role maintenance.
  SE93: Transaction codes for authorization checks.
  
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to documents in your specific SAP environment.
  
  
  User Groups: Understand how user groups are configured in your organization and how they relate to document access.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve the authorization issue.