ABAP CDS Views were presented in ABAP 7.40 SP05. There are two variations: The ABAP CDS Views and the HANA CDS Views. They are both piece of the new programming model of SAP. The new programming model of SAP pushes the code and in this way the rationale from the application level down to the database level and up to the front-end or customer side. Albums Views driving the rationale down to the database and up to the customer side.
Since they take rationale from an ABAP application from the application server and execute it rather at the database level. In addition, CDS Views permit the control of SAP UI5 Smart Controls and Fiori Elements through explanations and OData Services which delegates rationale to those controls and along what does the acronym erp stand for in sap these lines the customer side.
Before the new programming model of SAP the idea was to bring with pre-characterized SQL proclamations an information bundle from the database and to process it at the application level to the required outcome. The pre-characterized SQL explanations were most generally depicted by ABAP Dictionary Views.
The new programming model transfers the preparing of the SQL brought information from the application level down to the database level. What’s more, does as such by CDS Views. The CDS View don’t just pre-characterize the SQL explanation yet in addition contain the rationale to process the by the SQL proclamation got information. The point is to do however much rationale as could reasonably be expected at the database level by CDS Views.
On account of ABAP CDS Views the perspectives dwell still in the application level in the Data Dictionary (SE11). Be that as it may, a CDS View can move more rationale in contrast with an ABAP Dictionary View from the application server to the database through SQL. By the by, an ABAP CDS View still drives the consequence of the SQL explanation back to the application server.
In the old programming model was the standard the less database load the better. In the new programming model is the standard database should stack as much as possible. It is about Code-to-Data and not any longer Data-to-Code – Code-to-the-Database and not any longer Data-from-the-Database-to-the-Code.
ABAP Dictionary Views in Compare to ABAP CDS Views
Initially, ABAP Dictionary Views in contrast with ABAP CDS Views isn’t to be mistaken for ABAP CDS Views in contrast with HANA CDS Views.
ABAP Dictionary Views Features
lives in the application server
bolster a wide range of databases
restricted essential SQL works as INNER JOIN or SELECT
ABAP CDS Views
dwells in the application server
bolster a wide range of databases
essential SQL works as INNER JOIN, OUTER JOIN, UNION or SELECT
figurings, conglomerations, gathering
HANA CDS Views
dwells in the database
bolster just HANA database
the various highlights of ABAP CDS Views
unequivocal highlights for the HANA database
Why use ABAP CDS Views rather than ABAP Dictionary Views
There are 5 motivations to utilize ABAP CDS Views rather than ABAP Dictionary Views in a R/3 framework:
Upward similarity to S/4
Simple age of undeniable OData Services
Simple utilization of SAP UI5 Smart Controls and Fiori Elements
Verifiable approval checks
Execution support (see beneath)
ABAP Dictionary Views and ABAP CDS Views Performance
oth advancements utilize the equivalent SQL. This implies the execution is the equivalent on the off chance that you execute the equivalent SQL explanation by ABAP Stack and subsequently by an ABAP Dictionary View or by a CDS View.