Skip to Content

The SAP Portal has several caches to speed up the portal experience and to minimize the impact of the portal on the Server (load time, database, PCD lookups, etc.). This has many benefits, but it complicates debugging for developers and support staff. There, you don`t want to see cached results, you need to get the actual changes.


When the user is accessing the portal for the 1st time, the browser loads all necessary files and caches them locally. 1st access with no cache:


With every subsequent access the browser loads content from the local cache. This speeds up the content loading time for the user.


To enforce your browser to actually load all the content from the portal, refresh the page with CTRL+F5.


As you will lose your navigation context and to be sure that no old content is on the computer, empty the local browser cache. In this cache the browser stores images, HTML and Javascript. To empty this cache:


The next caches are located on the portal side.

Portal Caches

The main portal caches are:

  • Navigation cache
  • PCD cache
  • Portal runtime cache
  • Database cache
  • UME cache
Navigation cache

The navigation cache is responsible for caching the navigation of the portal, starting from the “Entry Point” level. As it caches some navigation data like title, merge ID, sort priority: if you make a change to the navigation of the user, the change might not be immediately visible. To clear the Navigation cache:

System Administration -> Navigation


Clear the cache for the ROLES connector.

PRT cache

The content admin can enable portal content to be cached in the memory by the portal. This content will be stored in the portal runtime cache. This cache is actually storing iView content.


If this cache is enabled, the content is cached in the Portal Runtime cache. As an example, when the masthead application is configured to use the cache level: “Shared”, all the users will see the user name of the first user that accessed the portal. To clear the PRT cache:

http:// server:port /irj/servlet/prt/portal/prtroot/

PCD cache

The portal stores PCD content (roles, worksets structure, page structure). If you added, deleted or changed an iView and this change isn`t visible, clear this cache. To clear the PCD cache:

System Administration -> Support -> Support Desk -> Portal Content Directory -> PCD Administration


Database cache

The PCD object configuration is stored in the database of the portal. Because reading the configuration is a performance intensive task, the portal uses the DB cache to minimize to load on the DB. To enforce the portal to reload the configuration of the objects from the DB, clear the DB cache:

http:// server:port /irj/servlet/prt/portal/prtroot/

UME cache

The user assignments are stored in the UME. You should clear this cache when you assign an user to a new role and the navigation doesn`t get actualized and clearing the other caches isn`t solving the problem, or when you assign a security role to an user and isn`t getting the permissions. To clear this cache:

System Administration -> System Configuration -> UME Configuration -> Support -> Invalidate cluster wide cache


The next caches are independent from the portal. 

NetWeaver AS Java cache

After cleaning the above mentioned portal caches, there is still the possibility that the change isn`t applied for the end-user. The NetWeaver AS Java has a cache that stores static files.

HTTP Provider Cache

This is the cache for static files like CSS, Javascript, Images, HTML. You`ll have to clear this cache when you redeploy an application and receive Javascript errors. To clear this cache:

Visual Administrator -> Cluster -> Server # -> Services -> HTTP Provider


Reverse Proxy cache

Depending on your infrastructure, you may also have a reverse proxy between the portal and the user. If the changes won`t get applied, don`t forget to also clear this cache.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Vivek Nidhi
    Oflate I found that Portal theme is also cached.. even if we remove the theme from the portal desktop, it is still present there..we need to delete it from the physcial location on the server
  2. Former Member
    Hi Tobias,

    Thank you for providing this log on Portal cache.

    I am working as a portal consultant, and being part of SRM Portal implementation team. I want to know some basic concepts of ensuring portal perfomance with the bench mark,

    1.       Number of Concurrent Users : 300

    2.       Number of Transactions : 2000

    3.       Target Duration : 40 mins

    Please provide any blog/docs which will be useful for me to proceed in this case if you have.

    PS : SRM Business Package is imported into portal , connected with SRM server and standard rules(Operational Purchaser, Strategic Purchaser,..) added to the users.

    Thanks in advance.

    1. Former Member
      Hi Tobias,

      Indeed a great sharing. Thank you so much for sharing such small utility one but a great topic.
      All the best for all future sharings!


  3. Lukas Weigelt

    Thanks for this simple overview. I was about to clear the UME cache with a sledge hammer, but thanks to you this won’t be necessary anymore ๐Ÿ˜›


    Cheers, Lukas

  4. Former Member

    Very useful work tobias!!! Can you tell us what is the action for the “HTTP Provider Cache” procedure? maybe the explanation needs little bit to be complete.

  5. Arno Hagen

    Hi Tobias,

    is there a way to delete the PRT cache for one single iView?

    Could you let me know which permissions somebody needs to clear the cache via

    http:// server:port /irj/servlet/prt/portal/prtroot/

    when he is not an Admin or Super Admin?

    Thanks a lot!


  6. Former Member

    Hi Tobias,

    Thank You for great article. Could you clarify how I could best clear the cache which holds the ip address of a server. In the portal content we have a system (FBP) and that is assigned to a server alias (corpppdb). We do site switches here and after that switch the server alias refers to a different server / ip address. I would like to clear the cache so the portal picks up the new system details.

    Thanks for your help so far,


    1. Former Member Post author

      That kind of cache is at OS level. In Windows, you do a ipconfig /flushdnscache in CMD to clear the cache. Under Unix I believe a restart of your network stack should solve the problem.

  7. Former Member

    Wow thank you so much for this! I didn’t know you could clear the PCD cache that way. Most of the tickets I get deal with users collapsing their timesheet window and complain the window is missing or accidentally saved a bad template in ESS. A quick clear of their PCD resolves their problem in seconds ๐Ÿ™‚

  8. Former Member

    Hi Tobias,

    Will portal server restart (including DB), will clear all the above mentioned cache or will there still be some cache we have to clear individually/manually?



    1. Former Member Post author

      A portal restart will reset the caches. Restarting the portal is normally your last resort. Depending on your infrastructure this can take a while.

    1. Former Member


      Hello Eduardo,

      do you have any Problems while showing or changing a document from KM in aย  single_document_item of a web template? Is this the reason for your question?

      We have this problem and the solution was to restart the Portal (as Tobias said: the last Resort).

      But if there was a possibility to clean this ‘document’ (KM-) Cache….


      thanks, Peter

  9. Former Member

    Hi Tobias, We have CI + 5 java server. After importing an object we could see the portal link on java server however it is missing on few java server nodes. Will PCD cache release works to resolve the issue ? if so should I need to for each and every application java server ? Please check and provide suggestions.



    Sadanand D



Leave a Reply