Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix DT656 - Technical settings make no sense - > are not generated


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 656

  • Message text: Technical settings make no sense - > are not generated

  • Show details Hide details


  • 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 DT656 - Technical settings make no sense - > are not generated ?

    The SAP error message DT656 ("Technical settings make no sense - > are not generated") typically occurs during the process of generating database objects for a table or view in the Data Dictionary (DDIC). This error indicates that the technical settings defined for the table are inconsistent or invalid, preventing the generation of the necessary database objects.

    Causes:

    1. Invalid Technical Settings: The technical settings for the table (like data class, size category, buffering, etc.) may not be compatible with the table's structure or intended use.
    2. Missing or Incorrect Parameters: Certain parameters required for the technical settings might be missing or incorrectly defined.
    3. Database-Specific Constraints: The settings may not comply with the constraints or requirements of the underlying database system.
    4. Inconsistent Data Types: The data types defined for the fields in the table may not align with the technical settings.

    Solutions:

    1. Review Technical Settings:

      • Go to the Data Dictionary (transaction SE11) and check the technical settings of the table.
      • Ensure that the data class, size category, and buffering settings are appropriate for the table's intended use.
    2. Adjust Data Class and Size Category:

      • Make sure that the data class is suitable for the type of data being stored (e.g., master data, transaction data).
      • Verify that the size category is appropriate for the expected volume of data.
    3. Check Field Definitions:

      • Review the field definitions in the table to ensure that the data types and lengths are correctly defined and compatible with the technical settings.
    4. Consult Documentation:

      • Refer to SAP documentation or notes related to the specific version of SAP you are using for any known issues or additional guidance.
    5. Recreate the Table:

      • If the issue persists, consider recreating the table with the correct settings from scratch, ensuring that all parameters are correctly defined.
    6. Transport Requests:

      • If the table is part of a transport request, ensure that the transport is correctly configured and that there are no inconsistencies in the transport environment.

    Related Information:

    • Transaction Codes: SE11 (Data Dictionary), SE14 (Database Utility), SE14 (Table Maintenance).
    • SAP Notes: Check SAP Notes for any specific issues related to your version of SAP that might provide additional insights or patches.
    • Database Documentation: Review the documentation for the specific database you are using (e.g., HANA, Oracle, SQL Server) for any constraints or requirements regarding table definitions.

    If you continue to experience issues after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker