How To Fix CFD_REGISTRY_CHECK174 - CDS View is not set to invisible but is RDS exposed in Model &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CFD_REGISTRY_CHECK - Custom Fields: Messages for Registry Check

• Message number: 174

• Message text: CDS View is not set to invisible but is RDS exposed in Model &1

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_REGISTRY_CHECK174 - CDS View is not set to invisible but is RDS exposed in Model &1 ?

  The SAP error message CFD_REGISTRY_CHECK174 indicates that there is a configuration issue with a Core Data Services (CDS) view in the context of the SAP system's exposure to the Rapid Data Services (RDS). Specifically, the error suggests that the CDS view is not marked as "invisible" but is still exposed in the RDS model, which can lead to inconsistencies or unintended behavior.
  Cause:
  
  CDS View Configuration: The CDS view is defined in such a way that it is not set to invisible, meaning it is intended to be visible and accessible. However, it is also marked as RDS exposed, which typically implies that it should not be directly accessible.
  Model Definition Issues: There may be a mismatch in the model definition where the visibility settings of the CDS view do not align with the intended usage in the RDS context.
  Development or Transport Issues: Changes made to the CDS view or its exposure settings may not have been properly transported or activated in the system.
  
  Solution:
  
  
  Check CDS View Definition: Review the definition of the CDS view in the ABAP Development Tools (ADT) or the relevant transaction (e.g., SE11, SE80). Ensure that the visibility settings are correctly configured.
  
  If the view should not be directly accessible, set the @AbapCatalog.sqlViewName annotation to invisible.
  If it should be visible, ensure that it is not marked as RDS exposed.
  
  
  
  Adjust RDS Exposure: If the CDS view is intended to be used in RDS, ensure that it is correctly marked for RDS exposure. You may need to adjust the annotations related to RDS in the CDS view definition.
  
  Use the @OData.publish: true annotation if you want to expose the view as an OData service.
  
  
  
  Re-transport Changes: If changes were made to the CDS view or its exposure settings, ensure that these changes are properly transported to the relevant systems (development, quality assurance, production).
  
  
  Check Dependencies: Ensure that there are no dependencies or references to the CDS view that might be causing conflicts with its visibility settings.
  
  
  Consult Documentation: Refer to the SAP documentation for Core Data Services and Rapid Data Services for best practices and guidelines on configuring visibility and exposure settings.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on configuring CDS views and RDS.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  SAP Help Portal: Utilize the SAP Help Portal for detailed documentation on CDS views, RDS, and related topics.
  
  By following these steps, you should be able to resolve the CFD_REGISTRY_CHECK174 error and ensure that your CDS view is correctly configured for its intended use.