ABAP CDS Views ABAP Dictionary Views in Compare

To begin with, 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

dwells in the application server

bolster a wide range of databases

constrained 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

estimations, accumulations, gathering

settled perspectives

HANA CDS Views

lives in the database

bolster just HANA database

the various highlights of ABAP CDS Views

unequivocal highlights for the HANA database

Here are the contrasts between ABAP CDS Views and HANA CDS Views.

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

Understood approval checks

Execution help (see beneath)

ABAP Dictionary Views and ABAP CDS Views Performance

Between the ABAP Stack after 7.40 SP05 and CDS Views is no execution contrast. The two advances utilize the equivalent SQL. This implies the execution is the equivalent on the off chance that what is the full meaning of erp in sap you execute the equivalent SQL articulation by ABAP Stack and along these lines by an ABAP Dictionary View or by a CDS View.

ABAP CDS Views

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 hence 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. Furthermore, CDS Views permit the control of SAP UI5 Smart Controls and Fiori Elements through comments and OData Services which delegates rationale to those controls and subsequently the customer side.

Before the new programming model of SAP the idea was to get with pre-characterized SQL articulations an information bundle from the database and to process it at the application level to the required outcome. The pre-characterized SQL articulations were most usually depicted by ABAP Dictionary Views.

The new programming model transfers the preparing of the SQL got information from the application level down to the database level. Also, does as such by CDS Views. The CDS View don’t just pre-characterize the SQL articulation yet additionally contain the rationale to process the by the SQL explanation brought 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). In any case, a CDS View can move more rationale in contrast with an ABAP Dictionary View from the application server to the database through SQL. All things considered, an ABAP CDS View still drives the consequence of the SQL proclamation back to the application server.

In the old programming model was the rule the less database load the better. In the new programming model is the guideline 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.

Leave a Reply

Your email address will not be published. Required fields are marked *