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 set up correctly, leading to no data being available for the calculation.
  
  Solution:
  
  Check Source Data: Verify that there is data in the source system for the relevant time period and selection criteria. You can do this by running a query directly against the source tables.
  Review Selection Criteria: Ensure that the selection criteria used in the data extraction process are correct and that they match the data available in the source.
  Data Compression: If the data has been compressed, check the compression settings and ensure that the data is available in the compressed state. You may need to decompress the data if necessary.
  Monitor Data Load Processes: Check the data load processes in the SAP BW system to ensure that they have completed successfully and that there are no errors or warnings.
  Check InfoProvider Configuration: Review the configuration of the InfoProvider (InfoCube or DSO) to ensure that it is set up correctly and that it is able to receive and store data as expected.
  Run Data Consistency Checks: Use transaction codes like RSA1 to check for data consistency and to identify any issues with the data model.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like RSA1 (Data Warehousing Workbench), RSMO (Monitor Data Load), and RSPC (Process Chain Maintenance) to monitor and manage data loads.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP BW documentation for best practices on data extraction and loading processes.
  Support: If the issue persists, consider reaching out to SAP support for further assistance, providing them with detailed logs and error messages.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.