How To Fix LCM_DOCUMENT105 - No authorization to delete document &1 with content type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: LCM_DOCUMENT - Message Class for LCM Document

• Message number: 105

• Message text: No authorization to delete document &1 with content type &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 LCM_DOCUMENT105 - No authorization to delete document &1 with content type &2 ?

  The SAP error message LCM_DOCUMENT105 indicates that a user does not have the necessary authorization to delete a document of a specific content type. This error typically arises in the context of document management systems within SAP, where users are expected to have specific permissions to perform actions on documents.
  Cause:
  The primary cause of this error is a lack of authorization for the user attempting to delete the document. This can happen due to:
  
  Missing Authorization Object: The user may not have the required authorization object that allows deletion of documents of the specified content type.
  Role Assignment: The user’s role may not include the necessary permissions for document deletion.
  Content Type Restrictions: Certain content types may have specific restrictions that prevent deletion unless certain conditions are met.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed.
  Review the user’s roles and authorizations in transaction PFCG to ensure that the necessary permissions are included.
  
  
  
  Modify Roles:
  
  If the user lacks the necessary authorizations, you may need to modify their roles or create a new role that includes the required authorization objects for document deletion.
  Common authorization objects related to document management include S_DOCUMENT, S_DOKU_AUTH, and others depending on your specific SAP configuration.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary access to change roles or authorizations, consult with your SAP security team or administrator to request the required permissions.
  
  
  
  Check Content Type Settings:
  
  Ensure that the content type in question allows for deletion. Some content types may have specific settings that restrict deletion based on status or other criteria.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, test the deletion process again to confirm that the issue has been resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control document management actions.
  SAP Documentation: Refer to SAP Help documentation for detailed information on authorization management and document handling.
  Transaction Codes:
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SCDO: Document Management System (DMS) settings
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to allow the user to delete the document successfully.