How To Fix CONT_TOOLS507 - Check category ARL. Roles contain objects that do not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: CONT_TOOLS - Message for BI Content Tools German

• Message number: 507

• Message text: Check category ARL. Roles contain objects that do not exist

What causes this issue?

Objects of type 'role' have been found that reference BW objects that
are no longer in the system.
A BW object (query, template or view) has probably been assigned to the
role but then deleted again without being deleted from the role.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Use transaction PFCG in the "menu" tab page to check which BW elements
were assigned to the role.
You can display the details from the context menu. In the Object
Description field, you can find the technical name of the referencing
object, the query name for example.
You can use the object name to check whether the object exists.
Transaction RSRT for query elements or report RS_TEMPLATE_MAINTAIN for
templates might be of use for this.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CONT_TOOLS507 - Check category ARL. Roles contain objects that do not exist ?

  The SAP error message CONT_TOOLS507 indicates that there is an issue with the roles in the system, specifically that they contain objects that do not exist. This error typically arises during the process of role maintenance or when performing authorization checks.
  Cause:
  
  Missing Authorization Objects: The roles may reference authorization objects that have been deleted or do not exist in the system.
  Transport Issues: If roles were transported from one system to another, some objects may not have been transported correctly.
  System Upgrades: After an upgrade, some objects may become obsolete or may not be compatible with the new version.
  Custom Development: Custom authorization objects may have been removed or renamed, leading to inconsistencies in roles.
  
  Solution:
  
  
  Check Role Definitions: 
  
  Go to the role maintenance transaction (PFCG) and check the roles that are causing the error. Look for any missing authorization objects.
  
  
  
  Recreate Missing Objects: 
  
  If you identify that certain authorization objects are missing, you may need to recreate them or restore them from a backup.
  
  
  
  Transport Requests: 
  
  If the issue is due to transport, ensure that all necessary transport requests have been imported correctly into the target system.
  
  
  
  Role Comparison: 
  
  Use the role comparison feature in PFCG to compare the roles in the development and production systems to identify discrepancies.
  
  
  
  Check for Obsolete Objects: 
  
  Review the roles for any obsolete or deprecated authorization objects and remove or replace them as necessary.
  
  
  
  Authorization Trace: 
  
  Use transaction SU53 to analyze authorization failures and identify which objects are causing issues.
  
  
  
  Consult Documentation: 
  
  Review SAP notes and documentation related to the specific version of SAP you are using, as there may be known issues or patches available.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  PFCG (Role Maintenance)
  SU53 (Authorization Check)
  SUIM (User Information System)
  
  
  
  SAP Notes: 
  
  Check SAP Notes for any specific guidance or patches related to CONT_TOOLS507 or authorization object issues.
  
  
  
  Best Practices: 
  
  Regularly review and clean up roles and authorization objects to prevent such issues from arising.
  Maintain proper documentation of custom objects and their dependencies.
  
  
  
  By following these steps, you should be able to resolve the CONT_TOOLS507 error and ensure that your roles are correctly configured in SAP.