ABAP Core Data Services – Part 3(Virtual Data model types)

-

Table of Content:

S.NoTopics
1.Introduction
2.VDM View types
3.Analytics Data Category
4.More Blog’s (Follow)
5.Credits

This blog is continuation of my previous blog’s :
ABAP Core Data Services – Introduction (ABAP CDS view) in this detailed introduction is given about the ABAP Core Data services.
ABAP Core Data Services – Part 1 (ABAP CDS Entities) in this detailed introduction is given about the ABAP CDS Entities.
ABAP Core Data Services – Part 2 (Types of CDS views) in this detailed introduction is given about different types of ABAP CDS views.
Before, start reading this I would request you to go through above mentioned blog for better and smooth understanding.
I,hope you have got the basic understanding about ABAP CDS views. In this blog, we’ll see the different Virtual data model types in ABAP CDS views .
Let’s Start !!

Introduction

A Virtual Data Model (VDM) is a structured representation of HANA database views which was introduced to be used in SAP HANA Live for SAP Business Suite.It provides direct access to SAP business data using standard SQL or OData requests. The VDM exposes the Business Data of an SAP system as an Understandable, Comprehensive and Executable model for consumers in Transactional applications, Analytics, External interfaces fulfilling important product qualities.
VDM is intended to be interpreted by view browsers and other functionality which is based on the virtual data model.So, these views can be consumed directly by rich client UIs (such as HTML5, SAP BusinessObjects, and Excel) without any additional software layer (for example, ABAP application system) in between (two-tier architecture).
Now, to take advantage of powerful functionality of virtual data model in ABAP CDS views, SAP introduced @VDM annotations to define an ABAP CDS view which can be consumed and interpreted by Analytics engine used in different tools for Analysis. It offers additional features
Eg: Better Performance, Extensibility, Security and Privacy, Consistency as a reusable, stable and compatible platform for SAP internal Development, Partners, Customers thus increasing development efficiency and fostering ease of consumption.

VDM View types

The classification of VDM is used only for SAP internal structuring and interpretation of the CDS views. Releasing CDS views for customers and partners is controlled by additional internal classification of the views.
Different VDM view types are:
  1. Basic
  2. Composite
  3. Consumption

Basic View

A basic view is created on top of DDIC tables/views, which means only a basic view is a view which interacts with database for fetching data. The fetching of data directly from database results as core data for other type of view types without any data redundancies.
Data source for basic view is raw data directly from DDIC tables/views.
Syntax: @VDM.Viewtype: #BASIC

Composite View

A composite view is created on top of basic views, which means composite views doesn’t interact with database directly for data, but instead thorough dimension result set of basic views. The multiple basic views can be used with join / association for fetching data and doing calculations (eg:. using built-in-expressions and functions) on retrieved data  to consume in different analytics tools using consumption view.
Data source for composite view is basic views.
Syntax: @VDM.Viewtype: #COMPOSITE

Consumption View

A consumption view is created on top of composite view, which means consumption view doesn’t interact with DDIC tables/views or basic views. The consumption view is written on top of composite view which provides factual and cube data. This view is used to expose the data to different analytics tools (such as HTML, SAP BusinessObjects, Analysis for Excel, SAP Lumira, etc..) which helps to create reports and different visualization for presenting Business data.
Data source for consumption view is composite views.
Syntax: @VDM.Viewtype: #CONSUMPTION

We have already seen, different virtual data model view types that are used for Analytics purpose. But only using VDM view types is not just enough for consuming CDS view in analytics tools because till now we have just defined data model for CDS view, nothing related to type of data CDS view is returning. So, to let the Analytical manager know how to interpret each CDS entity we have to declare Data Category for each particular ABAP CDS views with VDM view type annotations.

Analytics Data Category

To enable the analytic manager for multidimensional data consumption, performing data aggregation, and slicing and dicing data. BI frontends like Design Studio and Analysis Office can consume the data via the analytic manager.
The different types of Analytics data category are:
  1. Dimension.
  2. Fact.
  3. Cube.
  4. Aggregation level.

Dimension

The view that represents master data is annotated as @ObjectModel.dataCategory: #DIMENSION. If we have to use any of the view for replication or for a query, we should use @Analytics.dataCategory: #DIMENSION.

Fact

The view represents transactional data (center of star schema). Usually, it contains measures. Typically, these views are necessary for replication, therefore, views listed as Fact data category should not be joined with master data views.
Syntax: @Analytics.dataCategory: #FACT

Cube
The Cube view (like #FACT) represents factual data, but cube view does not have to be without redundancy, which means joins with master data are possible. The consumption views are built on top of CUBE views, where data is replicated from facts.
Syntax: @Analytics.dataCategory: #CUBE

Aggregation Level

The view using data category as aggregation level indicates that CDS view is of type projection. For, this type of view analytics manager offers write-back functionality. In this type of view associations are not allowed and elements can be renamed.
Data source of this type of views is a CDS view with dataCategory = #CUBE, which supports Analytics.writeBack.className annotation.
Syntax: @Analytics.dataCategory: #AGGREGATIONLEVEL

Data CategoryRepresents Master dataRepresent Transaction dataCan be Joined with master dataOffers Write backContains Measure
Dimension
Fact
Cube
Aggregation Level


To keep the focus on core objective (Core Data Services) of this blog, I tried to make it as small as possible.
Suggestions and questions are welcomed !!

Follow:-


Thank you.

Credits:-

Assigned tags

View more...

Related Blog Posts

Related Questions

9 Comments
You must be Logged on to comment or reply to a post.
  • Author's profile photo Joachim Rees
    Joachim Rees
    January 15, 2018 at 3:32 pm
    Hey Tushar,
    thanks for sharing!
    I tried to map what you describe in theory with an actual example I came across today.
    I start with C_MaterialStockActual, which is the consumption view, and I turn the sequence you gave around, putting the Consumption view on the top of the list and the Basic-View on the bottom.
    -> This seems a better fit to me, as the Baisc-view reads from the database, and that is underneath everything else.
    So this is how I went exploring: Open C_MaterialStockActual in AdT, and then just see where it selects from – follow that path using the F3-key.

    This is the ‘stack’ that unfolds this way:

    C_MaterialStockActual (reads from: )
    I_MaterialStock (reads from: )
    I_MaterialStock_Aggr (reads from: )
    I_MaterialDocumentRecord (reads from: )
    MATDOC (-> the database table ).


    Her I show parts of the annotations, especially the @VDM.viewType:

    C_MaterialStockActual:
    @VDM.viewType: #CONSUMPTION
@Analytics.query : true

define view C_MaterialStockActual


    I_MaterialStock:
    @VDM.viewType: #COMPOSITE
@VDM.private: false
@Analytics.dataCategory:#CUBE

define view I_MaterialStock
  as select from I_MaterialStock_Aggr

    I_MaterialStock_Aggr:
    @VDM.viewType: #COMPOSITE
@VDM.private: false
@Analytics.dataCategory:#FACT

define view I_MaterialStock_Aggr

    I_MaterialDocumentRecord:
    @VDM.private: false
@VDM.viewType: #BASIC

define view I_MaterialDocumentRecord


    So I think I learned the following in addition to your blog:
    1. It’s no always exactly 3 levels (Basic, Aggregate, Consumption), it also can be more .
    2. “A composite view is created on top of basic views,” or on top of another composite view .

    Great to dig deeper in the big field of CDS-Views and to learn navigation my way around them !

Please support my work

Comments

Post a Comment

Popular posts from this blog

all user exit mv45afzz (implicit user exit )

-
MV45AFZZ this is included here all code put related to sales order creation while creating a sales order  va01 this exit trigger so as per your requirement we can write your code here I going to listed different type exit as per the real requirement you find the code and develop your business scenario INCLUDE MV45AFZZ . Modify Screen VA01/VA02/VA03 How to Activated and Deactivated Screen  Export Memory example While Creating a sales order  How to Call workflow While Creating a sales order  TYPES  :  BEGIN  OF  ty_vbak ,           KVGR1  TYPE  vbak - KVGR1 ,           KVGR2  TYPE  vbak - KVGR2 ,          END  OF  ty_vbak . DATA  :  ls_vbak  TYPE  ty_vbak . IF  sy - tcode  =  'VA02'  and  sy - uname  =  'FREDDIE' . BREAK freddie . *SELECT SINGLE KVGR1 KVGR2 *  FROM vbak *  INTO ls_vbak * WHERE vbeln = vbak-vbeln. * *IF vbak-KVGR1 <> ls_vbak-KVGR1 or vbak-KVGR2 <> ls_vbak-KVGR2. *  VBAK-FAKSK = '05'.
Read more

How to Give Dropdown in alv report in sap abap programming Language

-
   IF  p_fieldname  =  'REASONS' .     wa_fcat - f4availabl  =  'X' .    ENDIF .   PERFORM  dropdown_table  CHANGING  g_grid . FORM  dropdown_table  CHANGING  g_grid  TYPE  REF  TO  cl_gui_alv_grid .    DATA  : lt_dropdown  TYPE  lvc_t_drop  WITH  HEADER  LINE .    DATA :  gs_f4  TYPE  lvc_s_f4 ,         gt_f4  TYPE  lvc_t_f4 .    LOOP  AT  it_fcat  INTO  wa_fcat .      IF  wa_fcat - fieldname  =  'REASONS' .       wa_fcat - drdn_hndl  =  '1' .       wa_fcat - outputlen  =  20 .        MODIFY  it_fcat  FROM  wa_fcat .      ENDIF .    ENDLOOP . *CLEAR GT_F4. *  GS_F4-FIELDNAME  = 'REMARK'. *  GS_F4-REGISTER   = 'X'. *  GS_F4-GETBEFORE  = 'X'. *  GS_F4-CHNGEAFTER = 'X'. *  APPEND GS_F4 to GT_F4.    CALL  METHOD  g_grid -> register_f4_for_fields      EXPORTING       it_f4  =  gt_f4 .   lt_dropdown - handle  =  '1' .   lt_dropdown - value  =  'Loadability Issue' .    APPEND  lt
Read more

Long Text in input and output field in module pool

-
Image
display long text in input and output field then below code help you how to display long text your input and output fields in sap ************************************************************************ * Program Name      :  ZLONG_TEXT_EDITOR           Object ID:   p002    * * Description       :  Long text with function module                   * * Create Date       :  26.12.2018                                      * * FO Owner          :  Rohini kumar                                    * * Tech Owner        :  Rohini Kumar                                    * * Project Module    :  SD                                              * ************************************************************************ *                        Change Log                                    * ************************************************************************ *  REQ#         DATE         WHO            CHANGE_ID        DESCR     * *-------------------------------------------
Read more