How To Fix RSSDA028 - Data type DECIMAL of field &1 is not supported in CalcScenario

SAP Error Message - Details

• Message type: E = Error

• Message class: RSSDA - BW HANA Smart Data Access

• Message number: 028

• Message text: Data type DECIMAL of field &1 is not supported in CalcScenario

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 RSSDA028 - Data type DECIMAL of field &1 is not supported in CalcScenario ?

  The SAP error message RSSDA028 indicates that there is an issue with the data type of a field in a calculation scenario. Specifically, it states that the DECIMAL data type is not supported in the context of the calculation scenario you are working with. This can occur in various SAP modules, particularly in SAP BW (Business Warehouse) or SAP HANA environments where calculation scenarios are defined.
  Cause:
  
  Unsupported Data Type: The primary cause of this error is that the DECIMAL data type is not compatible with the calculation scenario you are trying to use. Calculation scenarios often have restrictions on the types of data they can process.
  Field Definition: The field in question (denoted as &1 in the error message) is defined as DECIMAL in the data model, but the calculation scenario expects a different data type (e.g., INTEGER, FLOAT, etc.).
  Modeling Issues: There may be issues in the data modeling or transformation processes that lead to the use of DECIMAL fields in contexts where they are not allowed.
  
  Solution:
  
  Change Data Type: If possible, change the data type of the field from DECIMAL to a supported type (like INTEGER or FLOAT) in the underlying data model or InfoObject definition. This may involve modifying the data source or the transformation logic.
  Adjust Calculation Logic: If changing the data type is not feasible, consider adjusting the calculation logic to avoid using DECIMAL fields. This might involve creating a new calculated field that converts the DECIMAL value to a supported type.
  Review Calculation Scenario: Check the definition of the calculation scenario to ensure that it is set up correctly and that it is compatible with the data types being used. You may need to consult the documentation for the specific SAP module you are working with to understand the supported data types.
  Consult SAP Notes: Look for any relevant SAP Notes or documentation that may provide additional guidance or updates regarding this error message. SAP frequently updates its software, and there may be patches or notes that address this issue.
  
  Related Information:
  
  SAP Documentation: Review the official SAP documentation for the specific module you are using (e.g., SAP BW, SAP HANA) to understand the supported data types and best practices for defining calculation scenarios.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Testing: After making changes, thoroughly test the calculation scenario to ensure that it functions as expected and that the data integrity is maintained.
  
  By addressing the data type issue and ensuring compatibility with the calculation scenario, you should be able to resolve the RSSDA028 error.