How To Fix CFD_REGISTRY_CHECK035 - Enter the Name of your extensible OData Model

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 035

• Message text: Enter the Name of your extensible OData Model

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_CHECK035 - Enter the Name of your extensible OData Model ?

  The SAP error message CFD_REGISTRY_CHECK035, which prompts you to "Enter the Name of your extensible OData Model," typically occurs in the context of SAP Fiori or SAP Gateway development when working with OData services. This error indicates that the system expects a valid name for an extensible OData model, but it has not been provided or is not recognized.
  Cause:
  
  Missing Model Name: The error usually arises when the required input for the OData model name is missing or not properly configured in the application or service definition.
  Configuration Issues: There may be issues in the configuration of the OData service or the associated metadata.
  Development Environment: If you are working in a development environment, it could be due to incomplete or incorrect setup of the OData service.
  
  Solution:
  
  Provide a Valid Model Name: Ensure that you enter a valid name for your extensible OData model in the relevant configuration or input field. This is often done in the service definition or when creating a new OData service.
  Check Service Configuration: Review the configuration of your OData service in the SAP Gateway Service Builder (transaction code SEGW). Make sure that all necessary fields are filled out correctly.
  Regenerate the Service: If you have made changes to the model or service, regenerate the service to ensure that all changes are applied. This can be done in the Service Builder.
  Check Metadata: Ensure that the metadata for the OData service is correctly defined and that the model is properly registered in the system.
  Review Documentation: Consult the SAP documentation or help resources for guidance on setting up extensible OData models and troubleshooting common issues.
  
  Related Information:
  
  SAP Gateway: Familiarize yourself with the SAP Gateway and OData service concepts, as understanding these will help you troubleshoot issues more effectively.
  Transaction Codes: Common transaction codes related to OData services include:
  
  SEGW: Service Builder for creating and managing OData services.
  /IWFND/MAINT_SERVICE: To maintain and activate OData services.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message or provide updates and patches.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support or consulting with a colleague who has experience with OData services in SAP.