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 -->
Introduction:
What is S/4HANA Embedded Analytics?
It is the collection of all Analytical Features integrated in the SAP S/4HANA Suite that enables, Business users or end users to perform real time analytics or operational reporting on the live transactional data. It comes with a set of predefined and prepackaged representations of operational data. These representations called VDM (Virtual Data Models) allows business users to derive good insights into the data.
It doesn’t require a separate implementation. It is a part of the S/4HANA Software and is generally available with the new S/4HANA releases.
Customers and partners can extend the existing CDS Views VDM’s and build new ones in SAP S/4HANA.
Please be informed that SAP S/4HANA Embedded Analytics will not replace any existing SAP Solutions.
SAP strategy is to offer customers maximum choice and flexibility and more innovations and S/4 HANA Embedded analytics compliments existing SAP Solutions.
You can carry out all your operational reporting with S/4HANA Embedded Analytics. This can help you reduce the operational reporting load from your SAP BW Application. You might still need BW for your EDW which will help you analyze the historical data, data consolidation from multiple sources and intensive data analysis.
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.
We would be leveraging this functionality extensively in the subsequent sections.
3) SAP BW Bex Query
{
Hope you remember that we had defined the SQL View name as CFIDAYSSLSOUTSTG. (in Part 1of 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)
}
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
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 Info Area and Search for our Object
{
Hope you remember that we had defined the SQL View name as 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.
This is a 4 Part Blog Series. In the Subsequent parts, we will see more S/4HANA Embedded Analytics options. Stay Tuned..
BR,
Prabhith