How To Fix RSMSS_ANALYZER_MSG008 - InfoCube E-Fact tables with missing indexes/obsolete index layout

SAP Error Message - Details

• Message type: E = Error

• Message class: RSMSS_ANALYZER_MSG - Messages for RSMSS_ANALYZER

• Message number: 008

• Message text: InfoCube E-Fact tables with missing indexes/obsolete index layout

Check description
This check looks for infocube E-Fact tables and compares existing
indexes with the indexes defined in the SAP standard of your current BW
release.
The check identifies:
Missing SAP standard indexes (including unique and clustered indexes)
Customer-created indexes that do not meet the SAP standard (that is, not
defined as data dictionary extension indexes)
SAP standard indexes based on a former BW release if they are different
to the standard of the current BW release.
Indexes that only exist on the database (without data dictionary
definition) are not found.
The findings are displayed as warning messages. It is not mandatory to
repair the index layouts, for example, after the upgrade of your system.
Repair description
With the repair option, the index layout of the selected E-Fact table is
adapted to the SAP standard. DDIC extension indexes and indexes that
only exist in the database remain unchanged.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSMSS_ANALYZER_MSG008 - InfoCube E-Fact tables with missing indexes/obsolete index layout ?

  The SAP error message RSMSS_ANALYZER_MSG008 indicates that there are issues with the InfoCube E-Fact tables, specifically that they are missing indexes or have an obsolete index layout. This can lead to performance issues when querying the InfoCube, as the database may not be able to efficiently access the data.
  
  Cause:
  
  Missing Indexes: This can occur if the indexes were not created during the InfoCube's initial setup or if they were inadvertently dropped or not maintained during updates.
  Obsolete Index Layout: This typically happens when the InfoCube structure has changed (e.g., after a data model change or after adding new characteristics) but the indexes have not been updated accordingly. This can lead to inefficiencies in data retrieval.
  
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check the Index Status:
  
  Use transaction code RSMO to check the status of the InfoCube and its indexes.
  You can also use transaction RSA1 to navigate to the InfoCube and check its