How To Fix DT672 - No access authorization or internal error

SAP Error Message - Details

• Message type: E = Error

• Message class: DT - Table activation (incl. indexes)

• Message number: 672

• Message text: No access authorization or internal error

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 DT672 - No access authorization or internal error ?

  The SAP error message DT672, which states "No access authorization or internal error," typically indicates that a user is attempting to access a resource or perform an action for which they do not have the necessary permissions. This error can arise in various contexts within SAP, such as during data retrieval, report generation, or transaction processing.
  Causes:
  
  Insufficient Authorizations: The user does not have the required roles or authorizations assigned to their user profile to access the specific transaction or data.
  Authorization Object Issues: There may be specific authorization objects that are not properly configured or assigned to the user.
  Internal Errors: There could be a system or configuration issue that is causing the error, such as a problem with the underlying data or a bug in the SAP system.
  User Profile Issues: The user profile may not be correctly set up, or there may be inconsistencies in the user master data.
  Transport Issues: If the error occurs after a recent transport, it may be due to missing authorizations that were not included in the transport.
  
  Solutions:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to analyze the authorization check. This will show which authorization objects failed.
  Review the user’s roles and profiles in transaction SU01 or PFCG to ensure they have the necessary permissions.
  
  
  
  Adjust Authorizations:
  
  If the user lacks the required authorizations, work with your SAP security team to assign the appropriate roles or modify existing roles to include the necessary authorizations.
  
  
  
  Review Authorization Objects:
  
  Identify the specific authorization objects that are causing the issue and ensure they are correctly configured in the roles assigned to the user.
  
  
  
  Check for Internal Errors:
  
  If the issue seems to be an internal error, check the SAP system logs (transaction SM21) for any related error messages or warnings that could provide more context.
  
  
  
  Consult SAP Notes:
  
  Search the SAP Support Portal for any relevant SAP Notes that might address known issues related to the error message DT672.
  
  
  
  System Configuration:
  
  If the error persists, it may be necessary to review system configuration settings or consult with SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  SM21: System Log
  
  
  SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP support for assistance, especially if it appears to be an internal error.
  
  By following these steps, you should be able to diagnose and resolve the DT672 error in SAP.