ERPClimb logoERPClimb
CDS · Data Modelling

SAP CDS Views Interview Questions

CDS has quietly become the dividing line in ABAP interviews. Candidates who modelled data before HANA think in joins and nested selects; interviewers now listen for associations, annotations and pushdown — whether you think in the layer where the database does the work.

The questions on this page are drawn from ERPClimb's reviewed bank and cover the full arc: what a CDS view entity actually is and how it differs from the classic DDIC-based view, associations versus joins, parameters and where they push down, access control through roles, and the analytical annotations that drive embedded reporting.

The strongest answers here are architectural, not syntactic. Saying where logic belongs — and what it costs when it lands in the wrong layer — is what separates a senior answer from a tutorial answer.

What interviewers actually probe

Associations versus joins

A guaranteed question. The expected answer covers lazy evaluation and exposure to consumers, not just syntax — associations declare a relationship the consumer chooses to navigate.

What the annotations do

Interviewers probe whether you know that annotations carry semantics — UI, analytical, access — rather than decoration, and which annotation families drive Fiori Elements and embedded analytics.

View entities versus classic views

The modern-versus-legacy line: why the view entity is the go-forward artefact, what the DDIC-based view could not express, and what a migration between them involves.

Access control

Where authorisation lives in a CDS world — the expected answer names the access control artefact and explains why filtering at the model beats filtering in every consumer.

13 questions with full answers

Ordered from foundational to advanced. No sign-in required.

easyCDS Views

1. What is a CDS view?

A CDS view is a Core Data Services data model defined in DDL, typically in ADT, and designed as a HANA-first approach to expose reusable business data. The first thing to check is that it is not just a simple database view: it generates a database view and related dictionary artefacts, so it sits higher in the modelling layer. It is used because it provides a structured, semantically rich way to model data close to the database while keeping it consumable by applications. A strong candidate adds that CDS supports annotations for OData, analytics, UI and authorisation, which makes it suitable for modern SAP development and service exposure.
easyCDS Views

2. What is an association in CDS?

An association in CDS is a declarative navigation from one view or entity to another, defined with a statement such as association [card] to X on <condition>. The first thing to check is the relationship and the ON condition, because that defines how the target can be reached. It is useful because the join is lazy: it is only generated when a path expression actually consumes the association, which helps keep the model clean and avoids unnecessary joins. A strong candidate also mentions that associations improve semantic modelling and make reuse easier, since consumers can navigate to related data without hard-coding the join logic in every view.
mediumCDS Views

3. Data appears wrong in a consumption CDS view. Approach?

First check each layer independently in ADT, starting with the underlying basic or interface view before the consumption view, so you can isolate where the wrong data is introduced. Then review joins and associations for cardinality or filter issues, and verify aggregation types plus unit and currency handling, because these often change the displayed result even when the source data is correct. After that, inspect the generated SQL in ST05 to confirm what actually runs at database level and whether the CDS definition matches the runtime result. A strong candidate also compares the preview result with the business expectation and checks whether the issue is caused by a missing join condition, incorrect grouping, or inconsistent master data.
mediumCDS Views

4. How do you expose a CDS view as OData?

First check the system release, because the exposure method depends on whether you are on S/4HANA with RAP available or on an older stack. On S/4HANA, annotate the CDS view with the relevant @ObjectModel.query: true and @UI annotations, then create a service definition and service binding in RAP to publish it as an OData service for Fiori. This is the preferred approach because it keeps the model, service, and UI metadata aligned and reduces manual coding. On older systems, use ODATA_V2_UI to reference the CDS view and expose it through classic OData V2 handling. A strong candidate also mentions checking the service activation and testing the endpoint before handing it to the UI team.
easyCDS Views

5. What is the difference between CDS view entity and classic CDS view?

First check the definition type. A classic CDS view is created with define view and typically needs a generated SQL view name, because the runtime object is based on that separate SQL view. A CDS view entity is created with define view entity and does not require a separate SQL view name, so the model is more direct and streamlined. For that reason, on supported releases, view entities are generally preferred for new development. A strong candidate would add that the choice affects how the object is managed and evolved, and that entities are the modern CDS option when starting fresh, while classic views may still be encountered in existing solutions.
hardCDS Views

6. How do you secure data exposed by CDS Views?

First I would check whether the CDS view exposes data that needs row-level protection and whether an authorization check is already enabled on the view. If access must be restricted, I would create the relevant DCL roles so the view returns only the records a user is allowed to see. I would also review the selected fields and avoid exposing sensitive data unless it is really required. A strong candidate also validates the result with users who have different authorisations, so both the data scope and the field-level exposure are tested from an end-to-end security perspective.
mediumCDS Views

7. A CDS-based Fiori app shows duplicate rows. What would you check?

