How To Fix ESH_ENG_CDS_ABAP035 - &1: DDIC view data missing

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ENG_CDS_ABAP - ES-CDS/ABAP

• Message number: 035

• Message text: &1: DDIC view data missing

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 ESH_ENG_CDS_ABAP035 - &1: DDIC view data missing ?

  The SAP error message ESH_ENG_CDS_ABAP035 indicates that there is missing data in a Data Dictionary (DDIC) view that is required for the operation you are trying to perform. This error typically occurs in the context of SAP's Enterprise Search or when working with Core Data Services (CDS) views.
  Cause:
  
  Missing Data: The most common cause is that the underlying database table or view that the DDIC view is based on does not contain the expected data.
  Inconsistent Data Model: Changes in the data model (like deletion or modification of tables/views) that are not reflected in the DDIC view can lead to this error.
  Transport Issues: If the DDIC view was transported from one system to another, there might be inconsistencies or missing objects in the target system.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the data in the underlying tables/views.
  
  Solution:
  
  Check Data Availability: Verify that the underlying tables or views contain the necessary data. You can do this by executing a simple SELECT statement on the relevant tables.
  Rebuild the DDIC View: If the view is corrupted or not reflecting the current state of the database, you may need to regenerate or rebuild the DDIC view.
  Transport Consistency: Ensure that all necessary objects have been transported correctly. Check for any missing objects or dependencies in the target system.
  Authorization Check: Ensure that the user has the necessary authorizations to access the data. You can check this in transaction SU53 or by consulting with your security team.
  Check for Notes: Look for any SAP Notes related to this error message. Sometimes, SAP releases notes that provide specific fixes or workarounds for known issues.
  Debugging: If the issue persists, consider debugging the application or process that is triggering the error to get more insights into what might be going wrong.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), or SE37 (Function Builder) to investigate the DDIC view and its components.
  SAP Notes: Search the SAP Support Portal for any relevant notes that might address this specific error message.
  Documentation: Review the documentation for the specific CDS view or application you are working with to understand its dependencies and requirements.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.