How To Fix CFD_GW_UI011 - Usage of underlying CDS View &1 is missing in Usage Entity Set

SAP Error Message - Details

• Message type: E = Error

• Message class: CFD_GW_UI - TechnicalMessages for Custom Field Maintenance oData Service

• Message number: 011

• Message text: Usage of underlying CDS View &1 is missing in Usage Entity Set

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 CFD_GW_UI011 - Usage of underlying CDS View &1 is missing in Usage Entity Set ?

  The SAP error message CFD_GW_UI011 indicates that there is an issue with the usage of a Core Data Services (CDS) view in the context of a Gateway service. Specifically, it suggests that the underlying CDS view is not properly referenced or utilized in the associated usage entity set.
  Cause:
  
  Missing Usage Entity Set: The CDS view is not linked to any usage entity set in the Gateway service definition.
  Incorrect Annotations: The annotations in the CDS view may not be correctly defined, leading to the system not recognizing its usage.
  Service Registration Issues: The OData service may not be properly registered or activated in the SAP Gateway.
  Transport Issues: If the CDS view was recently transported, it may not have been fully activated in the target system.
  
  Solution:
  
  
  Check CDS View Annotations:
  
  Ensure that the CDS view has the correct annotations for usage in the OData service. You may need to add or correct the @OData.publish: true annotation if it is missing.
  
  
  
  Define Usage Entity Set:
  
  Go to the Gateway Service Builder (transaction code SEGW) and check if the usage entity set is defined for the CDS view. If not, you may need to create a new entity set that references the CDS view.
  
  
  
  Activate the Service:
  
  After making changes, ensure that you activate the OData service in the SAP Gateway using transaction code /IWFND/MAINT_SERVICE. Check if the service is listed and activated.
  
  
  
  Check for Transport Issues:
  
  If the CDS view was transported, ensure that all related objects (like the service definition) are also transported and activated in the target system.
  
  
  
  Regenerate the Service:
  
  If changes were made to the CDS view or its annotations, regenerate the service in the Gateway Service Builder to ensure that the changes are reflected.
  
  
  
  Check for Dependencies:
  
  Ensure that there are no missing dependencies or issues with the underlying data model that could affect the CDS view.
  
  
  
  Related Information:
  
  CDS Views: Core Data Services (CDS) are a way to define semantically rich data models in SAP. They can be used to create OData services.
  OData Services: OData is a standard protocol for creating and consuming RESTful APIs. In SAP, OData services are often used to expose data from backend systems to frontend applications.
  SAP Gateway: SAP Gateway is a technology that enables the connection between SAP systems and external applications, allowing for the creation of OData services.
  
  If the issue persists after following these steps, it may be beneficial to consult SAP Notes or reach out to SAP support for further assistance.