SAPUI5 CDS annotated cannot find DDIC

[Szczerbowski]

Hi,

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:

CX_SADL_NO_DATA_FROM_DDIC
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.

[Szczerbowski · Accepted solution]

In the end I replaced this interface with a custom entity and an RFC call in the implementing ABAP class.
Faster to develop, more consistent in artifacts and easier to control, since I am not involved db-side.

[former_member607044]

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.

[Szczerbowski]

Hi,

I have system A with a some tables A1, and A2, on which I created CDS A3_V.

Then I used SDA to get a virtual source on system B: A3_V --> B1_V

Then I created an AMDP and a table function to query that view (since it's only hana-side): B2_AMDP & B2_TF

Which I used in a CDS B3_VALUEHELP

That is consumed by Fiori in CDS B4_CDS_UI5.

So if in that last one B4_CDS_UI5 I reference B3_VALUEHELP it complains that B3 has no DDIC data and the whole Fiori app does not load.

Which one do you want me to check? I guess maybe it's about missing annotations in B3_VALUEHELP, or missing authorization to the hana-side objects?

Can't really see where i should even start debugging.

[yogananda]

michal.szczerbowski2

If you are using an AMDP to query an Hana view and get the above error Please check if The Hana View actually exists (could also be a lack of privileges) The output of the Hana View is explicit and is the same as the annotation attributes. This error essentially means there is a mismatch between annotation and the hana view's output In case the error still persists then, you could use a debugger to find out at what level the CDS framework is unable to retrieve the appropriate data