How To Fix DDLS379 - SEARCHED CASE: Type information of default value is not correct

SAP Error Message - Details

• Message type: E = Error

• Message class: DDLS - For DDL source handling

• Message number: 379

• Message text: SEARCHED CASE: Type information of default value is not correct

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 DDLS379 - SEARCHED CASE: Type information of default value is not correct ?

  The SAP error message DDLS379, which states "SEARCHED CASE: Type information of default value is not correct," typically occurs during the activation or generation of database objects, such as tables or views, in the Data Dictionary (DDIC). This error indicates that there is a mismatch between the data type of a default value and the data type of the field it is assigned to.
  Cause:
  
  Type Mismatch: The default value assigned to a field does not match the data type of that field. For example, if a field is defined as an integer, but the default value is a string, this will trigger the error.
  Inconsistent Lengths: If the length of the default value exceeds the defined length of the field, it can also lead to this error.
  Invalid Default Value: The default value may not be valid for the specified data type (e.g., using a date format that is not recognized).
  Changes in Data Type: If the data type of a field has been changed after a default value was set, it may lead to inconsistencies.
  
  Solution:
  
  Check Field Definitions: Review the field definitions in the Data Dictionary (transaction SE11) to ensure that the data types and lengths are correctly defined.
  Verify Default Values: Go to the field where the default value is set and check the default value for correctness. Ensure that it matches the data type and length of the field.
  Adjust Default Values: If the default value is incorrect, modify it to match the field's data type. For example, if the field is of type CHAR(10), ensure the default value is a string of 10 characters or less.
  Re-activate Objects: After making the necessary changes, try to re-activate the database object (table/view) to see if the error persists.
  Check for Dependencies: If the field is part of a larger structure or table, ensure that all related objects are consistent and correctly defined.
  
  Related Information:
  
  Transaction Codes: Use SE11 (Data Dictionary) to check and modify table definitions, and SE14 (Database Utility) to manage database objects.
  Documentation: Refer to SAP Help documentation for detailed information on data types and their constraints.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis or ABAP development team for further assistance, as they may have additional insights or tools to diagnose the issue.