Showing results for 
Search instead for 
Did you mean: 

SAPUI5 CDS annotated cannot find DDIC

Active Participant
0 Kudos


I have a List Report built on a CDS and use annotations to provide F4 value helps.
It works if the annotated subquery is 'normal', so a table sourced query.
But if I use an AMDP table function, to query a Hana-side virtual table, then I get:

No data retrieved from ABAP dictionary for entity yyy

I cannot find any trigger point for that exception or message SADL_ENTITY-001 so I can't debug what exactly is missing.

View Entire Topic
0 Kudos

The exception CX_SADL_NO_DATA_FROM_DDIC with the message "No data retrieved from ABAP dictionary for entity yyy" typically occurs when the ABAP Dictionary cannot retrieve the required metadata for the specified entity. This exception is commonly encountered in the context of CDS-based List Reports when using annotations to provide F4 value helps.

In your case, you mentioned that the issue arises when you use an AMDP (ABAP Managed Database Procedure) table function to query a HANA-side virtual table. The AMDP table function allows you to perform advanced operations within the HANA database, but it seems to be causing the exception.

To troubleshoot this issue, here are a few suggestions:

  1. Verify the CDS definition: Double-check the CDS view definition used in your List Report and ensure that it includes the necessary associations, annotations, and dependencies on the AMDP table function. Make sure the entity 'yyy' is properly defined and accessible.
  2. Check the AMDP implementation: Review the implementation of the AMDP table function. Ensure that the input and output parameters, as well as the logic inside the AMDP class, are correctly defined. Pay attention to any potential issues related to data retrieval or data types.
  3. Debug the AMDP table function: Use the ABAP debugger to step through the code of the AMDP class and table function. Set breakpoints at relevant points, such as the start of the AMDP method or the query execution inside the table function. By debugging, you can pinpoint the exact location where the exception is triggered and gather more information about the cause.
  4. Analyze the ABAP Dictionary: Analyze the ABAP Dictionary objects involved in your CDS view and AMDP table function. Ensure that all required tables, structures, and types are present and activated in the system. Check if any relevant changes were made to the underlying database objects and if those changes have been propagated correctly to the ABAP Dictionary.
  5. Consult SAP Community: If the above steps do not resolve the issue, consider posting a question on the SAP Community platform. Provide detailed information about your CDS view, AMDP table function, and any relevant error messages. The SAP Community is an excellent resource to seek assistance from experts who can help diagnose and troubleshoot the problem.

By following these steps, you should be able to identify the root cause of the exception CX_SADL_NO_DATA_FROM_DDIC and resolve the issue with your List Report using annotations and AMDP table functions.