How To Fix /UI2/FDM_2_CDM3073 - Group Tile &1&2: Referenced catalog tile &3&4 not found.

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 073

• Message text: Group Tile &1&2: Referenced catalog tile &3&4 not found.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /UI2/FDM_2_CDM3073 - Group Tile &1&2: Referenced catalog tile &3&4 not found. ?

  The SAP error message /UI2/FDM_2_CDM3073 indicates that there is an issue with a group tile in the Fiori Launchpad. Specifically, it means that a referenced catalog tile is not found. This can occur for several reasons, and here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Catalog Tile: The referenced catalog tile (identified by &3&4 in the error message) does not exist in the system. This could be due to it being deleted or not properly created.
  Authorization Issues: The user may not have the necessary authorizations to access the catalog tile, leading to it being "invisible" to the user.
  Transport Issues: If the catalog tile was transported from another system, it may not have been included in the transport request or may not have been activated properly.
  Configuration Errors: There may be configuration issues in the Fiori Launchpad or the associated roles and catalogs.
  
  Solution:
  
  
  Check Catalog Tile Existence:
  
  Go to the Fiori Launchpad Designer or the SAP GUI and check if the catalog tile exists. If it does not, you may need to create it or restore it from a backup.
  
  
  
  Verify Authorizations:
  
  Ensure that the user has the necessary roles assigned that include access to the catalog tile. You can check this in the PFCG transaction by reviewing the roles assigned to the user.
  
  
  
  Transport Check:
  
  If the catalog tile was supposed to be transported, check the transport logs to ensure that it was included in the transport request and that it was successfully imported into the target system.
  
  
  
  Recreate or Adjust the Tile:
  
  If the tile is missing, you may need to recreate it. If it exists but is not functioning correctly, consider adjusting its configuration.
  
  
  
  Clear Cache:
  
  Sometimes, clearing the cache of the Fiori Launchpad can resolve issues related to missing tiles. You can do this by using the /UI2/FLP transaction and selecting the option to clear the cache.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest patches and updates, as there may be bug fixes related to Fiori Launchpad issues.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to Fiori Launchpad and the specific error message for any known issues or additional troubleshooting steps.
  Fiori Launchpad Designer: Familiarize yourself with the Fiori Launchpad Designer, as it is a key tool for managing tiles, catalogs, and groups.
  Documentation: Review the official SAP documentation for Fiori Launchpad configuration and troubleshooting.
  
  By following these steps, you should be able to identify and resolve the issue related to the error message /UI2/FDM_2_CDM3073.