How To Fix 65635 - Security class cannot be archived because group cannot be archived

SAP Error Message - Details

• Message type: E = Error

• Message class: 65 - Securities class data

• Message number: 635

• Message text: Security class cannot be archived because group cannot be archived

What causes this issue?

The security class cannot be archived because the security group cannot
be archived. This is due to one of the following reasons:
The security class group contains a non-archivable security class.
The security class group is incomplete.
The end of the residence period for the security group is not reached.

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?

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 65635 - Security class cannot be archived because group cannot be archived ?

  The SAP error message 65635, which states "Security class cannot be archived because group cannot be archived," typically occurs in the context of archiving security-related objects in SAP, particularly when dealing with authorization objects and roles.
  Cause:
  This error arises when you attempt to archive a security class (such as a role or authorization object) that is still linked to a user group or has dependencies that prevent it from being archived. The underlying issue is that the associated user group has not been archived or is still in use, which violates the archiving prerequisites.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Dependencies: Identify the user group associated with the security class that you are trying to archive. You can do this by reviewing the configuration in transaction codes like PFCG (Role Maintenance) or SU01 (User Maintenance).
  
  
  Archive User Group: If the user group is no longer needed, you can archive it first. Use the appropriate archiving transaction (e.g., SARA for archiving) to archive the user group.
  
  
  Remove Dependencies: If the user group is still in use, you may need to remove any dependencies or references to the security class. This could involve:
  
  Reassigning users from the user group to another group.
  Deleting or modifying roles that reference the security class.
  
  
  
  Re-attempt Archiving: Once the user group is archived or the dependencies are resolved, you can attempt to archive the security class again.
  
  
  Check for Errors: After performing the above steps, if you still encounter issues, check the system logs or use transaction SLG1 to look for any additional error messages that might provide more context.
  
  
  Related Information:
  
  Archiving Process: Familiarize yourself with the archiving process in SAP, including the prerequisites and steps involved. The SAP Help Portal provides detailed documentation on archiving various objects.
  Authorization Management: Understanding how roles, profiles, and user groups work in SAP can help you manage security more effectively and avoid similar issues in the future.
  Transaction Codes: Key transaction codes related to this issue include:
  
  PFCG (Role Maintenance)
  SU01 (User Maintenance)
  SARA (Archive Administration)
  SLG1 (Application Log)
  
  
  
  By following these steps and understanding the underlying concepts, you should be able to resolve the error and successfully archive the security class.