How To Fix DT120 - No authorization for requested DB change to table &

DT120 - Overview

• Message type: E = Error

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

• Message number: 120

• Message text: No authorization for requested DB change to table &

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.

DT120 - Details

• The SAP error message DT120 indicates that a user does not have the necessary authorization to perform a database change on a specific table. This error typically arises when a user attempts to execute a transaction or program that requires access to modify data in a database table, but their user profile lacks the required permissions.
  
  Cause:
  
  Insufficient Authorizations: The user does not have the necessary authorizations assigned to their user role to perform the requested action on the specified database table.
  Table Locking: The table may be locked for changes due to ongoing transactions or maintenance activities.
  Transport Layer Restrictions: If the change is being made in a transport layer that restricts certain operations, this could also lead to the error.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to analyze the authorization check. This will show which authorization object failed.
  Review the user’s roles and profiles in transaction SU01 or PFCG