How To Fix ACM110 - Related PFCG_AUTH aspect &1 is still in use and cannot be deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: ACM - Message-Class for all ACM functions/exceptions

• Message number: 110

• Message text: Related PFCG_AUTH aspect &1 is still in use and cannot be deleted

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 ACM110 - Related PFCG_AUTH aspect &1 is still in use and cannot be deleted ?

  The SAP error message ACM110 indicates that a specific authorization aspect (in this case, related to PFCG - Profile Generator) is still in use and cannot be deleted. This typically occurs when you attempt to delete an authorization object or aspect that is still assigned to roles or users.
  Cause:
  
  Active Assignments: The authorization aspect you are trying to delete is still assigned to one or more roles or users in the system.
  Role Dependencies: The aspect may be linked to other roles or profiles that are currently active.
  Transport Requests: If the aspect is part of a transport request that has not been released or is still in use, it may prevent deletion.
  
  Solution:
  
  
  Check Assignments:
  
  Use transaction code PFCG to check which roles are using the authorization aspect. 
  Navigate to the role in question and check the "Authorizations" tab to see if the aspect is assigned.
  
  
  
  Remove Assignments:
  
  If you find that the aspect is assigned to roles, you will need to remove it from those roles before you can delete it.
  After removing the aspect from all roles, save your changes.
  
  
  
  Check for User Assignments:
  
  Use transaction code SU01 to check if any users are assigned the roles that contain the aspect.
  If users are assigned, you may need to remove the role from those users.
  
  
  
  Transport Requests:
  
  Check if the aspect is part of any transport requests. If it is, you may need to release the transport or remove the aspect from the transport request.
  
  
  
  Consistency Check:
  
  After making the necessary changes, you can run a consistency check using transaction SU25 to ensure that there are no inconsistencies in the authorization objects.
  
  
  
  Delete the Aspect:
  
  Once all assignments have been removed, you should be able to delete the authorization aspect without encountering the error.
  
  
  
  Related Information:
  
  PFCG (Profile Generator): This is the transaction used for role management in SAP. It allows you to create, modify, and delete roles and their associated authorizations.
  Authorization Objects: These are used to control access to various functions in SAP. Each object can have multiple fields that define the access level.
  User Management: Understanding how users are assigned roles and how roles are structured is crucial for managing authorizations effectively.
  
  If you continue to face issues after following these steps, it may be helpful to consult with your SAP Basis or Security team for further assistance.