SAP S/4HANA Embedded Analytics – A detailed Walkthrough (Part 2)

Hi All,

S/4HANA is steadily gaining shape in the market and so is the S/4HANA Embedded Analytics.

Part1 of the Blog can be found here –>

http://scn.sap.com/community/s4hana/blog/2016/03/10/sap-s4hana-embedded-analytics-a-detailed-walkthrough-part-13

Part3 of the Blog can be found here –>

SAP S/4HANA Embedded Analytics – A detailed Walkthrough (Part 3)

Part4 of the Blog can be found here –>

SAP S/4HANA Embedded Analytics – A detailed Walkthrough (Part 4)

Part5 of the Blog can be found here –> SAP S/4HANA Embedded Analytics – A detailed Walkthrough (Part 5)

Introduction:

What is S/4HANA Embedded Analytics?

               It is a set of Analytical Features integrated in SAP S/4HANA, that enables users to perform real time analytics on the live transactional data. It comes with a set of inbuild representations of operational data, called VDM (Virtual Data Models) which will allow users to arrive at better decisions from the available data.

SAP Best Practices for Analytics with S/4HANA: (RDS now be renamed as Best Practices) (Available in SMP since March 7th 2016– http://service.sap.com/analyticswiths4h) (V1.0)

               SAP Best Practices for analytics with SAP S/4HANA provides a comprehensive portfolio of analytical content based on SAP S/4HANA. It provides guidance on how to get started with SAP S/4HANA embedded analytics and how to integrate with best in class analytical platform and solutions from SAP for ex: SAP BI platform, SAP BW etc.

3 Options/Scopes:

1) Embedded Analytics with SAP S/4HANA (Mandatory)

2) Integration between SAP S/4HANA and SAP BO (Optional)

3) Integration between SAP S/4HANA and SAP BW (Optional)

My Personal opinion here is with SAP S/4HANA Embedded Analytics, SAP BW (Embedded BW) has got a lot of significance.

CDS Annotations:

I am not going to take you through the entire Annotations topic here but would rather concentrate on the ANALYTICS ANNOTATIONS:

It enables the analytic manager for multidimensional data consumption, performing data aggregation, and slicing and dicing data.

Some Relevant Analytical Annotations are as following:

a)   Analytics.dataCategory

By specifying the data category, the developer can give directives and hints, for example, tell the analytic manager how to interpret individual entities.

Possible values are:

@Analytics.dataCategory: #DIMENSION, #CUBE, #FACT, #AGGREGATION LEVEL

b)   Analytics.query

Query view classification. By tagging the CDS view, the developer can specify which views will be exposed to the analytic manager.

Possible values are:

@Analytics.query: true, false

c)   Analytics.dataExtraction.enabled

Application developers can use this annotation to mark views that are suitable for data replication (for example, delta capabilities must be provided for mass data)

  @Analytics.dataExtraction.enabled : true, false

d)   Analytics.hidden

You can use this flag to decide whether the entity should be visible to analytic clients.

@Analytics.hidden: true, false

e)   Analytics.planning.enabled

You can use this annotation to define an input-enabled analytic query

@Analytics.planning.enabled : true, false

f)    Analytics.writeBack.className

Only relevant for Analytics.dataCategory: #CUBE or Analytics.dataCategory: #FACT.

Disclaimer : The above contents are extracted from help.sap.com

Its Worth Noting that all S/4HANA CDS views are automatically exposed as a ODP transient Info Provider/Bex Queries.

We would be leveraging this functionality extensively in the subsequent sections.

3.A) SAP BW Bex Query

Select Search for the required Object(Transient Provider View)

{ 

Hope you remember that we had defined the SQL View name of the CDS with the annotation @Analytics.datacategory : CUBE is IFIDAYSSLSOUTSTG. (in Part 1 of this Blog Series)

The Transient Provider naming convention is 2C*.

So Prefix 2C with the SQL view and search with that in Bex Query designer:

(2CIFIDAYSSLSOUTSTG)

}

The Step by Step process for exposing CDS View to Bex have been explained in the below Blog:

http://scn.sap.com/community/bw-hana/blog/2016/02/10/expose-cds-views-to-sap-bw-bex-query-designer

3.B) RSRT in BW:

Select Search for the required Object(Transient Query View)

{

Hope you remember that we had defined the SQL View name of the CDS with the annotation @Analytics.query: true is CFIDAYSSLSOUTSTG. (in Part 1 of this Blog Series)

The Transient Provider naming convention is 2C*.

So Prefix 2C with the SQL view and search with that in Bex Query designer:

(2CCFIDAYSSLSOUTSTG)

}

4)  SAP Lumira

Open Lumira from your Desktop.Click New –>

Some times, the BW Connector will not be available (Like Below Screen)

For Solving that, Go to the Extensions:

Search for SAP BW Data Acquisition Connector

Download and Restart Lumira

After Reloading you can see the connection “Download from SAP BW”.

Click on that and Press Next:

Connect to Local BW System (Embedded BW in S/4 HANA System).

Provide the credentials of S/4HANA System and Proceed.

Select Search for the required Object(Transient Query View)

{

Hope you remember that we had defined the SQL View name of the CDS with the annotation @Analytics.query: true is CFIDAYSSLSOUTSTG. (in Part 1 of this Blog Series)

The Transient Provider naming convention is 2C*.

So Prefix 2C with the SQL view and search with that in Bex Query designer:

(2CCFIDAYSSLSOUTSTG)

}

Select and Proceed.

The Parameters defined in CDS will appear here (above screen)

Provide the Parameters and Press OK

Drag the Required Dimensions and Measures and Press Create.

You will see that the Dataset is getting created.

Arrange the Dimensions and Measures.

This Completes the S/4HANA Embedded Analytics – Lumira Scenario.

Hope you are already aware that now we don’t have Publish to Lumira option. Instead publish it to the SAP BI Platform (out of Scope in this blog).

Thanks for going through the Document. Do let me know your Reviews and Suggestions.

BR,

Prabhith