RAP_CDS_ODATAbeginner
CDS Annotations
Master CDS annotations for semantics, authorization, analytics, UI metadata and service consumption. Learn where annotations belong, how to avoid polluting reusable interface views and how metadata extensions and projection layers keep consumer-specific behavior maintainable.
Overview
Master CDS annotations for semantics, authorization, analytics, UI metadata and service consumption. Learn where annotations belong, how to avoid polluting reusable interface views and how metadata extensions and projection layers keep consumer-specific behavior maintainable.
Lessons in this topic
- CDS Annotations Part 1: What Annotations Are and Where They ApplyUnderstand what CDS annotations are, where they can be placed, which families exist (ABAP, semantics, UI, consumption, search, analytics), how they propagate through view layers and where they end up in OData.
- CDS Annotations Part 2: Semantic Annotations for Currency, Units and TextsMake data self-describing with semantic annotations: amounts with currencies, quantities with units, text elements and text associations, languages, and admin fields that RAP maintains automatically.
- CDS Annotations Part 3: Fiori UI Annotations — Line Items, Facets and Selection FieldsBuild a complete Fiori Elements list report and object page with UI annotations: header info, line items, selection fields, identification, facets, field groups, actions and value helps.
- CDS Annotations Part 4: Metadata Extensions — Separating UI from the Data ModelSeparate UI from the data model with metadata extensions: syntax, allowed annotations, layers and precedence, and how to organize extensions for several apps on the same business object.
- CDS Annotations Part 5: Troubleshooting Precedence, Metadata and UI BehaviorFind out why an annotation seems to be ignored: check the effective value, layer precedence, the exposed element, the OData metadata and caches — in a fixed order.
Interview questions covered
- What are CDS annotations, which scopes and families exist, and how do they propagate?
- Three apps reuse one interface view that contains all UI annotations. Changing one app breaks the others. How do you reorganize?
- How do you connect amounts, quantities and texts to their semantics in CDS, and what goes wrong without it?
- Build a Fiori Elements list report and object page for purchase requests with annotations only. Which annotations do you use?
- An object page lost its 'Financial Details' section after a refactor. What do you check?
- What is a metadata extension, how are layers resolved, and which annotations can it not contain?
- A developer's new column annotation does not appear in the Fiori app. Give your troubleshooting order.
- Where should each kind of annotation live in a RAP stack (R_, C_, metadata extension), and why?
- After transport to QAS, list columns and filters look different from DEV. What could cause it?
- You inherit CDS views full of annotations. What do you review first?