How To Fix SEPMH_DG073 - Field '&1' is not of type Decimal - attribute rule does not apply

SEPMH_DG073 - Overview

• Message type: E = Error

• Message class: SEPMH_DG - EPM HANA DG - Messages

• Message number: 073

• Message text: Field '&1' is not of type Decimal - attribute rule does not apply

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.

SEPMH_DG073 - Details

• The SAP error message SEPMH_DG073, which states "Field '&1' is not of type Decimal - attribute rule does not apply," typically occurs in the context of SAP applications that involve data modeling or data transformation, particularly when working with attribute rules in the SAP HANA environment or SAP BW (Business Warehouse).
  
  Cause:
  This error indicates that there is an attempt to apply an attribute rule to a field that is not of the expected data type (Decimal). The specific reasons for this error can include:
  
  Data Type Mismatch: The field referenced in the error message is expected to be of type Decimal, but it is defined as a different data type (e.g., Integer, String, etc.).
  Incorrect Configuration: The attribute rule may have been configured incorrectly, pointing to the wrong field or expecting a different data type.
  Modeling Errors: There may be issues in the data model where the field's data type was not set correctly