How To Fix GX725 - Authorization check: &1 records not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: GX - Archiving/Reorganization

• Message number: 725

• Message text: Authorization check: &1 records not allowed

What causes this issue?

&v1& records that met your selection criteria were refused due to
missing authorizations.

How to fix this error?

If you are running the evaluation online, execute transaction SU53.
Here you can see which authorizations are missing.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GX725 - Authorization check: &1 records not allowed ?

  The SAP error message GX725, which states "Authorization check: &1 records not allowed," typically indicates that a user is attempting to access or manipulate records for which they do not have the necessary authorizations. This error is related to the authorization checks that SAP performs to ensure that users can only access data they are permitted to.
  Cause:
  
  Insufficient Authorizations: The user does not have the required authorizations to view or modify the specified records. This could be due to missing roles or authorizations in their user profile.
  Authorization Object Restrictions: The authorization object associated with the transaction or report may have restrictions that prevent the user from accessing certain records.
  Data Restrictions: There may be specific data restrictions in place that limit access to certain records based on user roles or organizational units.
  
  Solution:
  
  Check User Roles: Verify that the user has the appropriate roles assigned that include the necessary authorizations for the transaction or report they are trying to access.
  Review Authorization Objects: Identify the relevant authorization objects that are being checked when the error occurs. This can be done using transaction SU53 (Display Authorization Check) immediately after the error occurs. This transaction shows the last authorization check and can help identify what is missing.
  Adjust Authorizations: If the user lacks the necessary authorizations, work with your SAP security team to adjust the user's roles or create new roles that include the required authorizations.
  Consult with Security Team: If you are not able to resolve the issue, consult with your SAP security team or administrator to review the authorization settings and make necessary adjustments.
  Testing: After making changes to the user’s authorizations, have the user log out and log back in to ensure that the changes take effect. Then, test the transaction again to see if the error persists.
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU01: User Maintenance - to check and modify user roles.
  SU53: Display Authorization Check - to analyze authorization failures.
  PFCG: Role Maintenance - to create or modify roles and authorizations.
  
  
  
  Authorization Objects: Common authorization objects that might be relevant include:
  
  S_USER_AUTH: User authorization checks.
  S_TABU_DIS: Table access authorization.
  S_DATASET: Authorization for file access.
  
  
  
  Documentation: Refer to SAP documentation or your organization's internal guidelines for managing user authorizations and roles.
  
  
  By following these steps, you should be able to identify the cause of the GX725 error and implement a solution to resolve it.