PlatformPlatformDelivered with a runtime rather than published. Nothing versions it independently and there is nothing to adopt or avoid — it is simply what the platform gives you.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
ABAP CDS
The modelling layer of ABAP Cloud — view entities, projections and annotations defined above database tables, delivered with the platform rather than installed.
Data models rich enough to carry meaning as well as shape, and pushed down to SAP HANA rather than assembled in application code. The same models are meant to serve transactional applications, analytical ones and enterprise search, which is the reason the annotations matter as much as the entities.
Where it sits
Lives in
Provides
Data modellingABAPData modellingDefining the shape of data before anything serves it: entities and their types, how they relate, and the projections and views that services and applications consume.
Who is behind it
SAP SE
Before choosing this
Conditions
PracticalFunctional boundary
Nothing to choose here and nothing to install: it is what an ABAP Cloud system gives you. It shares a name and a lineage with CAP's CDS but is a different language in a different runtime, and a model does not move between them.
What it declares
Every artifact
- Type
- Platform
- Origin
- By SAP
Connections
Group by
NodeRelationBasis
Functional
Data modellingData modellingDefining entities, their relations and the views services consumeSAP and community, unassessed
provides
stated
provides Data modelling
Defines the persistent and projected shape of data for ABAP Cloud, as the technology ABAP data models are built on.
“ABAP data models are based on ABAP Core Data Services (ABAP CDS) – a technology for defining and consuming semantically rich and SAP HANA-optimized data models.”
Defining entities, their relations and the views services consume
Download
Learn more
Readings
- CDS Associations & JoinsCDS Associations & JoinsA Devtoberfest 2026 session from SAP's performance and scalability team on what an ABAP CDS association becomes on SAP HANA, taken as an excerpt from their internal performance training. The CDS edge rests on the three ways an association is used: a path expression and an explicit join both put a left outer join into the generated view, while exposing the association leaves the view without one and adds the join only for a query that asks for its fields, which the session calls join on demand. The data modelling edge is the advice that follows and the demo under it — cardinality written as precisely as the data allows, because the optimiser trusts it, shown with a view whose missing cardinality let SELECT COUNT(*) prune the join and return 18 rows where selecting the columns returned 56, plus the left-hand, right-hand and left-outer-to-inner rewrites that correct cardinalities make possible.SAP Developers, published 2026-10-12SAP Developers, YouTube — SAP Developers playlists
- Developing authorizations for business users in SAP Business AI Platform, ABAP environmentDeveloping authorizations for business users in SAP Business AI Platform, ABAP environmentA Devtoberfest 2026 session that walks the places an authorization check has to be written when a RAP business object is implemented, which is the whole of the authorization edge: read restrictions as DCL access controls that become a filter at query time, a child entity inheriting its parent's conditions through an association, the projection layer inheriting rather than changing them, and the same check repeated on the draft side. The ABAP CDS edge holds on that draft half — until 2608 a draft query view was needed above the draft table so a DCL had something to attach to, while a draft table entity is already on CDS level and takes the DCL directly, as long as the associations used in the inherited conditions are redefined on it. Create, update and delete are then taken handler by handler, including the trap that instance authorization reads the buffer and so cannot see the new value a pre-check would reject, and the session closes on in local mode and privileged EML calls.published 2026-10-12Andre Fischer, YouTube — SAP Developers playlists
- Updates on Embedded Analytics in ABAP Cloud for DevelopersUpdates on Embedded Analytics in ABAP Cloud for DevelopersA Devtoberfest 2026 session (ABA-33) on the generator wizards for Embedded Analytics in ABAP Cloud, run by right-clicking a data definition in the ADT Project Explorer. It first names the artefacts a star schema needs, all of them ABAP CDS — cube view at its centre, dimension, text and hierarchy views reached by association, a hierarchy directory, and an InA service definition and binding — and then generates them: the star schema generator reads a view entity's metadata, sorts its fields into dimensions and measures, asks about the ones it cannot decide, offers the dimension views it found and writes an activated cube view; the hierarchy generator produces directory, node, base and definition views plus a maintenance business object with a generated app, which is used to group airlines into alliances before the hierarchy is switched on in the layout of the multi-dimensional analysis app. That is analytic modelling on the ABAP platform, which is what the edges rest on; the outlook names time-dependent hierarchies, translatable texts and dimensions generated from database tables.published 2026-10-05Andreas Riehl, YouTube — SAP Developers playlists
2 more
- From SEGW to @OData.publish: Expose Your CDS View as OData in S/4HANAFrom SEGW to @OData.publish: Expose Your CDS View as OData in S/4HANAWalks through exposing an ABAP CDS view as an OData service in an on-premise S/4HANA system by adding the @OData.publish: true annotation, then registering and activating the generated service in SAP Gateway (transaction /IWFND/MAINT_SERVICE) before testing it with $filter, $top and $count. It sets this against the manual route through transaction SEGW, since the annotation generates the service, its navigation properties and its OData properties straight from the CDS view without a Service Builder project.rupalipunekar1234, published 2026-07-09rupalipunekar1234, SAP Community
- Analyze and optimize ABAP Cloud model apps built on core data servicesAnalyze and optimize ABAP Cloud model apps built on core data servicesPerformance anti-patterns in data models built with ABAP CDS under ABAP Cloud applications, and the tools that find them: the abstract names ABAP cross trace, the SQL analyzer (PlanViz) in Visual Studio Code and the SAP HANA database explorer as what the session uses to follow a bottleneck from the application to the database. The anti-patterns are taken from real business applications, which is where the data modelling edge holds; which ones are shown is not in the abstract. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Ingo Braeuninger, Robert Werlich, Steffen Siegmund and Thomas Fiedler, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
Others providing
Compare all 3 on the Data modelling page →Data modellingData modellingDefining the shape of data before anything serves it: entities and their types, how they relate, and the projections and views that services and applications consume.SAP and community, unassessed
- cdsanalysercdsanalyserA search tool that maps SAP database tables and fields to the CDS view entities that expose them, and back, from an index a background job builds, for SAP S/4HANA on-premise or private cloud.independent, abapMaps database tables and fields to the CDS views exposing them
- CDS Field MappingCDS Field MappingLooks up which Core Data Services entity and field a classic dictionary table and field map to, filterable by whether the target CDS view is released.independent, abapMaps classic dictionary tables and fields to CDS entities and fields
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaSAP Help Portal
first seen in the atlas
ecosystem and domainabap, data-and-persistence
History in the atlas
- Entered as package for want of anywhere better on the day the enum had no word for a platform component. Nothing publishes or versions ABAP CDS independently, and there is no adoption decision to make about it, which is what the new value is for.
- First seen.
For your agent
- Ref
artifact:abap-cds- JSON
- /artifacts/abap-cds.json
- MCP
- Connecting an agent