
Co-Authored: Ritesh K Kumaria, Shekhar Razdan
In continuation to the previous Posts (The Semantically Rich Data Model – An ABAP based CDS Views example) & (The Semantically Rich Data Model – An ABA... | SCN )
Annexure 4: How to Expose CDS Views as ODATA
CDS as OData for AS ABAP 7.5.
Annexure 5: How to Translate Labels in CDS Views
Column labels, Field Labels, Report names etc. can be specified while creating CDS Views. The Column and Fields can pick up labels from their corresponding Data Elements. This ensures that the translations for the Data Element Labels are available to the fields and thus no separate Translation needs to be done.
However, it is also possible to add fields in field list as literals that do not refer to any Data Element in particular. In such cases the field labels can still be specified using the Annotation “@EndUserText.label:”
The same annotation can also be used to specify the report name that is visible to the end user while consuming the report via an analytical client. So how does one translate the labels that have been specified by using @EndUserText.Label: ?
Similar to other DDIC objects CDS Views are also translatable via TCODE SE63 (Translation Editor).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
4 | |
3 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |