SAP Community - BW Analytic Engine (OLAP)

Smart Queries for SAP Analytics Cloud with BW Live Connection

2019-11-13T21:10:52+01:00

One important aspect of the integration of SAP Analytics Cloud and SAP BW / BW4HANA is always the topic performance. With wave 19 we released a new feature especially for the BW Live connectivity. Officially the feature is called "Query Merging", but I thought "Smart Query" sounds far better...

Lets assume a very simple case:

In our example, we have three charts displaying:

Net Value by Product (Top 10)

Costs by Product (Top 10)

Net Value by Region (Top 10)

Without doing anything, this would result in three queries towards the SAP BW system.

Now with the new option of query merging, we can reduce the amount of queries.

First I open the Query Settings as part of my story...

.. and I then enable both options:

Enable Query Merge

Visualize Query Merge

.. and then i refresh my story.

All three charts are shown with a different color and there is a small comment in the bottom right corner for each chart, showing with with data request the data was retrieved. In my given example we still have three data requests - so we didn't improve.

Why ?

So lets look at the pre-requisites:

Queries contain the same dimensions with the same hierarchies and drill.

Queries use the same sorting and ranking.

Queries do not have an active threshold with threshold filters.

The widget does not have a local filter on a dimension that is also used in a restriction in SAP BW.

Queries are part of the same receiver group if they use linked analysis.

There is no widget filter on a secondary structure query.

The widget filter is not defined as complex tuple or range filter.

Presentation types are the same.

So in our example the second rule is why our three charts are not being merged, because we are using three different sets of ranking rules.

So lets remove the ranking from all our three charts.....

.... and we can see that the two charts that share the dimension are now part of the same data request, so instead of 3 requests we now are only using 2 requests.

When looking at this simple example the impact might not be so obvious, so lets put this into a perspective.

Lets assume we have a SAP Analytics Cloud Story with a total of 6 widgets and instead of running 6 data requests, we would be running 2 data requests with the Query Merging capability enabled.

Lets also assume that the SAP Analytics Cloud Story is being viewed by 100 people each morning.

Our old scenario:

100 Users x 6 requests = 600 requests

New scenario with Query Merging:

100 Users x 2 requests = 200 requests

I am sure your BW Administrator would appreciate this and your end users will as well ...

Merging SAP BW Queries Documentation

Configuration of FIORI Analytical App using SAP Smart Business KPI Modeller

2019-12-13T06:08:12+01:00

Hi Readers,

First of all, thank you very much for reading this blog. I hope it will be helpful for you.

In this blog, I am going to discuss the steps to create your first FIORI analytical app using SAP Smart Business KPI Modeller.

Before going to start let's understand what is FIORI Analytical App.

What is FIORI Analytical App?

Analytical apps are used to provide role-based real-time information about business operations. Analytical apps integrate the power of SAP HANA with SAP business suite. It provides real-time information from a large volume of data in the front-end web browsers.

Using Analytical apps, you can closely monitor Key Performance Indicators KPIs. You can perform complex aggregations and calculations of your business operations and react immediately as per the changes in the market condition.

SAP Fiori Analytical apps run on SAP HANA database and use Virtual data models.

There are two types of Analytical Apps −

SMART Business

Virtual Data Models

SMART Business

SAP Fiori smart business apps are used to monitor your most important KPIs in real-time and to make changes as per market conditions immediately.

Note − There are around 84 Analytical apps under this umbrella and out of these, you have 69 apps are smart business apps and rest 15 are Analytical Apps.

What is a KPI Modeler?

It is a tool used to model KPI and report tiles for monitoring the business data using Fiori Launchpad. You can define KPIs and reports to which you can apply different calculations and it enables you to make adjustments according to changing market conditions. You can configure drill-down views.

SAP HANA Live provides exceptional capability analytics for all business suite by enabling industry-standard access to SAP data through data models.

The data models are used for analytical purposes using views in the HANA database. The views from a virtual data model that a customer and partner can reuse.

Now, let's see the steps to follow to create a new KPI Report for any of your business processes.

1. Open your Fiori Launchpad, you will see KPI Modeller Tiles

2. Click on the Create KPI Tile

3. You should enter Title, Description, Choose Goal Type from options Maximizing, Minimizing or Range

4: You should select SAP HANA View from the Value Help

5. Select the HANA View and then search for OData Service from OData Service Value help.

6. Now, select the respective OData Service and respective Entity Set.

7: Now, Search for Value Measure from Measure Value help.

8. Click on Activate and Add Evaluation

9. Once clicked on Activate and Add Evaluation, the Add Evaluation page opens up. On this page some of the fields are prefilled. This data is fetched from KPI.

10. Select a few Additional Measures

11: Now, Select optional Filters

12: Select Value Type

13: You can also Enter Target, Threshold, and Trend if required

14: Now, click on Activate and Configure Tile

15: Once you clicked on Add Tile, Add Tile page opens up, you can choose any tile type as per your requirement.

16: After clicking on Save and Configure Drill Down, the Drill-Down Configuration Details page will come up.

Now, you have to select an Evaluation and click on Configure Button.

17: Now, select Measures and Dimensions.

18: You can select the Visualization Type and Save View

19: Save the new Configuration

20: Now, you can go to Tile Catalog in Fiori Launchpad and search for the KPI Tile that was created and Add Tile to Group by Clicking on ‘+’ icon

That's it!!! Your new KPI report will be available on your Fiori Launchpad.

Thanks & Regards,

Rahul Patra

ASUG BI and DW Upcoming Influence Councils

2020-01-20T18:26:09+01:00

Some of you might already be aware what ASUG Influence Councils are and some of you might be new to the topic.

An ASUG Influence Council is basically your opportunity to "make your voice heard" and present any requirements and suggestions to the product team from SAP. In addition, you are not doing this just by yourself, but instead you are combining your voice with several other customers together, which then provides it an even stronger voice.

In case you are interested to join some of these Influence Council, I highly recommend that you join these public calls to hear more about the scope and what type of profile the product team is looking for.

February 03 - Data Warehouse Cloud Influence Council 2020 Launch

February 11 - Enterprise Data Warehouse Influence Council 2020 Launch

February 20 - SAP BusinessObjects BI Platform Influence Council 2020 Launch

February 24 - SAP BusinessObjects Web Intelligence 2020 Launch

February 24 - SAP Analytics Cloud Integration with BW Influence Council 2020 Launch

March 12 - SAP Analysis for Microsoft Office Influence Council 2020 Launch

March 16 - Mobile Analytics Influence Council 2020 Launch

S/4HANA Analytics: BW queries with or without BW modeling (comparison)

2020-05-06T15:42:03+02:00

Since I am a proponent of using BW queries even directly in S/4HANA Embedded Analytics, I have done some research whether stirring BW objects into the picture has any major down-sides.

There are two major scenarios of virtual data consumption in BW:

A BW Query directly on a CDS view with @analytics.dataCategory: #CUBE. I will call it CDS scenario further in the text.

A BW Query on a Composite Provider that has an OpenODS that is based on DataSource that is based on CDS (mentioned above). I will call it HCPR scenario.

We all realize that CDS-scenario is much simpler, robust, extendable, easier to support and so on. But... we have some BW fans amongst us that would maybe like to union the live data with something else like benchmarks, external system data, etc., so we have certainly valid reasons for HCPR scenario.

Before we start doing any modeling, let us just measure if there is a penalty of using the triple-sandwich of BW objects. For the sake of real head-to-head comparison let us eliminate various factors that may influence performance like network time (if we have separate instances), additional data union operations, etc. I take just a plain and simple example of standard BW technical content consumed in two different ways. (Don't blame me for using BW technical content here, it is written in the same ABAP CDS nowadays and works in exact same fashion as S/4HANA CDS views).

So, here we go, 2 queries with exact same set of fields built on top of CDS-view directly on one end and HCPR on the other.

I execute (yes, in RSRT) three very basic tests:

Very aggregaed, i.e. just Key Figures and nothing in drill-down

Slightly aggregated, i.e. just an Object is in drill-down

Full details, i.e. all 10 characteristics are in rows

In addition, I execute it on two very different data-sets, 1 being 20k records, the other – 1,6 mil (filtered to 0,4 mil in Query), so we see if there is growth related to data-volume.

Scenario	Small data-set	Observation	Big data-set	Observation
Very aggregated		Nothing major, but Data Manager seems taking +45% more time in HCPR case HCPR also implies query regeneration even though I generated it before execution (1/10^th of a second)		No major impact
Slightly aggregated		Nothing major, but Data Manager seems taking +25% more time and OLAP Data Transfer +70% more time in HCPR case HCPR also implies query regeneration even though I generated it before execution (1/10^th of a second)		No major impact
Full details		OLAP Data Transfer +8% Data Manager +6%		The cumulative effect of DM and OLAP in HCPR case is +20 seconds (15% increase), which is a significant penalty

* a small remark that I am doing it on a system where there are 1,6 mil records

So, to draw a conclusion – I’ve never noticed HCPR-based solution taking over the CDS

There seems to be insignificant penalty for using HCPR in aggregated data-sets, so it is a viable way forward from performance point of view. For bigger, more detailed queries I would do the exact measurement and see if user-expectations will be met.

If you would like to reproduce the same scenario, you may grab a BW system and work with Technical Content, e.g. OLAP statistics CDS views. I used RV_C_OlapStatACube

Getting BEx query ID in customer exit for authorization variables

2020-05-29T17:30:36+02:00

Introduction:

The importing parameter "I_S_RKB1D"(query attribute) is not getting filled for authorization variable(I_STEP=0) in the FM "EXIT_SAPLRRS0_001"(FM for customer exit variable). Recently I have faced this issue in our system and came up with a workaround and thought to share it so that it will be helpful for someone who is having the same issues.

Problem Statement:

In customer exit/BAdI for BEx Variable, we often have requirements to get the query related attributes (e.g., ID of the query) so that we can mold our code accordingly. We already have an importing parameter(I_S_RKB1D in case of customer exit) for the query attributes in the FM/Class of the Customer exit/BAdI respectively. The importing parameter works fine for customer exit variables for I_STEP=1 and 2(work fine in the sense, the query id is filled in the imparting parameter). However, for authorization variables(that is when the value of I_STEP is 0), the values are not filled in the query attributes and remain blank.

Below screenshot for reference. We can see the variable "I_VNAM" which have the value for authorization variable name, "I_STEP" which have the value "0" which is for authorization check. We can see the value of the variable "I_S_RKB1D-COMPID" is empty, which should have the value of the query being run.

(The above screenshot is from the function module "EXIT_SAPLRRS0_001" which belongs to the customer exit "RSR00001"-BI: Enhancements for Global Variables in Reporting).

We can see in the below screenshot, the value of I_STEP is "2" and the query id is populated successfully in the variable "I_S_RKB1D-COMPID".

So, to summarize the issue, the query ID is not getting populated for Authorization Variable (I_STEP=0) but, it is working fine for the customer exit variable(I_STEP =1 or 2).

Proposed Solution:

There is a standard class "CL_RSBOLAP_SELECTION_OBJECT" which is responsible for calling the customer exit/BAdI for authorization/customer exit variable of BEx. The class has an attribute "IF_RSBOLAP_MD_SELECTOR~N_S_COMPKEY" which stores the query attributes of the query which is being run.

So, we can take the help of the "static attribute" of Object-Oriented Programing. We will create a custom class and create a static attribute in the class for the query id. We set the value of query attribute from this class using a "Pre-exit" in the method. Then inside the customer exit/BAdI, we can use our custom class to get the query Id.

Those who are new to Object-Oriented programming, static attributes are the attributes of the class which are not associated with the object of the class directly and exists on per class basis. Which means, there will be only one instance of the attribute for one class and these attribute can be accessed without creating the object of the class. For more information, please refer to the below link.

https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abapclass-data.htm

As mentioned already, we will be creating a pre-exit in the class of the method. Pre-exit is nothing but the enhancement technique, where we can associate our code to the class which will be called automatically by the system whenever that particular method is called anywhere. As this is the pre-exit, so our code will be called followed by the code of the standard method. For more information, please refer to the below link

https://wiki.scn.sap.com/wiki/display/ABAP/Enhancement+Framework+-+Class+Enhancements+-+Pre-exit,+Post-exit+and+Overwrite-exit+methods+-+Concept+and+Simple+Scenarios

So, let's start.

Step 1: Creation of custom class

Let's create a custom class "ZCL_BW_QUERY_NAME". This class will be used to get the Query Id. This class will have below component:Attribute:

MV_QUERY_ID - To store the query Id

Methods:

SET_QUERY_ID - Sets the query ID - This will be used in the Pre-exit of the method of class "CL_RSBOLAP_SELECTION_OBJECT" to set the value

GET_QUERY_ID - Gets the query ID - This will be used in customer exit/BAdI to get the query id

Method: SET_QUERY_ID

  METHOD set_query_id.

    "Set the query id

    mv_query_id = im_v_query_id.

  ENDMETHOD.

Method: GET_QUERY_ID

  METHOD get_query_id.

    "Return the query id

    rt_v_query_id = mv_query_id.

  ENDMETHOD.

Step 2: Creation of pre-exit for setting the value of Query in the custom class

To create the Pre-exit go to the class "CL_RSBOLAP_SELECTION_OBJECT" in class builder(t-code: SE24) and click on "Class--> Enhance" in the menubar.

If you have already an enhancement implementation, then the created enhancement implementation will be shown in the pop-up. Select the implementation to proceed. In my case, there is no existing implementation, so I will go ahead and create one.

Once the Enhancement Implementation is created, place the cursor on the method "CREATE_OLAP_OBJECT". Then create a pre-exit method.

Please click on "Yes" in the pop-up if the pop-up is displayed.

Now click on the button shown in "Pre-exit" column of the method "CREATE_OLAP_OBJECT".

Please add below code inside the pre-exit of the method method

METHOD IPR_ZEHN_QUERY_DETAILS~CREATE_OLAP_OBJECT.

*"------------------------------------------------------------------------*

*" Declaration of PRE-method, do not insert any comments here please!

*"

*"methods CREATE_OLAP_OBJECT

*"  importing

*"    !I_AUTHCHECK type RS_BOOL

*"  raising

*"    CX_RSBOLAP_UNKNOWN_DATA_PROV .

*"------------------------------------------------------------------------*

  "Set the query ID  

  zcl_bw_query_name=>set_query_id( im_v_query_id = core_object->if_rsbolap_md_selector~n_s_compkey-compid ).

ENDMETHOD.

So, we have created the custom class and set the query Id. We are all done. No kidding. Now we can use our method "GET_QUERY_ID" of our class "ZCL_BW_QUERY_NAME" inside customer exit to fetch the query id.

Step 3: Get the query id in customer exit

Now, let's go our customer exit for BEx Variable to use our class to get the query id. Let's

IF i_s_rkb1d-compid IS INITIAL.

  "Get the query id

  i_s_rkb1d-compid = zcl_bw_query_name=>get_query_id( ).

ENDIF.

We can call the method "GET_QUERY_ID" of the class "ZCL_BW_QUERY_NAME". We can see we get the name of the query in the which is being run. Please note the value of "I_STEP" is "0", which confirms we are dealing with the authorization variable.

Conclusion:

As we saw, we had an issue to get the Query Name for the authorization variable(I_STEP=0). The I_S_RKB1D-COMPID was blank. However, for I_STEP=1 or 2, there is no issues and the variable "I_S_RKB1D-COMPID" is filled correctly. To overcome the issue, we have created a pre-exit in the method "CREATE_OLAP_OBJECT" in the class to set the query id in the custom class "ZCL_BW_QUERY_NAME". Then, we used the class "ZCL_BW_QUERY_NAME" in the customer exit(for BAdI also it will work fine) to get the name of the query. Cheers!

How to Recover Objects not visible within InfoArea

2021-12-31T09:20:53+01:00

In this Blog Post we will understand how to handle a situation when Objects are not visible within InfoArea.

Problem Statement :

Often when there are Role level and authorization related Changes from Basis or Security Team on User ID, User's might not be able to see the Modelling Objects and Query related Elements within the InfoArea and it creates a kind of confusion when no object is visible to work upon which used to exists before.

This issue often occurs due to Shared Buffer that exists on Application Server.

Lets try to Understand how we can resolve this Issue.

Solution :

Go to T-Code : RSOSM, which is often used for BW Search for SAP HANA Maintenance.

2. You will get the above Screen , Scroll to the bottom of the screen and click on "Configure BW Search" , You will be presented with the below Screen.

3. Once you are within "Configure BW Search" Section, You can see the status of your Shared Buffer as "Shared Buffer is Filled" and a Delete Icon besides that Status.

4. Click on that Delete Icon , it will delete your Shared Buffer and the Status will be changed to "Shared Buffer is not filled" as below.

5. Now , go back to your InfoArea and hit Refresh , You will be able to see all your Modelling Objects and Query related Elements back within InfoArea.

Conclusion:

By Following the above steps you will be able to clear up your shared buffer and able to see the missing Objects back within your InfoArea.

— Sources of the pictures are screenshots I have taken from SAP system and no image is taken from the internet.

Hope the above Information added a bit of value to your time and knowledge .

If you enjoyed reading it do give it a Like and would be happy to read your feedback in the comments section.

Obtaining MDX data in SAPUI5 via XMLA

2022-02-12T15:06:04+01:00

1. Introduction

SAP UI5 developers often struggle with obtaining data from the backend. The common way to access backend data is the OData protocol.

The OData interface provides such advantages as selecting. binding, filtering and sorting data.
On the other hand, there are some flaws in OData protocol as to handling OLAP Data for analysis.

MDX (Multidimensional Expressions) has established itself as a common query language for OLAP data. XMLA (XML for analysis) is an open standard for requesting OLAP Data with MDX.

Below find my description of how MDX Data can be obtained using XMLA in javascript for SAP UI5.

SAP offers the ISCF node /sap/bw/xml/soap/xmla/ as a web service data provider interface.

This web service offers two methods: Execute and Discover. In the following article is the focus on the Execute Method.

A JQuery post request will send the MDX query envelop in a XML structure as a web service request.

2. Create and test the MDX Query

Transaction MDXTEST allows us to create, test and execute a MDX Query.

The MDX query can be directly executed.

Execution of MDX Query

In this example, I used a Query which is provided in the trial SAP 7.52 Developer Edition.

https://developers.sap.com/trials-downloads.html?search=7.52

MDX example

SELECT

      NON EMPTY

        { [48CSWO6CA6TXXHDU2Q35OLJW0].Members }

      ON COLUMNS,

      NON EMPTY

        { [0D_FC_COUN                    0D_FC_COUN_H001].Members }

      DIMENSION PROPERTIES

        LEVEL_NUMBER

      ON ROWS

      FROM

        [0D_FC_C02/0D_FC_AE_EOIBV_Q001]

Key Figures are selected in the columns, the Country hierarchy is selected in the rows.
Additionally the property of the hierarchy level is included in the row dimension.

3. Preparing the MDX Statement for the XMLA call

The MDX statement needs to be embedded in a xml structure for the web service post request.

    var _sRequest = `

    <Execute>

      <Command>

        <Statement>

          ${_sMdx}

        </Statement>

        <Properties>

          <PropertyList>

            <Format></Format>

          </PropertyList>

        </Properties>

      </Command>

    </Execute>`;

The webservice request will be initialized by the JQuery post request to the endpoint.

 $.post("/sap/bw/xml/soap/xmla/Execute",_sRequest , _fProcessData);

4. Processing the XMLA response

_fProcessData is the callback Method for processing the response of the request.

The response can be analysed in the debugger.

From the response, the output in Axis0, Axis1 and CellData is relevant to obtain the MDX data..

Axis0 delivers the columns Information about the key figure.
The element Caption contains the key figure name in the text node.

Axis1 contains the rows with the requested attribute of the hierarchy level of the row dimension.
The first attribute of the member, here "Hierarchy" contains the technical name of the row column.

Axis 1

At first the response for the root element needs to be checked. If this element is not present, it indicates an error present. The error message will be passed in the rejection of the promise.

      var _oRoot = oData.querySelector("ExecuteResponse>return>root")

      if(!_oRoot){

            debugger;

       var _sError =

          oData.querySelector("Error")?.getAttribute("Description") || 

                "undefined Error";

 

       _fReject(_sError)

       return;

      }

Column nodes will be extracted from the Axis0 and the row nodes from Axis1

_ColumnNodes = _oRoot.querySelectorAll("Axes>[name='Axis0']>Tuples>Tuple");

_RowNodes    = _oRoot.querySelectorAll("Axes>[name='Axis1']>Tuples>Tuple");

Data nodes are extracted from CellData

_DataNodes =  _oRoot.querySelectorAll("CellData>Cell");

The rows of the output table will be determined from the row nodes, including the requested properties like "hierarchy level". We assume that the properties always occur starting from position 6 from the child nodes. If the technical name (remember 1. attribute of Member) contains blanks, replace them with one underscore.

      _RowNodes.forEach(pRow=>{

        let _oMemberNodes = pRow.querySelectorAll("Member")

        let _aRow = [];

        _oMemberNodes.forEach(pMember=>{

          let _sName = pMember.attributes[0].value.replace(/\s+/g,"_");

          _aRow[_sName] = pMember.querySelector("Caption").textContent;

          pMember.querySelectorAll(":nth-child(n+6)")

          .forEach(pProperty=>_aRow[_sName+pProperty.nodeName] = pProperty.textContent);                  

        })

        _aRowName.push(_aRow);

      });

Keyfigures will be determine by text node of the caption element.

      _ColumnNodes.forEach(pRow=>{

        let _oMemberNodes = pRow.querySelectorAll("Member")

        _oMemberNodes.forEach(pMember=>{

          _aColName.push(pMember.querySelector("Caption").textContent);

        })

      });

Finally the data has to be divided between the rows and columns

      _iCntRow = _aRowName.length;      

      _iCntCol = _aColName.length;

      

      _DataNodes.forEach((pData,pIndex)=>{

        let _sValue = pData.querySelector("Cell>Value").textContent;

        let _iRow = Math.trunc(pIndex / _iCntCol)

        let _iCol = pIndex % _iCntCol;

        _aRowName[_iRow][_aColName[_iCol]] = _sValue

      });

5. Binding the OLAP output to the Datamodel

As a result a promise is returned. Data from this promise can be bound to the model.

    this.getMdxData(this.getMdx())

    .then(aData=>{

      this.getView().getModel("viewModel").setProperty("/mdxData",aData);

    })

    .catch((oError)=>{

      debugger

    })

5.1 Result of the MDX Query in SAP UI5

After obtaining data from the XMLA web service, it can be bound directly to a table.

Final result

6. Conclusion

XMLA enables SAP UI5 developers to benefit from the dynamics of
Multidimensional Expressions (MDX).

Multidimensional Expressions (MDX) is the query language you use to work with and retrieve multidimensional data. This includes the definition of calculated members, named sets, scoped assignments and key performance indicators (KPIs).

MDX offers the flexibility to fetch data, pivot data in dynamic structures based on your needs,
without restriction of structured data types in the backend.

With MDX you use the flexibility of your multidimensional OLAP queries.

Thank you for reading this blog post. I want to encourage you to share your knowlege about SAPUI5 using this tag link https://answers.sap.com/tags/500983881501772639608291559920477

Appendix: Project Code

Three files are required to test the project_

zxmla/index.html
zxmla/Test.view.xml
zxmla/Test.controller.xml

File: zxmla/index.html



<!DOCTYPE html>

<html>

   <head>

      <meta http-equiv="X-UA-Compatible" content="IE=edge">

      <meta charset="utf-8">

      <title>XMLA-Test</title>

      <script

      

         id="sap-ui-bootstrap"

         src="resources/sap-ui-core.js" 

         data-sap-ui-theme="sap_bluecrystal"

         data-sap-ui-libs="sap.m"

         data-sap-ui-compatVersion="edge"

         data-sap-ui-preload="async"         

         data-sap-ui-resourceroots='{

            "zxmla": "./"

         }' >

      </script>

      <script>

         sap.ui.getCore().attachInit(function () {

            sap.ui.xmlview({

               viewName : "zxmla.Test"

            }).placeAt("content");

         });

      </script>

   </head>

   <body class="sapUiBody" id="content">

   </body>

</html>

File: zxmla/Test.view.xml



<core:View xmlns:core="sap.ui.core" xmlns:mvc="sap.ui.core.mvc" 

   xmlns="sap.m"

   controllerName="zxmla.Test">



  <Table id="idProductsTable" items="{viewModel>/mdxData}">

    <headerToolbar>

      <Toolbar>

        <content>

          <Title text="Products" level="H2"/>

          <ToolbarSpacer />

         <Button text="Go" press=".onPress"/>

        </content>

      </Toolbar>

    </headerToolbar>

    <columns>

      <Column><Text text="Level" /></Column>

      <Column><Text text="Land" /></Column>

      <Column><Text text="konsolidiertes Netto" /></Column>

      <Column><Text text="netto Umsatz" /></Column>

    </columns>

    <items>

      <ColumnListItem>

        <cells>

           <Text text="{viewModel>0D_FC_COUN_0D_FC_COUN_H001LEVEL_NUMBER}" />

           <Text text="{viewModel>0D_FC_COUN_0D_FC_COUN_H001}" />

           <Text text="{viewModel>Konsolidierter Netto}" />

           <Text text="{viewModel>Nettoumsatz}" />

        </cells>

      </ColumnListItem>

    </items>

  </Table>

</core:View>

File: zxmla/Test.controller.js



