What is a Differences Between ABAP CDS Views and ABAP Dictionary Views

ABAP Dictionary Views or Database Views are made in the SE11 in the ABAP Dictionary. ABAP CDS Views are made in Eclipse – for the time being. The theory is, that at some point or another they can be created in the Web IDE too.

Where an ABAP Dictionary View and an ABAP CDS Views gets made is the primary clear contrast. Be that as it may, first of all – what are ABAP Dictionary what does the acronym erp stand for in sap Views and what are ABAP CDS Views.

ABAP Dictionary Views

ABAP Dictionary Views bring from the database pre-characterized information. The ABAP Dictionary Views gets from the database by SQL Statements the information required for an application to process the ideal outcome.

For instance, an ABAP application needs to yield all items. For this, the application needs to bring from the database the fundamental information of an item. Also, rather than doing this legitimately by a SQL articulation the application utilizes an ABAP Dictionary View.

The ABAP Dictionary View gets the information of an item from the tables of the database by SQL. It interfaces just for an item important tables of the database by Inner Joins and chooses from the tables all the fundamental fields for an item.

At that point the ABAP application does not utilize straightforwardly a SQL articulation to get the information of the item from the database yet the ABAP Dictionary View. The ABAP Dictionary View resembles an extra layer between the ABAP application and the database.

For instance, the name of the ABAP Dictionary View is ZPRODUCTS. It contains all tables and fields which are important for an item.

In the ABAP code the view could be utilized this way:

SELECT * FROM zproducts

Request BY product_name

INTO TABLE @DATA(result).

cl_products_output=>display( result ).

An ABAP Dictionary View is a view for at least one database tables. It is actually a view. Envision you are glancing through binoculars at a database. You just center certain tables or even only one table. Same goes with ABAP Dictionary Views: You pick one certain table or group certain tables together. Furthermore, you can likewise concentrate just on specific fields from those picked tables.

For instance, a database contains a cluster of tables. The point of your application is to return information which dwells in three of the tables of the database. What’s more, just a single field of each table is fundamental. Here comes the view: The view associates those three tables and picks just the fields of the tables which are required.

When you actuate an ABAP Dictionary View then a SQL View is made. This SQL View contains the SQL grammar of the characterized ABAP Dictionary View. For instance, in the event that you associate more than one table with an ABAP Dictionary View, at that point the SQL explanation of the SQL View does this by an Inner Join.

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 accordingly the rationale from the application level down to the database level and up to the front-end or customer side. Compact discs 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. Also, 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 thusly the customer side.

Before the new programming model of SAP the idea was to get with pre-characterized SQL explanations 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 normally portrayed 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. What’s more, 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 got information. The point is to do however much rationale as could 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 and by, an ABAP CDS View still drives the aftereffect of the SQL proclamation back to the application server.

In the old programming model was the guideline 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.

Leave a Reply

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