Scribd
Upload
383 views

SAP Note:: 2043432 - Browser Cache Is Not Invalidated After

1. The document discusses cache management for SAP Fiori and provides steps to clear caches after a version or patch update. 2. Caches exist in the client, frontend server, and backend server layers. Clearing the browser cache, ICM server cache, metadata caches, and running specific reports clears caches across layers. 3. Key steps include clearing the http cache using transaction SMICM, metadata caches using transactions /IWFND/CACHE_CLEANUP and /IWBEP/CACHE_CLEANUP, and running reports like /UI2/INVALIDATE_GLOBAL_CACHES to clear UI2 caches.

Uploaded by

Vikky Rff
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
383 views

SAP Note:: 2043432 - Browser Cache Is Not Invalidated After

1. The document discusses cache management for SAP Fiori and provides steps to clear caches after a version or patch update. 2. Caches exist in the client, frontend server, and backend server layers. Clearing the browser cache, ICM server cache, metadata caches, and running specific reports clears caches across layers. 3. Key steps include clearing the http cache using transaction SMICM, metadata caches using transactions /IWFND/CACHE_CLEANUP and /IWBEP/CACHE_CLEANUP, and running reports like /UI2/INVALIDATE_GLOBAL_CACHES to clear UI2 caches.

Uploaded by

Vikky Rff
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

1.

SAP Note:
 2043432 - Browser cache is not invalidated after
version or patch update of SAP Fiori components
2. Activate the Cache Buster
http://help.sap.com/saphelp_scm700_ehp03/helpdata/en/1b/eb97
dba2d4414cb53ed656c0e8c70b/content.htm?
frameset=/en/9c/214a9eb00b4d7daf2d1ff36d446c1f/frameset.ht
m&current_toc=/en/bd/e12a271f0647e799b338574cda0808/plain
.htm&node_id=165

3. Steps
a. Transaction: /IWFND/CACHE_CLEANUP on Gateway
b. Transaction: /IWBEP/CACHE_CLEANUP on Backend and Gateway
c. Clear local browser cache
d. Run report /UI2/CHIP_SYNCHRONIZE_CACHE
e. Run report /UI2/DELETE_CACHE_AFTER_IMP
f. Optional: Run report /UI2/DELETE_CACHE
g. Optional: Run report /UI2/PAGE_CACHE_RESET
h. Run report /UI2/INVALIDATE_GLOBAL_CACHES
i. Run report /UI2/INVALIDATE_CLIENT_CACHES
j. Run report /UI5/APP_INDEX_CALCULATE
k. Run transaction SMICM -> HTTP Plug-In -> Server Cache -> Invalidate Locally
l. Run transaction SMICM -> HTTP Plug-In -> Server Cache -> Invalidate Globally

4. SAP Fiori - Cache Management: Clearing caches after


applying patches
created by Masayuki Sekihara on Jun 16, 2015 7:38 AM, last modified by Jeremy Good on Jun 16, 2015 5:18 PM
Version 2
This is a collaborative document to share lessons learned contents for SAP Fiori Cache Management topics in the
community SAP Fiori.
 
Please feel free to insert the link of your document or blog by selecting the edit button from Actions.
 
1. Challenges
 
After applying a support package or applying a note, clearing server side cache is required.
This document gives you an overview for understanding caches and the program names to clear caches manually.
 
2. Understanding the cache management
 
Caches are located in each layer (Client, Frontend Server and Backend Server)
 
3. Client
 
 Browser - No action is required. Please setup the Cache Buster.
o If clearing caches is required, you can manually clear the browser cache.
 Fiori Client - No action is required.
o When an app is updated on the server, Fiori Client automatically purges the existing cache and
pulls the update from the server.

o If clearing caches is required, you can manually clear the cache in the Setting -> Clear
Cache.http://help.sap.com/fiori-client
 
4. Frontend Server
 
 Cache Buster
o Cache Buster for SAP Fiori - SAP Fiori Launchpad - SAP Library
 ICM
o Transaction: SMICM  Menu, Goto -> HTTP Plug-in -> Server Cache -> Invalidate Globally
o ICM Server Cache - Internet Communication Manager (ICM) - SAP NetWeaver - SAP Library
 UI2
o Report: /UI2/INVALIDATE_GLOBAL_CACHES. This clears caches for Fiori launchpad and
other UI tools.

 Metadata
o Transaction: /IWFND/CACHE_CLEANUP. This clears the OData metadata cache.
 
 
5. Backend Server
 
 Matadata
o Transaction: /IWBEP/CACHE_CLEANUP. This clears the OData metadata cache.

There are various modules involved in Fiori development and we need to make sure that cache in all
these components have been cleared to avoid to any issues.

1. 1.Clear the server http cache


Go to the transaction SMICM. Goto -> HTTP plugin -> Server cache -> Invalidate Locally and Globally.
1. 2. Clear metadata cache
Transaction: /IWFND/CACHE_CLEANUP on Gateway (oData cache clearing)
Transaction: /IWBEP/CACHE_CLEANUP on Backend and Gateway (oData cache clearing)
1. 3. Synchronize chip cache
Run the report /UI2/CHIP_SYNCHRONIZE_CACHE. Make sure there is no error in the table
/UI2/CHIP_CHDR
Run the report /UI2/DELETE_CACHE_AFTER_IMP.
/UI2/DELETE_CACHE
1. 4. Run cache buster
Run the report /UI5/UPDATE_CACHEBUSTER.
1. 5. Clear local browser cache - to avoid views and resources being displayed from local browser
cache or else implement cache buster
     1.6  UI2 Cache
     Run report /UI2/INVALIDATE_GLOBAL_CACHES. This cache clearing is mandatory especially to
verify the translations integrated for ex tiles,groups,catalogs in Launchpad admin
     1.7 Fiori client app is capable of handling local cache whenever new resources are available in the
server so no need of manual cache management implementation 

 
Please make sure that you follow all above cache maintenance techniques wherever and whenever
required.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy