Show TOC

Procedure documentationInvalidating Objects in the Cache Locate this document in the navigation structure


The ICM server cache allows application programs to invalidate an object in all ICM server caches in the SAP system.

If an object has to be invalidated, all servers in the system must be notified by RFC that this object is no longer up to date and should be invalidated. The next time the object is requested, the up-to-date version of it must be re-loaded into each cache.

For a description of how to identify cache objects that have to be invalidated see the section on identifying objects.


You invalidate objects using method calls from the ABAP application (BSP application, HTTP request handler, and so on) or from the system (ICM monitor).

Invalidation Using ABAP Method Calls

To invalidate objects in the cache, you can use the following static methods of the CL_HTTP_SERVER class. You can call the methods from your application.


    Invalidates the object specified in the ICM Server Cache. This method has the following input parameters:

    ID of the object to be invalidated

    ID type

    Scope (local or global invalidation) Local means that the entry is invalidated in the ICM cache of the instance on which the method is called. Global means that the entry is invalidated for all instances of the SAP system.


    Invalidates a specified list of objects in the cache. The input parameters are a list of IDs and scope.


    Invalidates all objects in the ICM Server Cache.

Invalidation from the ICM Monitor

You can also invalidate individual entries or the entire cache from the ICM Monitor (transaction SMICM).