How To Fix RSRCACHE035 - Cache settings for query modified

SAP Error Message - Details

• Message type: E = Error

• Message class: RSRCACHE - Messages for OLAP Cache

• Message number: 035

• Message text: Cache settings for query modified

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 RSRCACHE035 - Cache settings for query modified ?

  The SAP error message RSRCACHE035 indicates that the cache settings for a query have been modified. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when there are changes made to the query definition or its underlying data model.
  Cause:
  
  Query Modification: The most common cause is that the query has been changed in a way that affects its cache settings. This could include changes to the query structure, filters, or data sources.
  Data Model Changes: Changes in the underlying InfoProvider or data model that the query is based on can also trigger this error.
  Cache Invalidation: The cache may be invalidated due to updates in the data or metadata, requiring a refresh of the cache.
  
  Solution:
  
  
  Refresh the Cache: The simplest solution is to refresh the cache for the affected query. This can usually be done through the SAP BW or BI administration tools.
  
  Navigate to the relevant query in the BEx Query Designer or the SAP BW administration interface.
  Look for options to refresh or clear the cache.
  
  
  
  Check Query Settings: Review the query settings to ensure that they are correctly configured. If any changes were made, verify that they are intended and correctly implemented.
  
  
  Re-activate the Query: If the query has been modified, re-activating it in the BEx Query Designer can help resolve the issue.
  
  Open the query in the BEx Query Designer.
  Make a minor change (like adding and then removing a filter) and save the query to trigger a re-activation.
  
  
  
  Check for Data Source Changes: If the underlying data source has changed, ensure that the query is still compatible with the data model. You may need to adjust the query to align with the new data structure.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or updates that may address this specific error message. There may be patches or updates that can resolve known issues.
  
  
  Related Information:
  
  Caching Mechanism: SAP BW uses caching to improve performance by storing the results of queries. When a query is executed, the results are cached, and subsequent executions can retrieve results from the cache instead of reprocessing the data.
  Monitoring Tools: Use transaction codes like RSRT (Query Monitor) or RSRCACHE (Cache Management) to monitor and manage query caches.
  Performance Considerations: Regularly refreshing and managing query caches can help maintain optimal performance in SAP BW environments.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation, as they may have access to logs and additional tools to diagnose the problem.