How To Fix /UI2/FDM_2_CDM3090 - Page &1 Section &2 Tile &3 reference catalog &4 which was not scoped

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 090

• Message text: Page &1 Section &2 Tile &3 reference catalog &4 which was not scoped

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_CDM3090 - Page &1 Section &2 Tile &3 reference catalog &4 which was not scoped ?

  The SAP error message /UI2/FDM_2_CDM3090 typically indicates that a specific page, section, or tile in the Fiori Launchpad is not properly scoped or configured. This can occur for various reasons, such as missing authorizations, incorrect configuration, or issues with the underlying data model.
  Cause:
  
  Missing Scoping: The referenced page, section, or tile is not included in the current scope of the Fiori Launchpad configuration.
  Authorization Issues: The user may not have the necessary authorizations to access the specified tile or page.
  Configuration Errors: There may be issues in the configuration of the Fiori Launchpad or the underlying OData services.
  Transport Issues: If the application was recently transported from one system to another, some configurations may not have been transported correctly.
  
  Solution:
  
  
  Check Scoping:
  
  Go to the Fiori Launchpad Designer and verify that the page, section, and tile are correctly scoped.
  Ensure that the relevant catalog is assigned to the user role.
  
  
  
  Review Authorizations:
  
  Check the user’s roles and authorizations to ensure they have access to the required catalogs and tiles.
  Use transaction PFCG to review and adjust roles as necessary.
  
  
  
  Configuration Verification:
  
  Ensure that the OData services required for the tile are activated and functioning correctly.
  Check the configuration in the Fiori Launchpad Designer to ensure that all necessary components are properly set up.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, verify that all necessary objects were included in the transport request.
  Check for any missing configurations or objects in the target system.
  
  
  
  Debugging:
  
  Use the browser's developer tools to check for any JavaScript errors or network issues that may provide more context about the error.
  Look into the SAP Gateway logs for any related error messages that could give more insight.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Fiori Launchpad Documentation: Review the official SAP documentation for Fiori Launchpad configuration and troubleshooting.
  Community Forums: Engage with the SAP Community or forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.