First I would check the CDS joins and associations to see whether any one-to-many relationship is being consumed as if it were one-to-one. Duplicate rows often come from a join that multiplies the result set, so I would review the cardinality, the key fields in the view, and whether the grouping logic is actually preventing repeated records. I would then compare the underlying data to confirm whether the duplicates are already present there or are introduced by the CDS layer. A strong candidate also checks the consumption view carefully, because exposing associations or joins incorrectly can cause record multiplication in the Fiori app even when the base data is clean.
mediumCDS Views

8. What is DCL?

First check whether the question is about CDS access control, because in SAP DCL usually means Data Control Language. It is the CDS artefact used to apply row-level authorisation to a view by linking the result set to authorisation objects. In practice, DCL is evaluated as filter conditions when the CDS view is queried, so users only see the records they are allowed to access. A strong candidate adds that this is part of securing CDS consumption cleanly at the data model level, rather than handling the restriction later in the application.
mediumCDS Views

9. How would you design CDS views for a Fiori list report?

I would design layered CDS views. A basic/interface view exposes reusable table-level fields, a composite view combines and prepares business data, and a consumption view adds UI annotations, selection fields, semantic annotations and authorization checks. I would avoid putting all logic and annotations into one giant CDS view.
hardCDS Views

10. A CDS view is slow in production. How would you analyze and improve it?

I would first identify the consumer and selection criteria, then analyze generated SQL, execution plan, data volume, joins, associations, filters and aggregation. I would reduce unnecessary fields and associations, add selective filters, correct cardinality, push aggregation to DB where suitable and split a monster view into layered reusable views if required.
hardCDS Views

11. Legacy report on SE11 views performs badly. Migrate to CDS?

Yes, but start by checking the existing SE11 views, the report logic, and where the bottleneck is before changing anything. If the report is doing row-by-row ABAP processing, move the data model to interface CDS views and use composite CDS views for the calculations and joins. This lets you push filtering and aggregation down to the database instead of handling large volumes in ABAP loops, which is usually the main performance gain. A strong candidate also validates the new result set against the old report, retests performance with realistic data, and only retires the SE11 views once no dependent programs or interfaces remain.
hardCDS Views

12. How would you structure a CDS model for a domain?

I would start by identifying the domain entities and then structure the CDS model in three clear layers. The interface layer exposes the raw tables and basic joins, so it stays close to the source and provides a stable foundation. On top of that, the composite layer adds the business logic, richer joins and associations needed to represent the domain consistently. Finally, the consumption layer is designed for the actual use case, such as UI or analytics, with the relevant annotations applied there. A strong point is to apply DCL at the interface level, so access control is enforced centrally and inherited by all consuming views. This keeps the model reusable, easier to govern, and simpler to extend without duplicating checks in every consumer.
hardCDS Views

13. CDS view is slow on HANA. What do you tune?

First check the SQL plan in SM/ST05 to see where HANA is spending time and whether the CDS is causing expensive joins, large intermediate result sets, or late filtering. Then simplify the view by removing unnecessary joins and pushing filters as early as possible, especially into associations so only relevant data is brought in. For complex logic that the optimizer cannot handle efficiently in CDS alone, a table function via AMDP can be a better option. If the view is part of an extraction or reporting pipeline, a persistent aggregate can help avoid repeated heavy calculations. A strong candidate also mentions validating the actual data volume and cardinality assumptions, because tuning only works if the design matches the access pattern.

Practise by experience level

Fresher1-3 years4-7 years8-12 yearsArchitect

The questions above are tagged by the experience levels they are normally asked at, so the same page works for a first interview and for a lead-developer round.

SAP CDS Views Interview Questions FAQ

What is the difference between a CDS association and a join?

A join combines data eagerly in the statement; an association declares a relationship that is only resolved when a consumer navigates it. Associations keep the base model lean, express cardinality, and are what path expressions and service exposure build on — which is why interviewers treat 'it is just a join' as a red flag.

What is a CDS view entity?

The current generation of CDS view: defined entirely in the DDL source, without a generated DDIC view underneath, and with stricter, cleaner semantics. It is the artefact new modelling should use, and knowing what the classic DDIC-based view could not express — typed associations being the everyday example — is the expected follow-up.

Where does authorisation happen for CDS views?

In the model itself, through access control artefacts attached to the view, so every consumer — service, analytical query, or direct read — gets the same filtering. The contrast interviewers want is with authority checks scattered across every calling program.

What are CDS parameters used for?

For inputs the model needs at selection time: a key date, a target currency, a language. Because they are part of the view's contract they push down to the database, unlike a filter applied after the fact in ABAP — that pushdown is the point of the question.

How do CDS views relate to embedded analytics?

Analytical annotations turn a view into a cube or query that the analytical engine can consume directly, which is how embedded reporting on S/4HANA is built. Interviewers check whether you know the modelling conventions that make a view analytically consumable rather than just selectable.

Next practice step

Practise these questions with Interview AITake a mock test

Related SAP interview topics

ERP Climb is an independent educational platform and is not affiliated with SAP SE.