Академический Документы
Профессиональный Документы
Культура Документы
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
SAP YARD
TUTORIALS
CODE SNIPPETS
HELP FORUM
SAP QUIZ
136
Shares
Beginners SAP
Enteremail
Subscribe
SEARCH
http://www.sapyard.com/abaponsaphanapartiv/
1/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
SAPYard
Let us start our encounter with Core Data Services (CDS) View with
questions and answers. Before we explain What is CDS View, let us ask,
Why CDS View?
Question: Why do we really need CDS Views?
Answer: According to SAP, CDS Brings Conceptual and Implementation Level
Closer Together.
136
Shares
656likes
Liked
Youand2otherfriendslikethis
Abapinho
The issue with the above SQL: Large Semantic Gap between Requirement
and SQL Code.
If you are not an experienced SQL developer, you would nd it
complex/dif cult to understand the meaning/semantic of the SQL. Therefore
SAP wanted something simpler and better. This is one motivation for CDS.
7MostPopular&FeaturedArticles
Being an ABAPer you nd the above SQL complex and you decide to write
your own Open SQL in ABAP.
DELETING rows of the internal
table within the LOOP. Is it a
http://www.sapyard.com/abaponsaphanapartiv/
2/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
Fiori App - An
Introduction from an
ABAPer
136
Shares
Issue with the above Open SQL: SQL Complexity Leads to Imperative Code
(codes which are like instructions/statements which change its state.
Imperative programming focuses on describing how a program operates.)
There are performance concerns in the above Open SQL. Loops in loops,
nested queries with many round trips is not advisable. This is another
motivation for CDS.
Zero
ABAP on SAP HANA.
Part I. First Program in
ABAP HANA
NetworkedBlogs
Blog:
SAPYard
With CDS, SQL developerssee small or no semantic gap and ABAPers do not
need any coding. You get the result directly from the CDS. Isnt this
motivation enough?
Topics:
Abap,Sap,Hana
Followourblog
3/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
CDS views?
Answer: CDS is much more powerful than what it appears. The CDS concept
is far more than simple view building but describes a DDL for building a metamodel repository involving database tables, database views, functions, and
data types.
136
CDS was invented by SAP, because the modeling capabilities of the ABAP
Dictionary and of the SAP HANA Studio are not suf cient for the needs
of all fully blown business applications with modern needs.
Shares
With HANA CDS, CDS is available for SAP HANA in the SAP HANA studio.
With ABAP CDS, the CDS concept is also made available for the AS ABAP,
where the features of CDS surpass the modeling capabilities of SE11. ABAP
CDS is open and not restricted to SAP HANA (i.e. database independent).
If we need meta-models for our application, that can be built with CDS, then
we need CDS views.
Question: OK, we read above that CDS was invented to facilitate needs
which ABAP Dictionary and HANA Studio could not meet. So, what are the
types of CDS Views?
Answer: There are two types of CDS Views.
1. ABAP CDS
2. HANA CDS
Check the details in CDS One Concept, Two Flavors
NOVEMBER 5, 2014
NOVEMBER 3, 2014
4/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
5/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
layered fashion, starting with basic views and then adding powerful views that
combine the basic views. Another difference is the support for special operators
such as UNION, which enables the combination of multiple select statements to
return only one result set.
CDS artifacts are stored in the DDIC and can be accessed in ABAP programs
via Open SQL in the same manner as ordinary ABAP tables or views.
136
Shares
In simple words:
Core data services are a new infrastructure for de ning and consuming
semantically rich data model in SAP HANA. Using a data de nition language
(DDL), a query language (QL), and an expression language (EL), CDS is
envisioned to encompass write operations, transaction semantics,
constraints, and more .
We can use the CDS speci cation to create a CDS document which de nes
the following artifacts and elements:
Entities (tables)
Views
User-de ned data types (including structured types)
http://www.sapyard.com/abaponsaphanapartiv/
6/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
Contexts
Associations
Annotations
Question: When do we need CDS Views?
Answer: It depends on reusability. If the functionality of a view is only
needed once, then no need to create CDS Views. We can use Joins, SQL
expressions, subqueries etc in Open SQL for this code push down. But if we
want to reuse a view, need semantical or technical capabilities of CDS that
136
Shares exceed those of Open SQL (but we try to keep the technical capabilities on
the same level, e.g., CDS knows UNION, Open SQL will know UNION with an
upcoming release) or we just want to push down the full data model to the
database, we need CDS.
Question: What is the fundamental difference between HANA CDS and
ABAP CDS?
Answer: The subtle differences between CDS in native SAP HANA and CDS in
ABAP lies in the view de nition. In both the ABAP and HANA scenarios, views
are created on top of existing database tables that are contained in the
DDIC. With CDS in native SAP HANA, we must create the basic entity types that
correspond to the DDIC tables as part of the CDS view de nition. With CDS in
ABAP, we can refer to any underlying DDIC table, view, or type from within the
CDS view de nition, avoiding the need to duplicate the DDIC table de nitions
on the CDS layer. In the ABAP scenario, the CDS de nitions are considered
DDIC artifacts and need to be activated like any other DDIC artifact and
when changes are made, their impact is propagated to dependent artifacts.
Question:What is preferred ABAP CDS or HANA CDS if the client is in
ABAP on HANA DB?
Answer: If you use ABAP on HANA DB, you can work directly on the DB and
also use HANA CDS there. But then the CDS objects created are not managed
http://www.sapyard.com/abaponsaphanapartiv/
7/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
by the ABAP Dictionary meaning you cannot access them directly with Open
SQL and they are not TYPEs in the ABAP TYPE system.
Question: When should we use ABAP CDS and when should we use
HANA CDS?
Answer: If you run SAP HANA standalone or in a side-by-side scenario
(there is no ABAP stack on top) you cannot use ABAP CDS. You must use
HANA CDS.
136
Shares
If you have an ABAP stack on top of a HANA database (an AS ABAP uses the
HANA database as central database) then:
i) If you want to access the CDS entities in ABAP as data types or in Open
SQL or if you want to evaluate the CDS annotations in ABAP, you must use
ABAP CDS.
ii) If you do not want to access the CDS entities in ABAP, but you want to
transport and upgrade them like ABAP repository objects, you can use ABAP
CDS.
iii) If you do not want to access the CDS entities in ABAP as data TYPEs or in
Open SQL, you can use HANA CDS, which is better integrated into SAP
HANA. An access from ABAP is then possible using Native SQL (ADBC,
AMDP) only.
Question: Can we consume ABAP CDS natively in HANA?
Answer: Yes we can. For each CDS view a database view (SQL view) is created
in the database during activation. We can access that database view natively if
we want to. CDS table functions are managed by AMDP. The respective
database functions can also be accessed natively.
Question: Is it also possible to access the database views (generated by
having a corresponding ABAP CDS view) in HANA natively and
http://www.sapyard.com/abaponsaphanapartiv/
8/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
http://www.sapyard.com/abaponsaphanapartiv/
9/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
136
Shares
http://www.sapyard.com/abaponsaphanapartiv/
10/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
Now let us try to open the DDL source of the CDS in SE11.
136
Shares
http://www.sapyard.com/abaponsaphanapartiv/
11/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
136
Shares
Having one name is just not good enough in CDS; we need two names.
One name is for the SQL view that is going to be created in the dictionary
(the one we will be able to look at in SE11), and the other name we have is a
name for the CDS view entity, which is viewed and changed via Eclipse.
PS: We could name both the SQL view and the CDS view the same, but we
should not as they are different things, so the name should re ect the
difference.
SQL view is visible in SE11, however, we cannot edit it in SE11.
CDS View entity is the one we should refer to in SELECT statements in our
ABAP programs. Although we can use DDL SQL View in our programs, but
we should not.
http://www.sapyard.com/abaponsaphanapartiv/
12/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
Seeing a CDS View in SE11 is kind of a technical artifact and we should not
address the database view that is shown there in our ABAP programs. From
SE11 you can also navigate to the database object that is generated from the
de nition. This database object can even be accessed directly with Native SQL.
This means we can access our CDS Views directly in ABAP programs or from
elsewhere. For evaluating the semantic properties (annotations) of a CDS
View (stored in system tables) we should use an appropriate API
(CL_DD_DDL_ANNOTATION_SERVICE if available in your system).
The database views created from the CDS source code are merely for technical
reasons. The CDS source code and the CDS entity de ned there should be
the real thing.
Question: What are the Salient Features of CDS?
1. Semantically Rich Data-Models
2. Domain speci c languages (DDL, QL, DCL)
3. Declarative, close to conceptual thinking
4. CDS is completely based on SQL
5. Any Standard SQL features (like joins, unions, built-in functions) is
directly available in CDS
6. Fully Compatible with Any DB
7. Generated and managed SQL Views
8. Native integration in SAP HANA
http://www.sapyard.com/abaponsaphanapartiv/
13/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
http://www.sapyard.com/abaponsaphanapartiv/
14/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
CDS view (de ned in a so-called DDL source) has to be transported via the
ABAP Change and Transport System (CTS). Moreover, the functionality
provided by CDS views can be used on all SAP supported databases, we dont
have to worry when transporting these objects in a heterogeneous system
landscape.
CDS views are entities of the ABAP CDS in the ABAP Dictionary that are
much more advanced than the classical SE11 views. We can in uence CDS
views with parameters that can be used at different positions of the DCL. As
136
Shares for classical SE11 views, for a CDS View, a platform dependent runtime object
is generated at the database that we can examine in SE11. When accessing a
(CDS) view with Open SQL (i.e ABAP), the database interface accesses this
runtime object. A CDS view is created with a source code based editor in Eclipse
using a DDL (which ha nothing to do with SQLScript).
For technical reasons, from the source code a classical DB view is generated in
SE11 that we can access like any classical view, but we shouldnt. Instead, the
so-called CDS entity should be accessed because it carries more meaning
than the mere technical DB view and involves new kind of client handling.
PS: In an upcoming release, the direct access to the DB view of a CDS view will
be declared as obsolete. So, better not to use them if it can be avoided.
We use CDS to model large parts of our application in the Dictionary and use
simple Open SQL SELECTs in ABAP for relatively straight joins and
subqueries in ABAP. Some day Open SQL might have the same power like
CDS but it doesnt mean that those are redundant. Already before CDS, we
had the choice between creating a reusable view in SE11 or programming a
join in Open SQL in ABAP. As a rule of thumb, we created a view if it is used in
more than one program and programmed a join when we needed it only once.
That is very similar for CDS, but with much more possibilities for modeling
semantically rich models for reuse in ABAP programs.
http://www.sapyard.com/abaponsaphanapartiv/
15/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
136
Shares
If you want to get such useful articles directly to your inbox, please
SUBSCRIBE. We respect your privacy and take protecting it seriously.
If you liked this post, please hit the share buttons and like us on facebook.
Thank you very much for your time!!
Also, check our complete list of ABAP for SAP HANA Tutorials.
Source:
1. DEV200 Core Data Services TechEd 2015 session
2. Blogs and answers from SAP Expert Horst Keller
3. SAPInsider
4. GIThub
67
http://www.sapyard.com/abaponsaphanapartiv/
16/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
Related Posts:
136
Shares
Previous post
4 COMMENTS
Next post
http://www.sapyard.com/abaponsaphanapartiv/
17/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
Shares
Hello Nick,
Thanks for reading our Blogs.
SAP HANA Live uses native SAP HANA SQL views,so they are
maintained via HANA Studio. CDS views SAP HANA S/4HANA
Embedded Analytics is based on ABAP-managed core data
services (CDS) of the ABAP layer of SAP. S/4HANA. CDS views
can be maintained in ABAP for Eclipse.you can consume both
via the Fiori.
Regards,
Team SAPYARD
18/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
http://www.sapyard.com/abaponsaphanapartiv/
19/20
10/30/2016
ABAPonSAPHANA.PartIV.CoreDataServicesSAPYard
http://www.sapyard.com/abaponsaphanapartiv/
20/20