sap.ui.define([

     "sap/ui/core/mvc/Controller",

    "sap/ui/model/json/JSONModel"

  ], function(Controller, JSONModel) {

  "use strict";

  

  return Controller.extend("zxmla.Test", {





  onInit: function() { 

    var _oModel = new JSONModel({mdxData: []});

    this.getView().setModel(_oModel, "viewModel");

  },

  

  onPress: function(oEvent){

    this.getMdxData(this.getMdx())

    .then(aData=>{

       debugger

      this.getView().getModel("viewModel").setProperty("/mdxData",aData);



    })

    .catch((oError)=>{

      debugger

    })

  },

 getMdxData: function(sMdx){

    var _fResolve, _fReject, 

        _oPromise = new Promise((resolve,reject)=>{

        _fResolve = resolve;

        _fReject = reject;

        });

    var _sMdx = this.getMdx();

    var _sRequest = `

    <Execute>

      <Command>

        <Statement>

          ${_sMdx}

        </Statement>

        <Properties>

          <PropertyList>

            <Format></Format>

          </PropertyList>

        </Properties>

      </Command>

    </Execute>`;

    

    var _fProcessData = function(oData, sStatus){

    

      var _oRoot = oData.querySelector("ExecuteResponse>return>root")

      if(!_oRoot){

            debugger;

       var _sError =

          oData.querySelector("Error")?.getAttribute("Description") || 

                "undefined Error";

 

       _fReject(_sError)

       return;

      }



      var _aColName = [], _iCntRow = 0, _iCntCol = 0;

      var _aRowName = []

      var _ColumnNodes =

        _oRoot.querySelectorAll("Axes>[name='Axis0']>Tuples>Tuple")

      var _RowNodes = 

        _oRoot.querySelectorAll("Axes>[name='Axis1']>Tuples>Tuple")

      var _DataNodes =  _oRoot.querySelectorAll("CellData>Cell")

    

      _RowNodes.forEach(pRow=>{

        let _oMemberNodes = pRow.querySelectorAll("Member")

        let _aRow = [];

        _oMemberNodes.forEach(pMember=>{

          let _sName = pMember.attributes[0].value.replace(/\s+/g,"_");

          _aRow[_sName] = pMember.querySelector("Caption").textContent;

          pMember.querySelectorAll(":nth-child(n+6)")

          .forEach(pProperty=>_aRow[_sName+pProperty.nodeName] = pProperty.textContent);                  

        })

        _aRowName.push(_aRow);

      });



      _ColumnNodes.forEach(pRow=>{

        let _oMemberNodes = pRow.querySelectorAll("Member")

        _oMemberNodes.forEach(pMember=>{

          _aColName.push(pMember.querySelector("Caption").textContent);

        })

      });

      

      _iCntRow = _aRowName.length;      

      _iCntCol = _aColName.length;

      

      _DataNodes.forEach((pData,pIndex)=>{

        let _sValue = pData.querySelector("Cell>Value").textContent;

        let _iRow = Math.trunc(pIndex / _iCntCol)

        let _iCol = pIndex % _iCntCol;

        _aRowName[_iRow][_aColName[_iCol]] = _sValue

      }); 

      debugger

      _fResolve(_aRowName)

      // check _aRowName

    };

  

  $.post("/sap/bw/xml/soap/xmla/Execute",_sRequest , _fProcessData);  

  return _oPromise  

  },

    

  getMdx: function(){

    var _sMdx =

    `SELECT

      NON EMPTY

        { [48CSWO6CA6TXXHDU2Q35OLJW0].Members }

      ON COLUMNS,

      NON EMPTY

        { [0D_FC_COUN                    0D_FC_COUN_H001].Members }

      DIMENSION PROPERTIES

        LEVEL_NUMBER

      ON ROWS

      FROM

        [0D_FC_C02/0D_FC_AE_EOIBV_Q001]`

     return  _sMdx;

  }



  });

});

Embedded Analytics with ABAP Cloud – The Multidimensional Cube (Part 2)

2023-03-31T03:23:36+02:00

Cheers ABAP folks!

The multidimensional cube view is the heart of the analytical model in ABAP CDS. In this blog post, I want to give you an insight into the modeling patterns of analytical cube views and their role within the ABAP Application Server.

New to analytics? Then I urgently recommend that you read the previous part of this blog post series: Embedded Analytics with ABAP Cloud – A Brief Overview (Part 1)

What Is a Multidimensional Cube?

A multidimensional cube view spans up all the dimensions that exist for a specific data set to which an analytical reporting is applied. A sales order, for example, may contain dimensional attributes such as an order date, an associated product, as well as a business partner reference. Querying the multidimensional cube with parameterization of specific dimensions returns an aggregated result for the matching cells that represent a measure, e.g. the turnover, in the multi-dimensional model:

f(Dimension 1, Dimension 2, Dimension 3) -> Measure



Example: f('Targot Corp.', '2023-02-25', 'Lemonade') -> turnover of this particular company

Pruning single dimensions when querying a multidimensional data set leads to the aggregation of the pruned dimension:

f(Dimension 2, Dimension 3) -> Aggregation of Measure over Dimension 1



Example: f('2023-02-25', 'Lemonade') -> sum of turnovers of all companies

Based on this, a multidimensional cube always provides the overall data basis for your analytical reporting. This can include defining foreign key relationships to dimensions based on dimensional attributes for further data exploration, defaulting for aggregations, and defining text relationships for labeling your attributes.

Multidimensional Reporting on Transactional Data

Ok, enough theory. Let’s get concrete: Imagine you run a company that ships soft drinks to retailers, and you have the following given transactional data model: A sales order is defined at the header level with references to the paying business partner, the business partner to whom the products are to be shipped, and an order date. In addition, each sales order can consist of multiple sales order items that have priced products, as well as a quantity assigned. Additionally, each sales order must be paid for. All these details are represented by different CDS entities that are linked by a relational data model.

The Transactional Model - Represented as Relational Data Model

In the corresponding transactional UI service, all this relational data is properly joined so the transactional business user can quickly act on specific sales orders. However, it seems a bit challenging to get a summary of last quarter’s sales with this data representation, doesn’t it?

The Transactional Model - User Interface

Preparing your Data Model Is Key

Therefore, it is recommended that you prepare your transactional data model before building an analytical model on top of it. I’ll show you how to do this.

Identify Relevant Data Sources

First, ask yourself: What are the relevant metrics that I want to report on to best run my business? In our current transactional sales order model, there are several possible analytical use cases. Let’s focus on reporting on the revenue of sales order items sold and the payment history. The following relational CDS entities are involved in this reporting:

Sales Order Item(s)

Payment(s)

Identify Relevant Relationships

Isolated reporting on these CDS entities would be easy to implement but wouldn’t provide much value to our business. Therefore, it's essential to identify the relevant relationships between these CDS entities and to take CDS entities in between into the reporting scope. The following CDS entity is added to our reporting scope:

Sales Order(s)

Span up Multidimensional Data Basis

Working at a conceptual level is certainly fun for all the theorists out there. However, at this point we need to hit the keys and span up our multidimensional data model directly on top of our relational data model. To do this, it's important to:

Preserve the unique keys across all involved CDS entities

Unite your measure-based data sets by using UNIONs in CDS entities

Resolve to-many-relationships by denormalization via dimension-based relations

In our example, the plain multidimensional data basis could be achieved with the following implementation of a CDS entity:

@EndUserText.label: 'Sales Order Cube Basis'

define view entity P_DD_TSM_ANA_SALESORDER

as select from sdd_tsm_ana_soi                 as SalesOrderItem

   left outer join SDD_TSM_ANA_SO              as SalesOrder

     on SalesOrder.sales_order_id = SalesOrderItem.sales_order_id



{

  key SalesOrder.sales_order_id                  as SalesOrder,

  key SalesOrderItem.sales_order_item_id         as SalesOrderItem,

  key abap.raw'00000000000000000000000000000000' as Payment

}



union all select from SDD_TSM_ANA_PAYM         as Payment

left outer join     SDD_TSM_ANA_SO             as SalesOrder

   on SalesOrder.sales_order_id = Payment.sales_order



{

  key SalesOrder.sales_order_id                  as SalesOrder,

  key abap.raw'00000000000000000000000000000000' as SalesOrderItem,

  key Payment.payment_id                         as Payment

}

This CDS view helps to span up the data basis for our multidimensional reporting. Proper key handling is essential here. Further attributes can be added later in the cube again. Key elements that do not belong to the reported data set are initialized with corresponding default values. The result of a data preview should then look like the following picture:

Data preview of the cubes data basis

Each data record contains a reference to either a concrete sales order item or to a concrete payment. Each record also contains a reference to a specific sales order header.

Slice and Dice Your Cube

After preparing our data basis, we now have a fine-granular reporting of all available data records that can be aggregated safely by the HANA engine without counting any measure twice. To design a multidimensional cube, we now need to:

Classify the cube view as such

Introduce measures, which are used for aggregations

Introduce dimensions, which are used for grouping based on drilldowns

Definition of a Cube

The cube simply selects from our prepared data model and creates joins to the original data sources to access further attributes. Don’t worry about performance: These additional joins are optimized by the HANA engine anyway. Just be sure to flag your cube with the annotation @analytics.dataCategory: #CUBE.

Measures

Next, add all measure-like fields to your cube that you're interested in for your analytical reporting. Measures are identified by their numeric data type, as well as by their capability to be aggregated by default, also called standard aggregation. This property can be set with the annotation @Aggregation.default.

Please consider the following recommendations for measures:

Do	Measures should be added to the cube if aggregated reporting is required for them.
Do	Aggregations are defined on element level for measures only.
Do	Aggregations are defined with annotation @Aggregation.default.
Do	Supported default aggregations on cube level are #SUM, #MIN, #MAX. Other aggregations need to be defined in concrete analytical queries.
Don't	Calculated measures based on formulas shouldn't be introduced in the cube, but in the analytical query on top.

Dimensions

To fine-tune your reporting, it is mandatory to define dimensions in your cube, for example, to group aggregated measures based on the characteristics of a data record. Dimensions are modeled either as foreign key fields, such as a business partner ID, or as pure attribute, such as an order date. Foreign key fields should also be linked via an association to the corresponding dimension view to span up the analytical star schema around your cube. This gives you further possibilities to deep dive into your analytical model at the query level.

Please consider the following recommendations for dimensions:

Do	Dimensions should be added to the cube if drill downs are to be applied.
Do	Dimensions may be represented by a dedicated dimension view associated with your cube.
Do	Be sure to link such an association with annotation @ObjectModel.foreignKey.association.

Special Case: Dimeasures

There may be use cases where some attributes need to represent a measure in one analytical reporting, but also a dimension in another one. Ok – I’ll be honest – Dimeasure is not an official term, but I think you know what I mean, right? Like calculating the average response time of incident processing based on a timestamp field, as well as using the same timestamp field for grouping the results by month. In such a case, make sure to simply introduce the field twice in your cube view. One with a measure-like flavor, the other one with a dimension-like flavor.

TL;DR – Just Give Me Some Coding

The result of an analytical cube could look like the following:

@Analytics.dataCategory: #CUBE

define view entity I_DD_TSM_ANA_SALESORDERCUBE

  as select from   P_DD_TSM_ANA_SALESORDER          as SalesOrder



    left outer join I_DD_TSM_ANA_SALESORDERITEM     as SalesOrderItem

       on SalesOrder.SalesOrderItem = SalesOrderItem.SalesOrderItemId



    left outer join I_DD_TSM_ANA_PAYMENT            as Payment      

       on SalesOrder.Payment        = Payment.PaymentId



    association [0..1] to I_DD_TSM_ANA_BUPA         as _Buyer                      

       on $projection.Buyer         = _Buyer.BupaId



{



  key SalesOrder.SalesOrder,

  key SalesOrder.SalesOrderItem,

  key SalesOrder.Payment,

      SalesOrder.OrderDate,



    @Aggregation.default: #SUM

    @Semantics.amount.currencyCode: 'ItemCurrency'

    SalesOrderItem.amount                           as ItemAmount,

    SalesOrderItem.currency                         as ItemCurrency,



    @Aggregation.default: #MAX

    Payment.PaymentDueDate                          as PaymentDueDate,

    @Aggregation.default: #MAX

    Payment.PaymentDate                             as PaymentDate,



    Payment.PaymentMethod                           as PaymentMethod,



    @Aggregation.default: #SUM

    @Semantics.amount.currencyCode: 'PaymentCurrency'

    Payment.PaymentAmount                           as PaymentAmount,

    Payment.PaymentCurrency                         as PaymentCurrency,



    @ObjectModel.foreignKey.association: '_Buyer'

    SalesOrder.Buyer,



    _Buyer

}

Great – But Where’s My Fancy Analytical Reporting?

I love your excitement! Building a dedicated CDS Analytical Query on top of our cube will be the next step – in the next part of this series. So, stay tuned!

Ok – I just can’t leave you behind with such a spoiler. Here's a preview of what an analytical reporting could look like when accessed via SAP Analytics Cloud.

Analytical Story in SAP Analytics Cloud (SAC)

Don't forget to checkout further material:

Developer Guide: Analytical Data Modeling

Cheerio ABAP folks!

SAP Native HANA Procedure to Create and Populate a Transpose Table

2023-08-08T18:16:56+02:00

Scenario:

The scenario is to transpose a table by a single transpose column and populate the new table with the data.

PRODUCT_DATA:

PRODUCT_TRANSPOSE:

Solution Approach:

The solution is to create the dynamic SQL statement as below which combines both creation and population of data into one step, where the bolded parts of the statement are dynamically created.

Create table Product_transpose as (        



    SELECT Product, Large,Small,Medium FROM (  



SELECT Product,



MAX(CASE WHEN Product_Type = 'Large' THEN Unit_Price END) AS   Large,



MAX(CASE WHEN Product_Type = 'Small' THEN Unit_Price END) AS Small,



MAX(CASE WHEN Product_Type = 'Medium' THEN Unit_Price END) AS Medium



From Product_data



Group By Product ))

