How To Fix /IWFND/MED036 - Metadata cache (shared memory) was cleaned up by user '&1'

/IWFND/MED036 - Overview

• Message type: E = Error

• Message class: /IWFND/MED -

• Message number: 036

• Message text: Metadata cache (shared memory) was cleaned up by user '&1'

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.

/IWFND/MED036 - Details

• The SAP error message /IWFND/MED036 Metadata cache (shared memory) was cleaned up by user '&1' typically indicates that the metadata cache used by the SAP Gateway has been cleared or invalidated by a user. This can happen for various reasons, and understanding the cause and potential solutions can help in managing this error effectively.
  
  Cause:
  
  Manual Cleanup: A user with the necessary authorizations has manually cleared the metadata cache. This can be done through transaction codes like /IWFND/CACHE or through specific administrative actions.
  System Maintenance: Regular system maintenance or updates may involve clearing the cache to ensure that the latest metadata is loaded.
  Configuration Changes: Changes in the configuration of OData services or the underlying data model can trigger a cache invalidation.
  Performance Optimization: Sometimes, cache clearing is performed as a part of performance optimization efforts to ensure that the system is using the most current data.
  
  
  Solution:
  
  Repopulate the Cache: After the cache has been cleared,