In brief
CDS stands for Core Data Services. With a CDS view you define in SAP how data from different tables forms a meaningful whole, for example "an order with its customer and items". The view runs in the database itself, which is fast, especially on SAP HANA.
What makes it special
- Meaning included. With annotations you describe what fields are: an amount with a currency, a description, a key. Tools and apps use that information directly.
- Building blocks. Views build on each other: basic views on the tables, and on top of them views for a specific purpose.
- The foundation of modern SAP. Fiori apps, analytics and the RAP programming model work with CDS views. Through RAP or a service definition you publish them as an OData service.
Released views
SAP supplies thousands of standard CDS views. Some of them are officially released for customer use. These remain stable across new versions, and they are what you should preferably build on, rather than directly on SAP tables.
What do you use it for
- Assembling data for an app or report without copying it.
- A stable foundation for an integration or API.
- Doing calculations close to the data, in the database.
What to watch out for
- Build on released views where you can; that makes upgrades easier.
- Keep views clear and layered. A view that does everything is hard to maintain.
- Authorisations are part of it: with access controls you determine who sees which data.
Would you like advice on CDS views? Request a free advice conversation.
Updated on