How To Fix /UI2/FDM_2_CDM3060 - Catalog &1&2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 060

• Message text: Catalog &1&2 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_CDM3060 - Catalog &1&2 not found ?

  The SAP error message /UI2/FDM_2_CDM3060 Catalog &1&2 not found typically indicates that the system is unable to locate a specific catalog in the Fiori Launchpad or the associated configuration. This error can occur for various reasons, including missing or incorrectly configured catalogs, issues with the transport of Fiori content, or problems with the user roles and authorizations.
  Causes:
  
  Missing Catalog: The specified catalog does not exist in the system.
  Incorrect Catalog ID: The catalog ID referenced in the error message may be incorrect or misspelled.
  Transport Issues: If the catalog was recently transported from another system, it may not have been transported correctly.
  Authorization Issues: The user may not have the necessary authorizations to access the catalog.
  Configuration Issues: The Fiori Launchpad configuration may not be set up correctly.
  
  Solutions:
  
  
  Check Catalog Existence:
  
  Go to the Fiori Launchpad Designer or the relevant transaction (e.g., /UI2/FLP) and verify if the catalog exists.
  If it does not exist, you may need to create it or transport it from another system.
  
  
  
  Verify Catalog ID:
  
  Ensure that the catalog ID referenced in the error message is correct. Check for any typos or discrepancies.
  
  
  
  Transport the Catalog:
  
  If the catalog is missing due to transport issues, ensure that the transport request containing the catalog has been released and imported into the target system.
  
  
  
  Check User Roles and Authorizations:
  
  Ensure that the user has the necessary roles assigned that include access to the catalog. You can check this in the user profile or by using transaction PFCG.
  
  
  
  Review Fiori Launchpad Configuration:
  
  Check the Fiori Launchpad configuration settings to ensure that everything is set up correctly. This includes checking the target mapping and the catalog assignment.
  
  
  
  Clear Cache:
  
  Sometimes, clearing the browser cache or the SAP Fiori cache can resolve issues related to outdated information.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  /UI2/FLP - Fiori Launchpad
  /UI2/FLP_CATALOG - Catalog Management
  PFCG - Role Maintenance
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  Documentation: Refer to the official SAP Fiori documentation for guidance on managing catalogs and roles.
  
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis or Fiori support team for further assistance.