Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
uladzislau_pralat
Contributor
When it comes to compounded dimension ABAP CDS views you do not need to create them often. But when you do, you might be lacking experience in this area. In my blog I shed some light on this topic. Do not forget a bonus - Field Name dimension that can be used in your next change management CDS view query.

As you can see in my change management CDS view query example cryptic table fields are complemented with table field descriptions. It is possible thanks to using Field Name custom compounded dimension CDS view. Field Name dimension is compounded with Table Name dimension. This is because the same field might exists in multiple tables and have different descriptions. Compounded dimension takes care of it all.


There are a few important points you need to know when creating compounded dimension CDS views:

  1. Compounding fields are defined before compounded field in the list of key fields and annotated with foreign key association

  2. Compounded field is defined last in the list key fields and annotated with text association (if applicable)

  3. Representation key is defined as compounded field



There is only one important point you need to know in case of compounded text CDS view:

  1. Compounding fields are defined in the list of key fields before compounded field



Compounding dimension and text CDS views are very trivial:



You can download complete source code for Field Name dimension CDS view from GitHub:

ZI_FieldName

ZI_FieldNameText

ZI_TableName

ZI_TableNameText

 

 
1 Comment
Labels in this area