How To Fix /UI2/CDMFCC235 - Catalog &1 was filtered out.

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/CDMFCC -

• Message number: 235

• Message text: Catalog &1 was filtered out.

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/CDMFCC235 - Catalog &1 was filtered out. ?

  The SAP error message /UI2/CDMFCC235 Catalog &1 was filtered out typically occurs in the context of SAP Fiori applications, particularly when dealing with the Fiori Launchpad and its configuration. This message indicates that a specific catalog (identified by &1) has been filtered out and is not available for the user or the current context.
  Cause:
  
  Authorization Issues: The user may not have the necessary authorizations to access the catalog. This can happen if the catalog is restricted to certain roles or user groups.
  Catalog Configuration: The catalog may be configured in such a way that it is not visible to certain users or under certain conditions.
  Technical Issues: There may be technical issues with the Fiori Launchpad configuration or the underlying OData services that are causing the catalog to be filtered out.
  User Group Assignment: The user may not be assigned to the appropriate user group that has access to the catalog.
  
  Solution:
  
  Check Authorizations: Ensure that the user has the necessary roles assigned that include access to the catalog. You can do this by checking the role assignments in the SAP system.
  Review Catalog Configuration: Go to the Fiori Launchpad Designer and check the configuration of the catalog. Ensure that it is set up correctly and that there are no filters applied that would exclude the user.
  User Group Assignment: Verify that the user is assigned to the correct user group that has access to the catalog. If not, assign the user to the appropriate group.
  Check Technical Settings: If the issue persists, check the technical settings of the Fiori Launchpad and the OData services. Ensure that they are functioning correctly and that there are no errors in the backend.
  Consult Logs: Look at the SAP system logs (transaction codes like SLG1) for any additional error messages or warnings that might provide more context about why the catalog is being filtered out.
  
  Related Information:
  
  Fiori Launchpad Designer: This is the tool used to manage catalogs, groups, and tiles in the Fiori Launchpad. Familiarity with this tool can help in troubleshooting and configuring access.
  Authorization Objects: Understanding the relevant authorization objects (like S_SERVICE, S_TCODE, etc.) can help in diagnosing authorization-related issues.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide additional guidance on this error message.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further assistance.