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 -->
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)
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.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
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.
{
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)
}
{
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)
}
Thanks for going through the Document. Do let me know your Reviews and Suggestions.
BR,
Prabhith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 |