on 2025 Sep 10 3:24 PM
Hi everyone,
I would like to dive deeper into the topic of view extensions of standard CDS views. I am familiar with the basic concept and the implementation, and everything is understandable for simple or flat CDS views.
However, there are hardly any standard CDS views that have only one level, but rather multiple ones. The question that arises for me is whether it is always necessary to extend all levels in order to access a field on the "top" level. Or what is the best practice in this case (for example: extend all views? Build a custom view on the interface view and join / associate the desired table/view again? etc.)
For the sake of comprehension, here a concrete example:
The table VBAK was extended by a custom field, via append. I now want to include the respective field in the CDS view I_SalesOrder. The view I_SalesOrder has three hierarchy levels: I_SalesOrder -> I_SalesDocument -> I_SalesDocumentBasic. The latter selects the table VBAK.
Is it now the correct way to extend all three CDS views in order to be able to access the field in I_SalesOrder?
Thanks in advance for the help.
Best regards,
Lukas
Request clarification before answering.
check this association E_SalesDocumentBasic
that's the shortcut for you to add the z field to the top level
basically you will create two z cds, one to extend E_SalesDocumentBasic, second to extend I_SalesOrder
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 14 | |
| 8 | |
| 6 | |
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.