How To Fix EEDM_CALC_INST136 - No data found for calculation in compressed trigger

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDM_CALC_INST - IS-U: EDM Messages for Calculating Formula Instances

• Message number: 136

• Message text: No data found for calculation in compressed trigger

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 EEDM_CALC_INST136 - No data found for calculation in compressed trigger ?

  The SAP error message EEDM_CALC_INST136 indicates that there is no data found for a calculation in a compressed trigger. This typically occurs in the context of SAP Data Warehousing or SAP BW (Business Warehouse) when dealing with data extraction, transformation, and loading (ETL) processes.
  
  Cause:
  
  No Data in Source: The most common cause is that there is no data available in the source system for the specific time period or criteria being queried.
  Incorrect Selection Criteria: The selection criteria defined in the data extraction process may not match any records in the source.
  Data Compression Issues: If the data has been compressed in the InfoCube or DataStore Object (DSO), it may lead to situations where the expected data is not available for the calculation.
  Data Load Issues: There may have been issues during the data load process that resulted in missing data.
  Incorrect Configuration: The configuration of the InfoProvider or the data flow may not be