How To Fix RSIM036 - Incorrect index on E fact table

SAP Error Message - Details

• Message type: E = Error

• Message class: RSIM - Messages for BI KPI monitoring and Health Checks

• Message number: 036

• Message text: Incorrect index on E fact table

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 RSIM036 - Incorrect index on E fact table ?

  The SAP error message RSIM036, which indicates "Incorrect index on E fact table," typically arises in the context of SAP BW (Business Warehouse) when there are issues with the indexes of the fact tables in the InfoCube. This can lead to problems in reporting and data retrieval.
  Causes:
  
  Index Corruption: The indexes on the fact table may be corrupted or not properly maintained.
  Data Load Issues: If there were issues during data loading (e.g., incomplete loads, errors during extraction), it could lead to inconsistencies in the indexes.
  Changes in Data Model: If there have been changes to the data model (like adding or removing characteristics), the existing indexes may no longer be valid.
  Database Issues: Underlying database issues or inconsistencies can also lead to this error.
  
  Solutions:
  
  
  Rebuild Indexes:
  
  You can rebuild the indexes for the affected InfoCube. This can often resolve issues related to index corruption.
  Use transaction RSA1 to navigate to the InfoCube, and then use the "Manage" option to rebuild the indexes.
  
  
  
  Check Data Load:
  
  Review the data load process to ensure that there are no errors or incomplete loads. If necessary, re-extract and load the data.
  
  
  
  Activate the InfoCube:
  
  Sometimes, simply reactivating the InfoCube can help. This can be done in the Data Warehousing Workbench (transaction RSA1).
  
  
  
  Check for Consistency:
  
  Use the transaction RSMO to check the consistency of the InfoCube and resolve any inconsistencies found.
  
  
  
  Database Maintenance:
  
  If the issue persists, consider performing database maintenance tasks, such as updating statistics or checking for database integrity issues.
  
  
  
  SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  RSA1: Data Warehousing Workbench
  RSMO: Monitor Data Loads
  RSCUSTV10: Customizing for BW
  
  
  
  Documentation: Refer to SAP Help documentation for more details on InfoCubes and index management.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.