How To Fix DDLS_HIER059 - Datatype for valid_to &1 is not as data type for period_to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: DDLS_HIER - Used for DDL Hierarchies

• Message number: 059

• Message text: Datatype for valid_to &1 is not as data type for period_to &2

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 DDLS_HIER059 - Datatype for valid_to &1 is not as data type for period_to &2 ?

  The SAP error message DDLS_HIER059 indicates a mismatch in data types between two fields, specifically valid_to and period_to. This error typically arises in the context of data modeling or when working with hierarchical data structures in SAP, such as when defining InfoObjects in SAP BW or when working with data definitions in ABAP Dictionary.
  
  Cause:
  The error occurs when the data type of the field valid_to does not match the expected data type of the field period_to. This can happen due to:
  
  Inconsistent Data Types: The two fields may have been defined with different data types in the underlying database or data model.
  Incorrect Field Mapping: During the creation or modification of a data model, the fields may have been incorrectly mapped or defined.
  Changes in Data Model: If there were recent changes to the data model or database schema, it could lead to inconsistencies.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Data