Transport of Copies (TOC)

All the object related to one development should be saved in one request, Eg. A development is having program, table, fields, view, structure etc… All these objects are the part of one development so they have to be in one request. If by mistake you have saved one object in different request then you have the option of merging that separated objects task into the main request through SE09.. Another option is to create a TOC and include both the tasks into that TOC.. But one should have a good practice of keeping the related objects of one development into one request..  TOC should not be used for merging the request for avoiding such mistakes.

The beauty with Transport of Copy is, it dies in the next target system. Let's say I have three system landscape for my ECC system: DA1 -> QA1 -> PA1. If you create a workbench request in DA1 system and release it, it goes to import buffer of QA1. Once imported in QA1, transport is now available in the import buffer of PA1 for import in PA1. But, if you create a Transport of Copy for the same transport in DA1 and release it, it will be in import queue of QA1. However, when you import this transport to QA1 it does not go to the import buffer of PA1. 

Clear SAP Fiori Cache

A step by step guide to clear SAP Fiori Cache.

First a quick introduction to SAP Fiori Caching...

Why does SAP Fiori use caching techniques?
The SAP Fiori is used in consumer devices (Laptops/Tablets/Smartphones) where the UI/UX standards are very high.  It has a modern User Interface build on SAPUI5, and for performance SAP Fiori is using heavily caching techniques, in order to be as fast as possible to end users.



Keep in mind that in most cases SAP Fiori is installed on premise, using company's network infrastructure which many times suffers from network latencies, especially in complex and distributed landscapes.

In order to overcome these problems SAP Fiori has the following Cache Layers:

• SAP Backend System Cache - Usually OData Services related cache
• SAP Netweaver Gateway Cache - OData Services, Bsp App and Fiori Configuration Caches
• SAP Web Dispatcher Cache - HTML,CSS and JS Code cache
• SAP Fiori Client/ Web browser Cache - Cache of the end user's device

When should I clear SAP Fiori Cache?
Usually SAP Fiori cache should be cleared when a change has been made in its configuration, in OData Service, in a Fiori BSP App, in a Theme or when you are applying patches/notes. Also when you are facing strange issues with SAP Fiori, a good point to start the troubleshooting  is by clearing the SAP Fiori Cache.

Steps to clear the SAP Fiori Cache...

Step 1. Clear backend Cache
Execute TCODE /IWBEP/CACHE_CLEANUP for each of your backend systems (SAP ERP,CRM etc)
Select check box "Cleanup Cache in all models"

Step 2. Clear SAP Gateway Cache

2.1 Rebuild the custom theme  and clear the theme cache if something related to the theme has changed or the system has been patched:

• Rebuild theme using by accessing your theme designer in the SAP Gateway URL. The URL is:
  https://<Your GW Server Host:Port>/sap/bc/theming/theme-designer/
  Select the custom theme and click rebuild.

• Clear the Fiori Theme Cache by executing in your SAP Gateway system TCODE /ui5/theme_tool. Double click on the [Invalidate Cache] button.  

2.2 Execute TCODE /IWBEP/CACHE_CLEANUP  in the SAP Gateway

Select check box "Cleanup Cache in all models"

2.3 Execute TCODE /IWFND/CACHE_CLEANUP in the SAP Gateway

2.4 Execute TCODE SE38 in the SAP Gateway and run the following reports:

• /UI2/INVALIDATE_GLOBAL_CACHES - Select Execution mode 
• /UI2/CHIP_SYNCHRONIZE_CACHE
• /UI2/DELETE_CACHE_AFTER_IMP
• /UI2/INVALIDATE_CLIENT_CACHES - Select For All users
• /UI5/UPDATE_CACHEBUSTER

2.5 Execute TCODE  SMICM.  On the Menu select Goto - HTTP Plug-in - Server Cache -Invalidate Globally

Step 3. Clear the Reverse Proxy Cache (if exists)
You should clear you Reverse Proxy Cache. Usually this is an SAP Web Dispatcher but other products could be used as well.

Step 4. Clear the Client Caches
If SAPUI5 Cachebuster has been set up correctly then no further action is needed. In other cases you should clear manually the web browser cache or the fiori client app cache.


References:
http://scn.sap.com/docs/DOC-64731