3664234 - SAP Fiori Catalogs missing after Post Copy or Refresh (Homogenous System Copy)

Regarding this KBA please consider following general aspects of PCA: 

As part of the life cycle of an SAP solution, customers usually refresh existing test systems with data from a source system (System Refresh) or build up new systems (System Copy). Usually, the source system is a productive system and target system is a quality system.

In this context PCA (Post Copy Automation) is used to retain the system specific technical configuration of the target system by a standardized approach. PCA mainly rescues table content of the target system.

This means before system refresh table content of target system will be exported and after system refresh exactly the same table content will be imported in the target system.

Key facts:

• Basically, for System Refresh there are 2 possible options:

1. Retain the configuration from Target à (Select the desired Export/Import Tasks) à as a result the configuration looks like before the System Refresh
2. Retain the configuration from Source à (De-Select the desired Export/Import Tasks) à the configuration remains from the source system after the System Refresh

• For each PCA Export/Import task a pre-defined set of tables will be exported/imported; PCA always exports/imports the whole table content, no selective export/Import
• PCA must not be used/performed on the Source System
• PCA is not a transport tool. This means PCA must not be used to transport objects from one system to another

The 'Symptom' section of the following KBA assumes a system refresh of a Dev system using a Sandbox system. This does not represent a common system refresh scenario. Instead, a typical system refresh scenario consists of refreshing a QA system from a production system.

For further details about PCA, please refer to the PCA Summary Note 1614266.

• Let the following be true:
  • A Sandbox system has 2000 catalogs was requested to do a Post Copy or Refresh to a Development System (Used: Homogenous System Copy)
  • After the Refresh, the Development System has much less catalogs (ex: 300)
• Development and configuration in Fiori is put on halt as there are missing catalogs

• Key indicators:

  • Expected catalog count does not match actual catalog count after system copy
  • Target system maintains its original catalog structure rather than adopting source system catalogs
  • Missing catalogs that were present in the source system

S/4HANA Cloud Private Edition - all versions.

Refresh missing Fiori catalogs, System Copy Missing Fiori Catalogs, Homogenous System Copy Catalogs, Missing Catalogs Fiori, Fiori target system has less catalogs, System Copy from System A to System Be started to have missing catalogs, Fiori Missing Catalogs , KBA , PCO-OPS , ECS TechOps Servicedesk , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , Problem