First two statements are to create the table Product_transpose with the desired columns.

The inner select statement reads the data from product_data by transposing it as below.

Solution:

Step1:

First, we will use the SQL function “STRING_AGG”, to get the distinct values in the transpose column.

In our case “Product_Type”. This is the dynamic column list for the transpose table.

We will store this list it in 'ProductTypeList' variable.

SELECT string_agg(PRODUCT_TYPE, ', ')

INTO ProductTypeList

FROM (SELECT DISTINCT PRODUCT_TYPE from PRODUCT_DATA as b);

Step2:

Create the first part of the dynamic SQL statement as below.

DynamicSQL := 'Create table Product_transpose as (



    SELECT PRODUCT,  ' || ProductTypeList || ' FROM (



        SELECT PRODUCT,



         ';

Step3:

Dynamically create the statement for populating the data as below.

SELECT 

STRING_AGG('MAX(CASE WHEN PRODUCT_TYPE = ''' || PRODUCT_TYPE || ''' THEN 

Unit_Price END) AS ' || PRODUCT_TYPE, ', ')



INTO ColumnExpressions



FROM (SELECT DISTINCT PRODUCT_TYPE FROM Product_data);

Step4:

Combine all the 3 steps and create the complete dynamic SQL.

DynamicSQL := DynamicSQL || ColumnExpressions || 

' FROM Product_data GROUP BY PRODUCT))';

Step5:

Execute the dynamic SQL.

EXEC DynamicSQL;

Step6:

Call the procedure from the SQL console as below.

CALL "MYSCHEMA"."MYPACKAGE::product_transpose" ( ) ;

Complete Code:

PROCEDURE "MYSCHEMA"."MYPACKAGE::product_transpose" ( )



       LANGUAGE SQLSCRIPT



       SQL SECURITY INVOKER



       --DEFAULT SCHEMA <default_schema_name>



       --READS SQL DATA



       AS



BEGIN



DECLARE ProductTypeList NVARCHAR(10000);



DECLARE DynamicSQL NVARCHAR(60000);



DECLARE ColumnExpressions NVARCHAR(50000);





SELECT string_agg(PRODUCT_TYPE, ', ')



INTO ProductTypeList



FROM (SELECT DISTINCT PRODUCT_TYPE from PRODUCT_DATA as b);





DynamicSQL := 'Create table Product_Transpose as (



    SELECT PRODUCT, ' || ProductTypeList || '



    FROM (



        SELECT PRODUCT,



   ';



SELECT STRING_AGG('MAX(CASE WHEN PRODUCT_TYPE = ''' || PRODUCT_TYPE || ''' 



       THEN UNIT_PRICE END) AS ' || PRODUCT_TYPE, ', ')



       INTO ColumnExpressions



      FROM (SELECT DISTINCT PRODUCT_TYPE FROM PRODUCT_DATA);

   



DynamicSQL := DynamicSQL || ColumnExpressions || ' FROM PRODUCT_DATA



    GROUP BY PRODUCT))';



EXEC DynamicSQL;





END;

In Conclusion,

SAP Native HANA procedures are a powerful feature to execute complex data transformations, which can significantly enhance data manipulation and processing efficiency.

Embrace the advantages of streamlined data processing, optimized performance, and simplified code maintenance that these procedures offer.

Feel free to like, comment and share your thoughts! Your insights, questions, and feedback are invaluable in developing a collaborative learning environment.

CDS Hierarchy Directory: How to use NOTASSIGNEDNODE Annotation to suppress or to filter the Not Assigned(REST_H) nodes

2023-12-19T23:56:31+01:00

This blog is about how to handle Not Assigned(REST_H) nodes in CDS Hierarchy Directory of Analytical query, to get the result set either without Not Assigned node or filtered Not Assigned node. Let’s start with some basic information about CDS Hierarchy Directory.

Introduction to CDS Hierarchy Directory

There are two types of Hierarchy views. First where we use annotation ‘@Hierarchy’ and new one where we use ‘define hierarchy <NAME>’ (from 2023 on Prem and 2308 Cloud). In both the ways we can define association to a view which is then used as Hierarchy Directory.

Hierarchy Directory is CDS view.

It contains the List of all hierarchies available in the hierarchy view.

It can have Text for the hierarchies (language independent case) Or it can have an association to a text view (language dependent case)

It can contain a field which determine whether the Not Assigned node will be displayed or not.

It can contain a field which describes a filter which should be applied to the Not Assigned node.

It can contain a field which describes when a hierarchy was changed last time and which has annotation as ‘@Semantics.systemDate.lastChangedAt : true (for date)’ or ‘@Semantics.systemDateTime.lastChangedAt: true (for timestamp)’

When this field exist, then analytical engine will buffer the hierarchy and will renew the buffer when hierarchy is changed. Without this field hierarchy will always be rebuild and it can be performance overhead.

Use of NOTASSIGNEDNODE Annotations in CDS Hierarchy Directory

@HIERARCHY.NOTASSIGNEDNODE.SUPPRESSINDICATOR can be used to suppress the display of Not Assigned nodes.

It can be used for one field in a Hierarchy Directory view. The data type of the field must be Boolean (CHAR field with length 1 and with values '' or 'X'). If the flag is set for an entry in the directory, then the analytical engine doesn't create a 'Not Assigned' node. In this case the hierarchy itself acts as a filter and data which is not a leaf in the hierarchy is not part of the resultset.

@HIERARCHY.NOTASSIGNEDNODE.FILTER can be used to restrict the display of Not Assigned nodes.

It can be used for a field in the Hierarchy Directory view. The field needs in addition, a foreign-key association to a dimension view. This dimension view has also to be target of a foreign-key association defined in the dimension view which holds the hierarchy. The field with that foreign-key association must be a non representative key field. When the analytical engine resolves the 'Not Assigned' node, it derives a filter from the hierarchy’s name and applies this filter to the dimension values which have to be added to the 'Not Assigned' node. The other dimension values, which don't fulfil the filter criteria are ignored. In this case the hierarchy itself acts as a filter. The annotation can be used for key and for non-key fields in the Hierarchy Directory. Only constraint is that the field needs a foreign-key association.
With this feature you can improve the performance. It is only useful for hierarchies on dimensions with more than one key field and if one hierarchy should only contain leaves belonging to one value of a key field. A typical example is a cost center hierarchy. All cost centers of one hierarchy should belong to the same controlling area. Without this feature the analytical engine would also add cost centers of other controlling areas to the 'Not-Assigned' node. Notice that this happens independent of the filters used in a query. Therefore, in a query result there is no difference if the query contains a filter on the same controlling area. But the performance will be much better if the filter is also defined in the Hierarchy Directory.

Examples

Example 1: Without @HIERARCHY.NOTASSIGNEDNODE

@EndUserText.label: 'Connection Hierarchy Directory View'

@analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }

@ObjectModel.representativeKey: 'hieid'

define view entity ZOQ_CONNECTION_HIERARCHY_DIR as select from ZOQ_CONNID_HD

{

@ObjectModel.text.element: 'hiertxt'

key hieid,

@Semantics.text: true

hiertxt,

@Semantics.systemDate.lastChangedAt: true

last_changed

}

Resultset will display Not assigned (REST_H) nodes

Example 2: With @HIERARCHY.NOTASSIGNEDNODE.SUPPRESSINDICATOR

@EndUserText.label: 'Connection Hierarchy Directory View'

@analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }

@ObjectModel.representativeKey: 'hieid'

define view entity ZLR_CONNECTION_HIERARCHY_DIR as select from zoq_connid_hd

{

@ObjectModel.text.element: 'hiertxt'

key hieid,

@Semantics.text: true

hiertxt,

@Semantics.systemDate.lastChangedAt: true

last_changed,

@Hierarchy.notAssignedNode.suppressIndicator: true

'X' as suppressNotAssigned

}

Resultset will not display Not Assigned (REST_H) nodes

Example 3: With @HIERARCHY.NOTASSIGNEDNODE.FILTER

@EndUserText.label: 'Connection Hierarchy Directory View'

@analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }

@ObjectModel.representativeKey: 'hieid'

define view entity ZLR_CONNECTION_HIERARCHY_DIR as select from zoq_connid_hd

association to ZOQ_AIRLINE as _carrid on _carrid.carrid = $projection.carrid

{

@ObjectModel.text.element: 'hiertxt'

key hieid,

@Semantics.text: true

hiertxt,

@Semantics.systemDate.lastChangedAt: true

last_changed,

@ObjectModel.foreignKey.association: '_carrid'

@Hierarchy.notAssignedNode.filter: true

cast( 'LH' as s_carr_id ) as carrid,

_carrid

}

Resultset will display Not Assigned(REST_H) node but only with LH as we have provided filter on carrid LH

Following are some of correction which are done for this feature:

3348310 - Problem with Hierarchy.notAssignedNode.filter
3377570 - Dump: GETWA_NOT_ASSIGNED in class CL_RSR_RRK0_HIERARCHY

CDS View: Time comparison

2024-02-28T22:27:29.400000+01:00

This blog is about CDS scalar functions - CALENDER_SHIFT and CALENDER_OPERATIONS and how to use it in analytical queries for time comparison. Similarly FISCAL_CALENDAR_SHIFT and FISCAL_CALENDAR_OPERATION can be used.

These CDS scalar functions are used to compare the measure value of current time period with previous time period. Further it can be used to calculate measure value for year to date (YTD), month to date (MTD) or quarter to date (QTD). Current member can only be used when time dimensions are in drilldown else restricted measure is used. The usage of current member is not as fast as restricted measure. Detail specification of the mentioned scalar functions can be found in Help.

Usage of Current Member

This function can be used by modeling an association with the cube. In the ON-condition, the scalar functions are specified on the right side.

association to ZOQ_FLIGHT as _previousMonth
    on _previousMonth.fyearMonth = calendar_shift( base        => $projection.fyearMonth, 
                                                   base_level  => calendar_date_level.#MONTH,	
                                                   shift       => abap.int2'-1',
                                                   shift_level => calendar_date_level.#MONTH  )

Constraints:

Current member to work properly, we have to mark all the time fields which are related with annotation - @ObjectModel.value.derivedFrom. We should also specify semantics. for example,

key fldate,
@ObjectModel.value.derivedFrom: 'fldate'
@Semantics.calendar.yearMonth: true
@ EndUserText.label: 'FL Month'
_calday.calmonth as fyearMonth,

The base parameter must be filled with the same field name as it appears on the left: for example, the field name __previousMonth.fyearMonth should be same as base => $projection.fyearMonth

The Semantics of field $projection.fyearMonth must match the base_level parameter. As In the cube view example, the fyearMonth field has the annotation @Semantics.calendar.yearMonth: true, base_level is specified as calendar_date_level.#MONTH.
In the example to restrict the measure to the previous month, shift is set to -1 and shift_level is set to #MONTH. There is a constraint in using shift_level with base_level : for example for base level #MONTH, shift _level can be #MONTH,#QUARTER or #YEAR But can’t be #DAY.

Example 1: Time comparison with time in drill-down (Current Member Variables)

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Query: Current Memeber on Month'
define transient view entity ZLR_PC_CM_1 
provider contract analytical_query
as projection on ZOQ_FLIGHT

  association to ZOQ_FLIGHT as _previousMonth
    on _previousMonth.fyearMonth = calendar_shift( base        => $projection.fyearMonth, 
                                                   base_level  => calendar_date_level.#month,
                                                   shift       => abap.int2'-1',
                                                   shift_level => calendar_date_level.#month  )
  association to ZOQ_FLIGHT as _firstMonthOfQuarter
    on _firstMonthOfQuarter.fyearMonth between calendar_operation( base           => $projection.fyearMonth,
                                                                  base_level      => calendar_date_level.#month,
                                                                  operation       => calendar_date_operation.#first,
                                                                  operation_level => calendar_date_level.#quarter )  
                                          and $projection.fyearMonth  
      
  association to ZOQ_FLIGHT as _CMM1_CMP1
    on _CMM1_CMP1.fyearMonth between calendar_shift( base        => $projection.fyearMonth, 
                                                     base_level  => calendar_date_level.#month,
                                                     shift       => abap.int2'-1',
                                                     shift_level => calendar_date_level.#month  )     
                                 and calendar_shift( base        => $projection.fyearMonth, 
                                                     base_level  => calendar_date_level.#month,
                                                     shift       => abap.int2'1',
                                                     shift_level => calendar_date_level.#month  )  
 {
  @AnalyticsDetails.query: {
    axis: #ROWS,
    totals: #SHOW
  } 
  @EndUserText.label: 'Year Quarter'
  flquarter,
  
   @AnalyticsDetails.query: {
     axis: #ROWS,
     totals: #SHOW
  }  
   @EndUserText.label: 'Year Month'
   fyearMonth,
  
   @AnalyticsDetails.query.axis: #FREE
   .hidden: true
   currency,
   
   @Semantics.amount.currencyCode: 'currency'
   paymentsum,
   
   _previousMonth.currency as PrevMonthCurrency,
   @Semantics.amount.currencyCode : 'PrevMonthCurrency'
   @EndUserText.label: 'Previous Month'
   _previousMonth.paymentsum as PrevMonthPayment,

   _firstMonthOfQuarter.currency as firstMonthOfQuartCurrency,
   @Semantics.amount.currencyCode : 'firstMonthOfQuartCurrency'
   @EndUserText.label: 'Quarter to today'
   _firstMonthOfQuarter.paymentsum as firstMonthOfQuartPayment, 

   _CMM1_CMP1.currency as last3MonthCurrency,
   @Semantics.amount.currencyCode : 'last3MonthCurrency'
   @EndUserText.label: 'Previous month To next month'
   _CMM1_CMP1.paymentsum as CMM1_CMP1Payment

}
where flyear =  '2019'
  and currency = 'EUR'

Result:

In this Result

Red- column Previous Month -shows value from previous month.
Yellow- column Quarter to Today- shows the aggregate values of previous months in this quarter.
Green- column Gliding window of 3 month- shows aggregate value of previous month + current month + next month.

Usage of Restricted Measure

This can be done using the CASE statement, where one of the scalar function is used.

   case when fyearMonth = calendar_shift( base        => $parameters.p_month, 
                                          base_level  => calendar_date_level.#MONTH,
                                          shift       => abap.int2'-1',
                                          shift_level => calendar_date_level.#MONTH ) then paymentsum end as paymentPrev

Constraints:

The base parameter must be a parameter or a literal.
The type of parameter or literal must match to base_level. In the example for base_level calendar_date_level.#MONTH, the type of parameter p_month must be NUMC6.
In the example to restrict the measure to the previous month, shift is set to -1 and shift_level is set to #MONTH.

Example 2: Time comparison (Restricted key figure)

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Query: Current Memeber on Month'
define transient view entity ZLR_PC_RSRT_SHIFT1 
provider contract analytical_query
with parameters
       p_month : /bi0/oicalmonth
as projection on ZOQ_FLIGHT
 {
   @AnalyticsDetails.query: {
    axis: #ROWS,
    totals: #SHOW
  } 
   carrid,
   
   currency,
   
   virtual currCur : abap.cuky,
   @Semantics.amount.currencyCode : 'currCur'
   @Consumption.dynamicLabel: {
     label: 'Bookings &1',
     binding: [{ index : 1 , element : 'fyearMonth' }]
   } 
      
   case when fyearMonth = $parameters.p_month then paymentsum end as paymentCur,
   
   virtual currPrev : abap.cuky,
   @Semantics.amount.currencyCode : 'currPrev'
   @Consumption.dynamicLabel: {
     label: 'Previous Bookings &1',
     binding: [{ index : 1 , element : 'fyearMonth' }]
   } 
     
   case when fyearMonth = calendar_shift( base        => $parameters.p_month, 
                                          base_level  => calendar_date_level.#month,
                                          shift       => abap.int2'-1',
                                          shift_level => calendar_date_level.#month  ) then paymentsum end as paymentPrev,  
   
  
   
   virtual currLastInYear : abap.cuky,                                     
   @Semantics.amount.currencyCode : 'currLastInYear'
   @Consumption.dynamicLabel: {
     label: 'Bookings from &1 To &2',
     binding: [{ index : 1 , element : 'fyearMonth', replaceWith: #LOW },
               { index : 2 , element : 'fyearMonth', replaceWith: #HIGH }]
   }  
   case when fyearMonth between calendar_operation( base            => $parameters.p_month, 
                                              base_level      => calendar_date_level.#month,
                                              operation       => calendar_date_operation.#first,
                                              operation_level => calendar_date_level.#year  ) and $parameters.p_month then paymentsum end as paymentToDate                                            
 
}
where currency = 'EUR'

Result:

In this example I have used @Consumption.dynamicLabel to dynamically set the column label with values calculated from parameter.

Release Info:

On-Prem SAP_BW from 7.58 and Cloud from 2308

Related Notes:

3270090-CurrentMember + FemsN

3359468-Current Member on reference characteristic and selection for Partial Time Characteristic

CDS View: Hierarchy node sign reversal

2024-04-15T13:30:04.285000+02:00

This blog is about how to use @Semantics.signReversal in CDS Views to revert the sign of a measure in dependence of the settings of a hierarchy node. Analytic query offers the functionality to reverse a sign after aggregation based on a hierarchy node attribute.

This functionality shall be made accessible from a CDS Query, for this it is necessary to determine the hierarchy node attribute which stores the sign reverse indicator.

To make use of the sign reversal feature in an analytical query, the following field needs to be added to the related hierarchy view:

@Semantics.signReversalIndicator

signref as signReversalFlag,

Example: Hierarchy view

@AbapCatalog.sqlViewName: 'ZOQ_CONNIDHIER'
@EndUserText.label: 'Connection Hierarchy View'
@ObjectModel.dataCategory: #HIERARCHY
@Hierarchy.parentChild : {
  name : 'ConnectionHierarchy',
  label : 'Connection',
  siblingsOrder: [{ by: 'seqno' , direction: 'ASC' }] ,
  recurseBy : '_parent',
  directory: '_dir'
}

define view ZOQ_CONNECTION_HIERARCHY
  as select from zoq_connid_h

  association [0..1] to ZOQ_CONNECTION_HIERARCHY     as _parent     on  $projection.parentid = _parent.nodeid

  association [1]    to ZOQ_CONNECTION_HIERARCHY_DIR as _dir        on  $projection.hieid = _dir.hieid

  association [1]    to ZOQ_CONNECTION_NODENAME as _node       on       $projection.hieid   = _node.hieid
                                                                    and $projection.nodename = _node.nodeName
                                                                    and $projection.carrid   = ''
                                                                    and $projection.connid   = '0000'

  association [1]    to ZOQ_AIRLINE                  as _airline    on  $projection.carrid = _airline.carrid
                                                                    and $projection.connid = '0000'

  association [1]    to ZOQ_CONNECTION               as _connection on  $projection.carrid = _connection.carrid
                                                                    and $projection.connid = _connection.connid

{
      @Consumption.filter: { mandatory : true, selectionType : #SINGLE, multipleSelections : false }
      @ObjectModel.foreignKey.association: '_dir'
  key hieid,
  key nodeid,
      parentid,

      seqno,

      @ObjectModel.foreignKey.association: '_airline'
      carrid,
      @ObjectModel.foreignKey.association: '_connection'
      connid,
      @ObjectModel.foreignKey.association: '_node'
      nodename,
      
      @Semantics.signReversalIndicator
      signref as signReversalFlag,

      _parent,
      _dir,
      _node,
      _airline,
      _connection

}

Preview:

In CDS views with "Analytics.query : true" or define as "transient view entity", function "HRY_NODE_SIGN_VALUE(elemRef)" is used in a formula (AnalyticsDetails.query.formula). This function works in the following way, At first the path from the element to its hierarchy view is evaluated. In the hierarchy view there should exist exactly one field with semantics signReversal. For each hierarchy node for which the value of the sign reversal element returns space, the function HRY_NODE_SIGN_VALUE will return +1. If the value is not initial, the function returns -1. With this,

for example- the formula $projection.paymentsum * hry_node_sign_value( dimension => $projection.connid) as paymentsumSignRef

will return the key figure paymentsum for all nodes/leaves in the hierarchy with initial sign reversal indicator and It will return "- paymentsum" for all nodes/leaves with not initial sign reversal indicator.

If there is no field with semantics signReversal in the hierarchy view, the function HRY_NODE_SIGN_VALUE always returns +1.

Example: Analytical query

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'SIGN REVERSAL'
@Metadata.ignorePropagatedAnnotations: true
define transient view entity ZLR_SIGN_REV_FLIGHT_1 
   provider contract analytical_query 
     with parameters
     @EndUserText.label: 'Hierarchy'
     @Consumption.defaultValue: 'CNTRY' 
     p_hienm : char5 
     
  as projection on ZOQ_FLIGHT
    
 {   
    @AnalyticsDetails.query.axis: #ROWS
    @AnalyticsDetails.query: {
      displayHierarchy: #ON,
      hierarchyBinding: [{ type : #PARAMETER , value : 'p_hienm' }]
    }  
    connid,
    @AnalyticsDetails.query.axis: #FREE
    currency,
    
    @Semantics.amount.currencyCode: 'CURRENCY'
    @Aggregation.default: #SUM
    @AnalyticsDetails.query.axis: #COLUMNS
    curr_to_decfloat_amount( paymentsum ) as paymentsum,
    
    @AnalyticsDetails.query.axis: #COLUMNS
    @EndUserText.label: 'HierSignRev'
    @Aggregation.default: #FORMULA
    $projection.paymentsum * hry_node_sign_value( dimension => $projection.connid) as paymentsumSignRef
  
}

Result:

In this example for Hierarchy ZOQ_CONNECTION_HIERARCHY (which is defined in the ZOQ_FLIGHT), signReversalFlag is set for Carried id 'A', 'JL', 'UA'. Therefore, in result of analytical query HierSignRev field is showing the –ve result of the booking total.

SAP Delivered Hierarchies:

There are few SAP delivered hierarchies which have this feature.

Following fields name: FinancialStatementItem, CnsldtnFinancialStatementItem, FinancialStatementLeafItem, GLAccount, etc.

Can have this feature because they have foreign key association with dimension view which has hierarchy association to hierarchy view supporting this feature.

For example: Field with name ‘FinancialStatementItem’ typically have a foreign key association to dimension view I_CnsldtnFinStmntItem and corresponding hierarchy view I_FinStmntItmHier will support this feature.

Constraints:

Only one element in a view of data category HIERARCHY can be marked with semantics signReversal. The data type of the element should be CHAR of length 1. Allowed values are X or space.

Related Note:

1385580 - How does a formula variable with a replacement path work?

Availability:

This feature is available from S/4HANA 1909 (ABAP Platform 7.54).

CDS : How to define Hierarchy View

2024-07-17T14:18:20.286000+02:00

This blog is about how to define Hierarchy View in CDS.

There are two types of hierarchies – 'Leveled Hierarchy' and 'Parent-Child Hierarchy' In Analytics, only a Parent-Child hierarchy is supported.

In CDS, Hierarchy can be defined in two ways:

Inline Hierarchy: where the hierarchy definition is modelled in the dimension view.

External Hierarchy: where there is a separate CDS view to model the definition of the hierarchy.

In the past, External hierarchy was defined using the annotation '@ObjectModel.dataCategory: #HIERARCHY'. Now, in CDS it is allowed to define new type of CDS view called as Hierarchy CDS, which is defined using syntax define hierarchy, which create a hierarchical view.

A CDS hierarchy represents a HANA hierarchy, created when the CDS hierarchy is activated.

Normally the hierarchy contains headers and nodes. The header data of the hierarchy is coming from the directory view and the nodes data is coming from the hierarchy view itself.

Hierarchy Directory

The directory of the hierarchy provides the header information of the hierarchy. A hierarchy view might contain more than one hierarchy. Information about each hierarchy (e.g. text) is provided by a hierarchy directory. More information can be found in blog.

Typically, the directory view is defined as follows:

@EndUserText.label: 'Connection Hierarchy Directory View'
@Analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }
@ObjectModel.representativeKey: 'hieid'

define view entity ZLR_CONNECTION_HIERARCHY_DIR
  as select from zoq_connid_hd
{
      @ObjectModel.text.element: [ 'hiertxt' ]
  key hieid,
      @Semantics.text: true
      hiertxt,
      @Semantics.systemDate.lastChangedAt: true
      last_changed,

}

Output

Hierarchy View using define hierarchy <NAME>

This is the new way of defining hierarchy and it is available from 2023 on Prem and 2308 Cloud. For defining hierarchy, prerequisite is having a source view, which is mentioned in the definition as parent child hierarchy source.

Source View

In view definition parent child association is define along with that following associations:

Association to hierarchy view itself- It defines parent child relationship
Association to hierarchy directory - It contains all the header information- hierarchy ids.
Association to different dimension/text views – It is a relation from the nodes and leaves to dimension and text views. Via this association the text of a node/leaf is derived. In the following example '_node' is first level node. '_airline' acts as second level node and '_connection' is leaf and pointing to dimension.
Extra conditions like 'carrid = "" ' are not necessary and the order of the associations is not relevant. Instead in this case a separate field is needed, which returns the fieldname of the records, which should be used. In the example it is field 'nodetype'

@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Base for : New Way of defining Hierarchy'

define view entity ZLR_CONN_HIERARCHY_BASE
  as select from zoq_connid_h


  //association to itself.
  association [0..1] to ZLR_CONN_HIERARCHY_BASE      as _parent     on  $projection.hieid    = _parent.hieid
                                                                    and $projection.parentid = _parent.nodeid

  // association with hierarchy directory
  association [1]    to ZLR_CONNECTION_HIERARCHY_DIR as _dir        on  $projection.hieid = _dir.hieid


  // associations to the different node types
  // evalulated at runtime for each record in the order given here
  // first hit of ON-condition is followed
  // Differnce to old way of Hierarchy ZLR_CONNECTION_HIERARCHY - here no $projection.carrid   = ''  and $projection.connid   = '0000'
  association [1]    to ZOQ_CONNECTION_NODENAME      as _node       on  $projection.hieid    = _node.hieid
                                                                    and $projection.nodename = _node.nodeName
 

  // "nodatetype" Airline
  // Differnce to old way of Hierarchy ZLR_CONNECTION_HIERARCHY - here no  and $projection.connid = '0000'
  association [1]    to ZOQ_AIRLINE                  as _airline    on  $projection.carrid = _airline.carrid
 

  // association to dimension view
  association [1]    to ZLR_CONN                     as _connection on  $projection.carrid = _connection.carrid
                                                                    and $projection.connid = _connection.connid

{

      @Consumption.filter: { mandatory : true, selectionType : #SINGLE, multipleSelections : false }
      @ObjectModel.foreignKey.association: '_dir'
  key hieid,
  key nodeid,
      parentid,

      seqno,

      // three different node types possible in this example
      // here CONNID is leaf (can not be derived from this view)
      
      @ObjectModel.foreignKey.association: '_airline'
      carrid,
      @ObjectModel.foreignKey.association: '_connection'
      connid,
      @ObjectModel.foreignKey.association: '_node'
      nodename,

      cast(
      case when carrid is initial and connid is initial then 'NODENAME'
           when connid is initial                       then 'CARRID'
           else 'CONNID' end as fieldname ) as nodetype,
  


      // associations defined above have to be exposed here
      // otherwise they will not be available
      _parent,
      _dir,
      _node,
      _airline,
      _connection
}

Hierarchy View

Hierarchy view can be defined using the following syntax.

Syntax:

...
[DEFINE] HIERARCHY hierarchy
         [parameter_list]
         AS PARENT CHILD HIERARCHY(
           SOURCE cds_view
           CHILD TO PARENT ASSOCIATION _hierarchy_assoc
           [PERIOD FROM field1 TO field2 VALID FROM from TO to]
           [DIRECTORY _directory_assoc FILTER BY cds_cond]
           [START WHERE cds_cond]
           SIBLINGS ORDER BY field1 [ASCENDING|DESCENDING][,
                             field2 [ASCENDING|DESCENDING], ...]
           [DEPTH depth]
           [NODETYPE node_type]
           [LOAD BULK|INCREMENTAL|load_option]
           [MULTIPLE PARENTS {NOT ALLOWED}|LEAVES|ALLOWED]
           [ORPHANS IGNORE|ERROR|ROOT]
           [CYCLES ERROR|BREAKUP]
           [GENERATE SPANTREE]
           [CACHE ON|OFF|FORCE])
     { element_list }

In Syntax

SOURCE – Name of Source view. The mandatory addition SOURCE specifies a CDS view entity. This source must expose the hierarchy association specified after CHILD TO PARENT ASSOCIATION in its SELECT list.

source

ZLR_CONN_HIERARCHY_BASE

CHILD TO PARENT ASSOCIATION: The mandatory addition CHILD TO PARENT ASSOCIATION specifies the hierarchy association who’s ON condition selects the descendant nodes of the root node set.

child to parent association

_parent

PERIOD FROM field1 TO field2 VALID FROM from TO to: The optional addition PERIOD defines the hierarchy as a temporal SQL hierarchy in which the hierarchy nodes are limited by an adjustment of time intervals. In case of parameter, they can be different but value must be same when used in a query. period from datefrom to dateto valid from $parameters.p_date to $parameters.p_date

period from datefrom to dateto valid from '20230425' to '20230425'

DIRECTORY: Hierarchy directory name. The optional addition DIRECTORY defines a filter condition cds_cond for the rows of the source of the hierarchy specified after SOURCE. It defines association to the header/ directory view. Filter can be defined on hierarchy directory, based on parameter. In case of time dependent hierarchy date parameters can be used to filter out the hierarchy.

_dir filter by hienm = $parameters.p_hienm1

and keydate = $parameters.p_keydate

START WHERE: The optional addition START WHERE specifies the start condition for creating the hierarchy. START WHERE can be followed by a logical expression cds_cond that selects rows from the source cds_view.

start where

parentid is initial

SIBLINGS ORDER BY field1 [ASCENDING|DESCENDING]: The mandatory addition SIBLINGS ORDER BY sorts sibling nodes in the hierarchy. Default is Ascending.

siblings order by

seqno

NODETYPE node_type: The NODETYPE identifies an element of the CDS hierarchy that can be used to determine the type of the hierarchy node. The values of this element must be element names, which must also be contained in the element list of the CDS hierarchy.

In context of Analytics, it is mandatory to define the nodetype field in the source view of the hierarchy and also in the hierarchy view using key word 'nodetype'

For example, in the Source view

cast(

case when carrid is initial and connid is initial then 'NODENAME'

when connid is initial then 'CARRID'

else 'CONNID' end as fieldname ) as nodetype,

In the Hierarchy view

nodetype

nodetype

More detailed information can be found here ABAP Keyword Documentation (sap.com).

Example of Hierarchy View

define hierarchy ZLR_CONN_HIERARCHY
  with parameters
    @Consumption.defaultValue: 'CNTRY'
    p_hieid : zoq_conhieid
  as parent child hierarchy(
    source ZLR_CONN_HIERARCHY_BASE
    child to parent association _parent
    directory _dir filter by
      hieid = $parameters.p_hieid
    start where
      parentid is initial
    siblings order by
      seqno
    nodetype nodetype
  )
{

      @ObjectModel.foreignKey.association: '_dir'
  key hieid,
  key nodeid,
      parentid,
      seqno,

      @ObjectModel.foreignKey.association: '_airline'
      carrid,
      @ObjectModel.foreignKey.association: '_connection'
      connid,
      @ObjectModel.foreignKey.association: '_node'
      nodename,

      nodetype, 
     
      // associations defined above have to be exposed here
      // otherwise they will not be available
      _parent,
      _dir,
      _node,
      _airline,
      _connection



}

Output

Red: association _node

Green: association _airline

Blue: association _connection, the blue marked records are leaves

Example of Query using Hierarchy

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'ZLR_CONN - query'
@Metadata.ignorePropagatedAnnotations: true

define transient view entity ZLR_CONN_QUERY
provider contract analytical_query
as projection on ZLR_CONN
{
@AnalyticsDetails.query:{
axis:#ROWS,
displayHierarchy: #ON ,
hierarchyBinding: [{ type: #CONSTANT, value: 'CNTRY'  }]

}
  connid
    
}

Output

Hierarchy View Using @ObjectModel.dataCategory: #HIERARCHY Annotation (OLD way)

In View definition the annotation @Hierarchy.parentChild provides the information about the parent child hierarchy. It has hierarchy name, multiple parents, recursion by, ordering of siblings, root node visibility, orphaned node handling, etc. along with that, following associations need to be defined.

Association to hierarchy view itself - It defines parent child relationship.
Association to hierarchy directory view - It contains all the header information, hierarchy Ids and the descriptions.
Association to different dimension/text views – It is a relation from the nodes and leaves to dimension and text views. Via this association the text of a node/leaf is derived. In the following example '_node' is first level node, '_airline' acts as second level node and '_connection' is leaf and pointing to dimension.

Important is the order of the associations listed in the element-list and the 'extra-condition' in the ON-clause. For each record of the hierarchy the ON condition of the associations is checked - the first association which meets the ON condition is used to get text and attributes for the hierarchy node/leaf.

One association is mandatory - its target must be the dimension view which has a ObjectModel.hierarchy.association to the hierarchy view. These objects in the hierarchy represent the leaves.

Example

@EndUserText.label: 'Connection Hierarchy View'
@ObjectModel.dataCategory: #HIERARCHY
@Hierarchy.parentChild: [{  
name : 'ConnectionHierarchy',
  label : 'Connection',
  siblingsOrder: [{ by: 'seqno' }] ,
  recurseBy : '_parent',
  directory: '_dir'
  }] 
  
define view entity ZLR_CONNECTION_HIERARCHY
  as select from zoq_connid_h

  // basic parent child relation inside one hierarchy
  // hierarchy uniquely selected (see @Filter for field HIEID
  association [0..1] to ZLR_CONNECTION_HIERARCHY     as _parent     on  $projection.parentid = _parent.nodeid

  // necessary if view represents several hierarchies
  // association to the hierarchy directory
  association [1]    to ZLR_CONNECTION_HIERARCHY_DIR as _dir        on  $projection.hieid = _dir.hieid


  // associations to the different node types
  // evalulated at runtime for each record in the order given here
  // first hit of ON-condition is followed
  association [1]    to ZOQ_CONNECTION_NODENAME as _node       on       $projection.hieid   = _node.hieid
                                                                    and $projection.nodename = _node.nodeName
                                                                    and $projection.carrid   = ''
                                                                    and $projection.connid   = '0000'

  // "nodatetype" Airline
  association [1]    to ZOQ_AIRLINE                  as _airline    on  $projection.carrid = _airline.carrid
                                                                    and $projection.connid = '0000'

  // For which dimension this hierarchy belongs
  association [1]    to ZLR_CONNECTION               as _connection on  $projection.carrid = _connection.carrid
                                                                 and $projection.connid = _connection.connid

{
      @Consumption.filter: { mandatory : true, selectionType : #SINGLE, multipleSelections : false }
      @ObjectModel.foreignKey.association: '_dir'
  key hieid,
  key nodeid,
      parentid,

      seqno,

      // three different node types possible in this example
      // here CONNID is leaf (can not be derived from this view)
      
      @ObjectModel.foreignKey.association: '_airline'
      carrid,
      @ObjectModel.foreignKey.association: '_connection'
      connid,
      @ObjectModel.foreignKey.association: '_node'
      nodename,
      
      // associations defined above have to be exposed here
      // otherwise they will not be available
      _parent,
      _dir,
      _node,
      _airline,
      _connection

}

Output

Red: association _node

Green: association _airline

Blue: association _connection, the blue marked records are leaves

Reference

More information on @Semantics.signReversalIndicator can be found in the blog.

Query Hierarchy F4 Help not customizeable ? Not possible for a multi level Hierarchy ?

2024-10-31T16:19:34.903000+01:00

newly updated ! newly updated ! newly updated !newly updated !newly updated !

Hierarchy input Parameter f4 selection user customized solution searched
===========================================================
Summary:
Desired result is, that a SAP User with defined access rights can see and choose in the query input only those hierachie trees and leaves which he is authorized for.

The authorization rights for each single SAP User are available in a flat view consisting of (SAP User- Country -Region -- Company Code).

Current design Hierarchy Tree:
+-0HIER_NODE (Root=Betriebe Gesamt = All Plants)
+-- ZMO_CNTRY (Country Node = DE, AT)
+---ZMO REGION (Region Node: BER, FRO)
+----ZMO_CCODE (Company Code Leave=5070, 8000):

Current Query Design:

Hierachy node, Mulit entry, input ready variable of the filter which allows the multibed entry

Current– Customer Exit F4 Input Variable Design:

Current F4 Customers Exit Parameter Result:

Sample Desired Result:
A User with these Values Country = DE, Region=BER, Company Codes 5070, 5150, 5160 should result in this F4:

Suggested Solution With Badi RSR_VARIABLE_F4_RESTRICT

Filtervalues:

Using Class Method IF_RSR_VARIABLE_F4_RESTRICT~GET_RESTRICTION_NODE

With a Custome Class with the Method IF_RSR_VARIABLE_F4_RESTRICT~GET_RESTRICTION_NODE

???????Right Method ???????
???????But how to fill the Structures properly ??????
???????This wont do it

method IF_RSR_VARIABLE_F4_RESTRICT~GET_RESTRICTION_NODE.

DATA: l_s_node LIKE LINE OF c_t_node,
l_s_hier LIKE LINE OF c_t_hierarchy.
*
#CASE i_vnam.
**
WHEN 'ZCOMPCODE_HIERNODE_CUST_MULTI'.

* ZMO_COMPANY_HIERARCHIE_SAC is the flat view containing the
* Assigments Country Region – BUKR and via an Autorization CDS
* the right BUKrs
* GROUP By is only used to have only 1 BUKRS in the SELECT result set.
    SELECT     BUKRS
    FROM       ZMO_COMPANY_HIERARCHIE_SAC
    GROUP BY   BUKRS
    INTO @DATA(BUKRS).

       clear l_s_node.
       l_s_node-niobjnm  = 'ZMO_CCODE'. l_s_node-nodename = BUKRS.

       APPEND l_s_node  TO c_t_node.

    ENDSELECT.

    SELECT     country
    FROM       ZMO_COMPANY_HIERARCHIE_SAC
    GROUP BY   country
    INTO @DATA(country).
       clear l_s_node.
       l_s_node-niobjnm  = 'ZMO_CNTRY'.
       l_s_node-nodename = country.

       APPEND l_s_node  TO c_t_node.

    ENDSELECT.

    SELECT     region
    FROM       ZMO_COMPANY_HIERARCHIE_SAC
    GROUP BY   region
    INTO @DATA(region).
       clear l_s_node.
       l_s_node-niobjnm  = 'ZMO_REGIO'.
       l_s_node-nodename = region.
       APPEND l_s_node  TO c_t_node.

ENDCASE.

endmethod.

CDS View: How to provide the default value for hierarchy node variable in analytical queries

2024-11-08T15:57:12.182000+01:00

This blog is about – how to provide static or dynamic default value for hierarchy node variable in analytical queries.

Static Default values

Hierarchy node variable is defined using @AnalyticsDetails.variable annotation. Static default value for this variable can be provided using @AnalyticsDetails.variable.defaultHierarchyNode annotation.

In @AnalyticsDetails.variable annotation, selectionType need to set as #HIERRARCHY_NODE, also hierarchyBinding is specified along with referenceElement, MultipleSelections.

Example

@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Example of static default value'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
  serviceQuality: #X,
  sizeCategory: #S,
  dataClass: #MIXED
}
define transient view entity ZLR_RES_HIERNODE2
  provider contract analytical_query
  with parameters

    @EndUserText.label: 'Connection Hierarchy'
    p_hienm     : char5,

    @AnalyticsDetails.variable: {
       selectionType: #HIERARCHY_NODE,
       referenceElement: 'connid',
       hierarchyBinding: [{ type:#PARAMETER, value: 'p_hienm'}],
       multipleSelections: true,
       defaultHierarchyNode:
       {
         nodeType: 'carrid',
         node: [{element: 'carrid', value:'AZ' }]
       }

    }

    @Consumption.hidden: true
    p_hier_node : s_conn_id

  as projection on ZOQ_FLIGHT
{

  @AnalyticsDetails.query.displayHierarchy: #FILTER
  @AnalyticsDetails.query.axis: #ROWS
  @AnalyticsDetails.query.totals: #SHOW
  connid,

  currency,

  @Semantics.amount.currencyCode: 'CURRENCY'
  @AnalyticsDetails.query.axis: #COLUMNS
  paymentsum


}
where
      currency = 'EUR'
  and connid   = $parameters.p_hier_node

Output

Dynamic Default Values

Dynamic default values for hierarchy node variables should be derived from another CDS view (lookup view) at runtime.

@Consumption.derivation annotation enables derivation of the value for a parameter or a filter automatically at runtime by selecting a row from a given entity.

At first, a separate hierarchy node lookup view is defined.

Then hierarchy node variable is defined using @AnalyticsDetails.variable annotation.

To specify a default value for the previously defined node variable @Consumption.derivation.resultHierarchyNode is used.

@Consumption.derivation annotation contains,

lookupEntity, which provide the name of hierarchy node lookup view to get the hierarchy node.

resultHierachyNode annotation is used to provide hierarchy node value to a parameter.

resultHierarchyNode.nodeTypeElement must point to a field in the lookup entity and this field must return a fieldname. This fieldname (in the data of the lookup view) must be an existing fieldname in the lookup view. If the value of field NodeTypeElement in the result of the lookup is initial, the row represents a leaf.

resultHierarchyNode.Mapping describes the mapping of the elements in the hierarchy view and the elements in the lookup entity.

Consumption.derivation.binding is possible to add filters to the lookup. This is generic and not specific to hierarchy nodes.

Example

Step 1: Defining Hierarchy node lookup view

Hierarchy node look up view is use as a lookup entity in the @Consumption.derivation annotation.

@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Derivation for node parameter-resultHierarchyNode'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
  serviceQuality: #X,
  sizeCategory: #S,
  dataClass: #MIXED
}
define view entity ZLR_RES_DERIVE_BASE as select from  t000
{
   cast( 'carrid1' as fieldname ) as nodeType,
   cast( 'LH' as s_carr_id ) as carrid1, 
   cast( ' ' as s_conn_id ) as connid1,
   cast( ' ' as rsshnodename  ) as nodename1,
   $session.user                as userName                                                                             
}
where mandt = '000'

Step 2: Defining hierarchy node variable and use Consumption.derivation annotation in analytical query

In this example, ZLR_RES_DERIVE_BASE view is used as lookupEntity- which provides default value to the parameter

@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Example of dynamic default value'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
  serviceQuality: #X,
  sizeCategory: #S,
  dataClass: #MIXED
}
define transient view entity ZLR_RES_HIERNODE1 
provider contract analytical_query
with parameters

@EndUserText.label: 'Connection Hierarchy'
p_hienm : char5,

@AnalyticsDetails.variable: { 
   selectionType: #HIERARCHY_NODE, 
   referenceElement: 'connid',   
   hierarchyBinding: [{ type:#PARAMETER, value: 'p_hienm'}],
   multipleSelections: true
  
    }
  
@Consumption.derivation: {
  lookupEntity: 'ZLR_RES_DERIVE_BASE',
  resultHierarchyNode: {
      nodeTypeElement: 'nodetype',
      mapping: [
            { hierarchyElement: 'carrid', lookupElement: 'carrid1' },
            { hierarchyElement: 'connid', lookupElement: 'connid1' },
            { hierarchyElement: 'nodename', lookupElement: 'nodename1' }
      ]
    }
}
@Consumption.hidden: true
 p_hier_node : s_conn_id

as projection on ZOQ_FLIGHT
{

@AnalyticsDetails.query.displayHierarchy: #FILTER
@AnalyticsDetails.query.axis: #ROWS
@AnalyticsDetails.query.totals: #SHOW
connid,

currency,

@Semantics.amount.currencyCode: 'CURRENCY'
@AnalyticsDetails.query.axis: #COLUMNS
paymentsum
 
}
where currency = 'EUR' and connid = $parameters.p_hier_node

Output

Please note that in the older release instead of using @AnalyticsDetails.variable annotation, @Consumption.hierarchyNodeSelection is used.

@Consumption.hierarchyNodeSelection: {

hierarchyElement: 'connid',

hierarchyBinding: [{ type:#PARAMETER, value: 'p_hienm'}],

multipleSelections: true

}

CDS : How to define analytical query using two structures

2024-12-20T14:44:22.867000+01:00

This blog is about how to use two structures in CDS analytical query as in BW query.

The structure forms the foundational layout of the axes (rows or columns) in a data table, determining how information is organized and presented.
Structural components of key figure structures are always based on the key figure selections (basic key figures, restricted key figures, and calculated key figures). Characteristic structural components cannot contain key figure selections.

The arrangement of the structure affects the order and quantity of key figures or characteristics displayed in the rows and columns of a query or report.

Example: BW Query with Characteristic structure and Key Figure structure

In Analytical query, elements can be assigned to characteristics structure using @AnalyticsDetails.query.onCharacteristicStructure: true. Element with measures get automatically assigned to measure structure.

Formulas can be defined for both characteristic structure and measure structure. The operands of a formula must be elements of the same structure to which the formula belongs. Operands of the other structure are not allowed.

If an analytical query has two structures (a measure and a characteristic structure), then the query result is a grid. Each cell in this grid is defined by an element of the measure structure and one of the characteristic structures. Restrictions are combined with AND. If both elements are formulas, the formula of the measure structure is calculated by default. Also, other properties like scaling, decimals are taken from the element of the measure structure by default. If this should be different, @AnalyticsDetails.query.collisionHandling annotation is used.

collisionHandling:

{ formula : String( 20) enum { DEFAULT; THIS; CONCURRENT; };

decimals : String( 20) enum { DEFAULT; THIS; CONCURRENT; };

scaling : String( 20) enum { DEFAULT; THIS; CONCURRENT; };

semanticObject : String( 20) enum { DEFAULT; THIS; CONCURRENT; };

};

Example:

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'CDS Query with 2 Structures'
@ObjectModel.modelingPattern: #ANALYTICAL_QUERY
@ObjectModel.supportedCapabilities: [ #ANALYTICAL_QUERY ]

define transient view entity ZLR_2STRUCT_CELL_REF_SIMPLE
provider contract analytical_query
as projection on ZOQ_FLIGHT
{

//----Elements of Key Figure structure
@AnalyticsDetails.query.axis: #ROWS
@EndUserText.label: 'Max Capacity Economy'
seatsmax,

@AnalyticsDetails.query.axis: #ROWS
@EndUserText.label: 'Occupied Economy'
seatsocc,


@AnalyticsDetails.query.axis: #ROWS
@Aggregation.default: #FORMULA
@EndUserText.label: 'Percentage'
@AnalyticsDetails.query.decimals: 5
seatsocc / seatsmax * 100 as percentage,


//---Elements of Characteristics Structure

@AnalyticsDetails.query.axis: #COLUMNS
@EndUserText.label: 'Calender Year 2019'
@AnalyticsDetails.query.onCharacteristicStructure: true
case when flyear = '2019' then 1 else null end as year2019,

@AnalyticsDetails.query.axis: #COLUMNS
@EndUserText.label: 'Calender Year 2020'
@AnalyticsDetails.query.onCharacteristicStructure: true
case when flyear = '2020' then 1 else null end as year2020,

@AnalyticsDetails.query.axis: #COLUMNS
@Aggregation.default: #FORMULA
@EndUserText.label: 'Diffenece 2019-2020'
@AnalyticsDetails.query.onCharacteristicStructure: true
@AnalyticsDetails.query.decimals: 2
@AnalyticsDetails.query.collisionHandling: {decimals: #THIS}
 $projection.year2019 -  $projection.year2020 as difference

}

Output:

To display structure element in a hierarchy, AnalyticsDetials.query.elementHierarchy.parent and @AnalyticsDetails.query.elementHierarchy.initiallyCollapsed annotations are used in CDS.

Example:

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'CDS Query with 2 Structures'
@ObjectModel.modelingPattern: #ANALYTICAL_QUERY
@ObjectModel.supportedCapabilities: [ #ANALYTICAL_QUERY ]

define transient view entity ZLR_2STRUCT_CELL_REF_HIER
provider contract analytical_query
as projection on ZOQ_FLIGHT
{

//----Elements of Key Figure structure
@AnalyticsDetails.query.axis: #ROWS
@EndUserText.label: 'Max Capacity Economy'
seatsmax,

@AnalyticsDetails.query.axis: #ROWS
@EndUserText.label: 'Occupied Economy'
seatsocc,


@AnalyticsDetails.query.axis: #ROWS
@Aggregation.default: #FORMULA
@EndUserText.label: 'Percentage'
@AnalyticsDetails.query.decimals: 5
seatsocc / seatsmax * 100 as percentage,


//---Elements of Characteristics Structure

@AnalyticsDetails.query.axis: #COLUMNS
@EndUserText.label: 'Calender Year 2019'
@AnalyticsDetails.query.onCharacteristicStructure: true
  @AnalyticsDetails.query.elementHierarchy.parent: 'difference'
case when flyear = '2019' then 1 else null end as year2019,

@AnalyticsDetails.query.axis: #COLUMNS
@EndUserText.label: 'Calender Year 2020'
@AnalyticsDetails.query.onCharacteristicStructure: true
  @AnalyticsDetails.query.elementHierarchy.parent: 'difference'
case when flyear = '2020' then 1 else null end as year2020,

@AnalyticsDetails.query.axis: #COLUMNS
@Aggregation.default: #FORMULA
@EndUserText.label: 'Diffenece 2019-2020'
@AnalyticsDetails.query.onCharacteristicStructure: true
@AnalyticsDetails.query.decimals: 2
@AnalyticsDetails.query.collisionHandling: {decimals: #THIS}
@AnalyticsDetails.query.elementHierarchy.initiallyCollapsed: true  
$projection.year2019 -  $projection.year2020 as difference

}

Output:

After Expanding Hierarchy

Reference:

Working with Structures

CDS : How to define analytical query using cell definition

2025-02-19T15:53:49.446000+01:00

This blog is about how to use cell definition in CDS analytical query as like in BW query. Lets start with brief overview about two structures.

Two Structures

The structure forms the foundational layout of the axes (rows or columns) in a data table, determining how information is organized and presented. The arrangement of the structure affects the order and quantity of key figures or characteristics displayed in the rows and columns of a query or report. More information can be found in CDS : How to define analytical query using two str... - SAP Community

Cell Definition

A cell is the intersection between two structural components. Each cell in grid is defined by an element of the measures-structure and one of the characteristic-structure.

Exception cell: When implicit cell definition overwritten by an explicit definition, cell is called as exception cell. It can be defined using formula or selection. Formulas for a cell must only use operands which are cells.

Help cell: It does not have any direct connection with the corresponding structural elements. It is not embedded in the grid and not displayed, but can be used in formulas of an exception cell.

In BW modelling tool query designer, In 'Cell' tab we can specify the cell definition.

In the above screenshot marked,

Red : Exception cell

Green : Formula to calculate the value for the exception cell

Blue : Help cell

In analytical query to define the Exception cell, following annotation is used.

@AnalyticsDetails.query: {

  isCell: true,

  cellReference: {

    measureStructureElement: 'seatsocc',

    characteristicStructureElement: 'yearPlaceholder'

  }

}

A cell is specified with “@AnalyticsDetails.query.isCell: true”,

If it should overwrite a cell of the grid, then the coordinates can be specified with @AnalyticsDetails.query.cellReference (Exception Cell)

Otherwise, the element is invisible and must be hidden Consumption.hidden:true. (Help Cell)

A value of a cell in the grid can be obtained with CDS function - GET_CELL_REFERENCE_VALUE, which can be used in formula of an exception or help cell.

Example

In the following example, 'exceptionCellRatioPercent' is Exception cell, cellReference defines exact coordinate of this cell. 'helpCellratio' is a helper cell, it does not have cellReference, it is not part of grid and has Consumption.hidden:true. It is used in formula of an exception cell 'exceptionCellRatioPercent' to calculate percentage of occupied seats.

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Query with structure and cell definition'
@ObjectModel.modelingPattern: #ANALYTICAL_QUERY
@ObjectModel.supportedCapabilities: [#ANALYTICAL_QUERY]
// CDS Query like the normal query ZLR_2STRUCT_CELL_CAL
define transient view entity ZLR_2STRUCT_CELL_REF
provider contract analytical_query
as projection on ZOQ_FLIGHT
{

//Elements of the Key Figure Structure
@AnalyticsDetails.query.axis: #ROWS
@EndUserText.label: 'Max Seats'
seatsmax,

@AnalyticsDetails.query.axis: #ROWS
@EndUserText.label: 'Occupied Seats'
seatsocc,


//Elements of the Characteristic Structure
@AnalyticsDetails.query.axis: #COLUMNS
@EndUserText.label: '2020'
@AnalyticsDetails.query.onCharacteristicStructure: true
case when flyear = '2020' then 1 else null end as year2020,

@AnalyticsDetails.query.axis: #COLUMNS
@EndUserText.label: 'Occupied %'
@AnalyticsDetails.query.onCharacteristicStructure: true
case when flyear = '0000' then 1 else null end as yearPlaceholder,


abap.unit'%' as unitPercent,

//Help cell - used in formula of exception cell
@Aggregation.default: #FORMULA
@AnalyticsDetails.query: {
  isCell: true  
}
@Consumption.hidden: true
// scalar function with use of cell refernce
ratio_of( portion => GET_CELL_REFERENCE_VALUE(measure_struc_element => $projection.seatsocc, characteristic_struc_element => $projection.year2020 ),
total   => GET_CELL_REFERENCE_VALUE(measure_struc_element => $projection.seatsmax, characteristic_struc_element => $projection.year2020) )  as helpCellratio,


// Exception cell 
@Aggregation.default: #FORMULA
@AnalyticsDetails.query: {
  isCell: true,
  cellReference: {
    measureStructureElement: 'seatsocc',
    characteristicStructureElement: 'yearPlaceholder'
  
  }
}
@AnalyticsDetails.query.decimals: 2
@Semantics.quantity.unitOfMeasure: 'unitPercent'
$projection.helpCellratio * 100 as exceptionCellRatioPercent

 
}

Output

More information can be found Cell, Exception Cell and Help Cell | SAP Help Portal

CDS: How to use AnalyticsDetails.query.ignoreFurtherFilter in Analytical query (Constant Selection)

2025-03-04T13:26:32.355000+01:00

This blog is about how to use @ AnalyticsDetails.query.ignoreFurtherFilter in Analytical query to define a constant selection as like in BW query (see Note 944815).

‘Ignore filter’ is a property that influences the effect of filters on cells, in classic BW it is called as ‘Constant selection’. It is used to define a selection in query definition as fixed value. Navigation and filters then have no effect on this selection at runtime.

This feature is useful to calculate e.g., Market Index. More information about constant selection can be found Constant Selection | SAP Help Portal

@ AnalyticsDetails.query.ignoreFurtherFilter

annotation is used to model 'constant selection' in the Analytical Engine.

The value of each cell in a query result set is determined by different filters acting on this cell. These filters are from the structure element or key figures itself or global filters and drill down.

Sometimes there is a need that not all filters should be applied, therefore with this annotation filters on certain dimensions or on all dimensions can be excluded.

@AnalyticsDetails.query.ignoreFurtherFilter.forElement: Global filters and filters from drill down will not be applied on the structure element for the elements listed in the array.

@AnalyticsDetails.query.ignoreFurtherFilter.forAllElements: No global filters and no filter from drill down will be applied on the structure element.

Example

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'IGNOREFILTER- constant selection'
@ObjectModel.modelingPattern: #ANALYTICAL_QUERY
@ObjectModel.supportedCapabilities: [#ANALYTICAL_QUERY]
define transient view entity ZLR_PC_IGNOREFILTER1
provider contract analytical_query
as projection on ZDMO_I_FLIGHTCUBE
{
  
  @AnalyticsDetails.query.axis: #ROWS 
  AirlineID,

  @AnalyticsDetails.query.axis: #ROWS 
  @AnalyticsDetails.query.totals: #SHOW
  ConnectionID,

  
  CurrencyCode,
   
  
  @EndUserText.label: 'Price in 2024  '
  @Semantics.amount.currencyCode: 'CurrencyCode'
   case when FlightYear = '2024' then Price else null end as priceIn2024_without,
   
   
  @EndUserText.label: 'Price in 2024 for Airline'
  @Semantics.amount.currencyCode: 'CurrencyCode'
  @AnalyticsDetails.query.ignoreFurtherFilter.forElement: ['ConnectionID' ]
  case when FlightYear = '2024' then Price else null end as priceIn2024
 
}
where AirlineID = 'AA' or AirlineID = 'AZ'

Output

In the above example column 'Price in 2024 for Airline' shows the total price for airline, as 'ConnectionID' filter is ignored with annotation @AnalyticsDetails.query.ignoreFurtherFilter.forElement: ['ConnectionID' ]

Constraint

This feature is only available in Analytical query

CDS: How to use @AnalyticsDetails.elimination annotation to eliminate the internal business volume

2025-05-26T21:35:47.915000+02:00

This blog is about how to use @AnalyticsDetails.elimination to eliminate the internal business volume when executing an analytical query.

Internal business volume

When revenues made between two subsidiaries of company, for company’s total revenue, these revenues should not be considered, as transaction is happening within the company. For example, a company is divided into several subsidiaries. These subsidiaries are divided into further subsidiaries. This means there exists a hierarchy of subsidiaries. Subsidiaries are selling products to each other. For each subsidiary this is external sales. But for a parent subsidiary this is just internal sales, as both subsidiaries are descendants. By using this annotation, revenues made between two subsidiaries in an organization are no longer displayed.

More information about the concept can be found Elimination of Internal Business Volume | SAP Help Portal

Syntax

elimination: {

pair : array of {

dimension1: String(30);

dimension2: String(30);

}

rule : String(20) enum { ELIMINATE_IF_ALL; ELIMINATE_IF_ONE; };

}

The annotation can be used in cube-views (Analytics.dataCategory: #CUBE) or in analytical queries (define transient view entity with provider contract analytical query).

pair: this list defines the pairs (dimension1 and dimension2) which are checked for elimination. Both dimensions have needed a foreign key association to the same target view. If the annotation is used on cube level, both dimensions must be elements of the cube. If the annotation is used in an analytical query, both dimensions must be part of the source cube view.
rule: if set to #ELIMINATE_IF_ALL, then the volume is eliminated if all pairs are internal. If set to #ELIMINATE_IF_ONE the volume is eliminated if at least one pair is internal. If "rule" is not set, the AND-logic (ELIMINATE_IF_ALL) is applied.

Example

Following example displays the number of seat booked in flight according to the elimination rule specified on destination airport, departure airport, destination country, departure country.

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Elimination of Internal Busniess volumn'
@ObjectModel.modelingPattern: #ANALYTICAL_QUERY
@ObjectModel.supportedCapabilities: [#ANALYTICAL_QUERY]
define transient view entity ZLR_PC_FLIGHTICE_SIMPLE
  provider contract analytical_query
  as projection on ZOQ_FLIGHT_ICE
{

  _airportfrom._hier( p_HierarchyID : 'GEO' ) as _airportFromHier,
  @Consumption.hidden: true
  _airportfrom.AirportID                      as dummyAirportFrom,


  _airportto._hier( p_HierarchyID : 'GEO' )   as _airportToHier,
  @Consumption.hidden: true
  _airportto.AirportID                        as dummyAirportTo,
  
  @AnalyticsDetails.query: {
    axis: #ROWS,
    displayHierarchy: #ON,
    hierarchyAssociation: '_airportFromHier'
  }
  
  airportfrom,
  
  @AnalyticsDetails.query: {
    axis: #ROWS,
    displayHierarchy: #ON,
    hierarchyAssociation: '_airportToHier'
  }
  airportto,

  @Consumption.filter.defaultValue: 'DE'
  @AnalyticsDetails.query.axis: #ROWS
  countryfrom,

  @AnalyticsDetails.query.axis: #ROWS
  countryto,

  seatsmax,



  @AnalyticsDetails.elimination: {
    pair: [{ dimension1 : 'countryfrom' , dimension2: 'countryto' }]
  }
  @EndUserText.label: 'SeatsMax Q-ICE country'
  seatsmax                                    as seatsmaxICEQ_C,


  @AnalyticsDetails.elimination:{
    pair: [ { dimension1 : 'airportfrom' , dimension2: 'airportto' },
            { dimension1 : 'countryfrom' , dimension2: 'countryto' } ],
    rule: #ELIMINATE_IF_ALL
  }
  @EndUserText.label: 'SeatsMax Q-ICE airport and country'
  seatsmax                                    as seatsmaxICEQ_AC,


  @AnalyticsDetails.elimination:{
    pair: [ { dimension1 : 'airportfrom' , dimension2: 'airportto' },
            { dimension1 : 'countryfrom' , dimension2: 'countryto' } ],
    rule: #ELIMINATE_IF_ONE
  }
  @EndUserText.label: 'SeatsMax Q-ICE airport or country'
  seatsmax                                    as seatsmaxICEQ_A_C


}

Output

In this example for columns (cells marked with colour):

SeatsMax Q-ICE country – elimination pair mentioned as 'countryfrom' and 'countryto'. Therefore, there is no entry where departure country and destination country are same.

SeatsMax Q-ICE airport and country- elimination pairs are 'airportfrom' and 'airportto', 'countryfrom' and 'countryto' And rule as #ELIMINATE_IF_ALL, Therefore, there is no entry where destination airport and departure airport are same AND destination country and departure country are same.

SeatsMax Q-ICE airport or country - elimination pairs are 'airportfrom' and 'airportto', 'countryfrom' and 'countryto' And rule as #ELIMINATE_IF_ONE, Therefore, there is no entry where destination airport and departure airport are same OR destination country and departure country are same.

Constraints

The annotation can be used in cubes or in queries.

The dimension names in one pair (AnalyticsDetails.elimination.pair) must have a foreign key association to the same dimension view and this dimension view must have an hierarchy association.
In the query definition:

It is not necessary that any of the dimensions in the list of pairs is part of the query
If a hierarchy is assigned to a dimension, then the pair dimension must be assigned to the same hierarchy or must be without hierarchy
If a dimension is not in drill down, then the condition of the one pair is always true (independent of the value of the other dimension of the pair). The same is true on totals/subtotal lines.

Exploring CDS based Analytical Models with the Relation Explorer - analytical view/perspective

2025-10-01T16:39:40.313000+02:00

Relation explorer analytical view / analytical perspective makes it easy to get an overview of the analytical model with very less clicks. No need to open all the views to understands details.

We start small , looking to a branch of a star schema , dimension Connection ( /DMO/ANA_I_Connection ) which is part of the flight data model. After calling the relation explorer we see the Relation Explorer Tab in the below section of the screenshot.

Relation Explorer tab shows:

in the left pane the associations from the dimension to other CDS views over all levels are visualizes . It starts fully expanded!
next to the CDS view name we see the view type. E.g. /DMO/ANA_I_CARRIER is of type [Dimension]
in the right pane one can see all the elements of current view. As /DMO/ANA_I_Connection is selected all elements of this dimension are displayed.
- One can select (single click) any other view e.g. /DMO/ANA_I_CARRIER and the right pane get updated with the elements of that view.
- double clicking the view will directly open the view
the right pane displays all elements grouped by roles.
- In this example we have 2 keys and e.g. expanding AirlineID show label and additional details about association and InfoObject. In case of compounded parent we would have seen the Parent element.
- double clicking AirlineID highlight the element in the source ( see line 21 )
- [Text] gives a hint that AirlineID has text, this is missing for ConnetionID -> no Text supported
- Attributes list all dimension attributes. Last one, DistanceUnit is a Unit element.
- the Unit group show all unit related elements.
- other group are shown if relevant.

One can also start the analytical Relation Explorer based on query or cube view.
In both cases the cube view is opened and visualizes the cube with all associations .

We change focus and look to the example of a query - starting relation explorer shows the cube definition including dimension Connection from above.

with one view

in the left pane we get all associations visualizes. View names are shown with the view types
in the right pane we can see all 13 dimensions of the cube and get if dimension support Text, have Attributes or Hierarchies
- from 1st screenshot we already know that Text, Attributes and Hierarchies are available for AirlineID
- expanding ConnectionID show that it is compounded to AirlineID
we see all 5 measures with additional details like aggregation method and unit
with " Units (2) " we see the unit related dimensions. This section only list those dimension that are unit relevant. Expanding the dimension like CurrencyCode lists all related measures.
( Both dimension are also listed in dimension section. )
for time based dimension one can directly understand the base dimension and wherefrom it is derived without looking into the source ( see below snippet with FiscalYearMonth )

How to start the Relation Explorer

call relation explorer to see the view

right click somewhere in the CDS view

( in case of CDS view type cube, dimension or query the analytical view is the default view )

If the view is not shown, choose Configure Context and activate it.
one can switch any time to different perspective / context if needed

Release Info: analytical view / analytical perspective started with

BW/4HANA 2023 FP 04
S/4HANA Public Cloud and Privat Cloud OP2023