How To Fix /UI2/CDMDEL006 - No entries for selected Object Type(s) found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/CDMDEL -

• Message number: 006

• Message text: No entries for selected Object Type(s) 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/CDMDEL006 - No entries for selected Object Type(s) found ?

  The SAP error message /UI2/CDMDEL006 No entries for selected Object Type(s) found typically occurs in the context of the SAP Fiori Launchpad or when working with the SAP UI2 framework. This error indicates that the system could not find any entries for the specified object type in the configuration or data model.
  Causes:
  
  Missing Configuration: The object type you are trying to access may not be configured correctly in the system.
  Authorization Issues: The user may not have the necessary authorizations to view the object type.
  Data Model Issues: The underlying data model may not have any entries for the specified object type.
  Transport Issues: If the configuration was recently transported from another system, it may not have been transported correctly.
  Incorrect Object Type: The object type specified in the request may be incorrect or misspelled.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify that the object type is correctly configured in the SAP system. This can be done by checking the relevant customizing settings in the SAP Fiori Launchpad or UI2 configuration.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access the object type. You can check this using transaction codes like SU53 to analyze authorization issues.
  
  
  
  Inspect Data Model:
  
  Check the underlying data model to ensure that there are entries for the specified object type. You can use transaction codes like SE11 to view the data dictionary and confirm the existence of entries.
  
  
  
  Transport Check:
  
  If the configuration was recently transported, ensure that all necessary objects were included in the transport request and that the transport was successful.
  
  
  
  Correct Object Type:
  
  Double-check the object type being referenced in the request. Ensure that it is spelled correctly and matches the expected format.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the application to trace where the error is occurring. This may provide more insight into why no entries are being found.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found.
  Documentation: Review the official SAP documentation for the Fiori Launchpad and UI2 framework for any specific configuration steps or requirements.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution. If the problem persists, consider reaching out to your SAP support team for further assistance.