How To Fix DT679 - Technical settings could not be written

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 679

• Message text: Technical settings could not be written

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 DT679 - Technical settings could not be written ?

  The SAP error message DT679, which states "Technical settings could not be written," typically occurs during the process of defining or modifying the technical settings of a database table in the Data Dictionary (SE11). This error can arise due to various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to make changes to the technical settings of the table.
  Database Lock: The database might be locked due to another process or transaction that is currently using the table.
  Inconsistent Data Dictionary: There may be inconsistencies in the Data Dictionary that prevent the changes from being saved.
  Transport Issues: If the changes are being transported from one system to another, there may be issues with the transport request.
  Database Constraints: There may be constraints or dependencies in the database that prevent the changes from being applied.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to modify the technical settings. This can be done by checking the user's roles and authorizations in transaction SU53 or SU01.
  Release Locks: If the table is locked, identify the process that is holding the lock and release it. You can use transaction SM12 to check for and delete any locks.
  Consistency Check: Run a consistency check on the Data Dictionary using transaction SE11 or SE14 to identify and resolve any inconsistencies.
  Transport Request: If the changes are part of a transport request, ensure that the request is correctly released and that there are no issues with the transport system.
  Database Administration: Consult with your database administrator to check for any database-level constraints or issues that may be preventing the changes.
  
  Related Information:
  
  
  Transaction Codes:
  
  SE11: Data Dictionary (to view and modify table definitions).
  SE14: Database Utility (to perform database-related operations).
  SM12: Display and Delete Locks (to check for locks on database objects).
  SU53: Authorization Check (to analyze authorization issues).
  
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  System Logs: Review the system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.