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

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

Part2 of the Blog can be found here –>

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

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)

Part6 of the Blog can be found here –> https://blogs.sap.com/2017/06/30/sap-s4hana-embedded-analytics-a-detailed-walkthrough-part-6/

Part7 of the Blog can be found here –>  https://blogs.sap.com/2017/11/23/sap-s4hana-embedded-analytics-a-detailed-walkthrough-part-7/

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.

Now we will go through the various S/4HANA Embedded Analytics options:

5) Analysis Edition For Excel:

Open an analysis for Microsoft excel:

Access the Analysis Tab and click on the Select Data source option within “Insert Datasources”.

Skip the next screen:

Select the S/4HANA System:

Enter the system credentials:

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 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)

}

This indicates that tools like Analysis Excel is capable enough to understand the CDS generated backend Transient Provider as well as Transient Query.

The system will prompt for the Variables Screen which we have added in the CDS definition using Parameters:

Create the Final report according to your requirement.

A sample report is shown in the below Screenshot.

The above scenario is just an overview of how to bring in the CDS View in Analysis of Excel. Hence the later steps of how to showcase more flavours to the final report is not been explained in this blog.

6) SAP DESIGN STUDIO:

Open Design Studio

The Design studio application will open.

Create anew Analysis application

Provide a Application name and select a layout.

Add a Datasource

Select the S/4HANA System.

Provide the credentials:

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 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)

}

This indicates that tools like Design Studio is capable only to understand the CDS generated backend Transient Query and doesn’t understand Transient Provider.

Check the details:

Drag the data source from Left to the Right Pane and proceed with your requirement.

PS: My Skill in this tool is very bad. Hence don’t want to take a risk here, by designing a complex report.

Once you have completed your requirement, there is an option to “Execute Manually”.

The created application/report will look something like below:

7) Cloud for Analytics(C4A)/ New Name Business Objects Cloud(BOC):

The integration between S/4HANA Cloud  and BOC can be done through the following option. Again the approach of 2C* convention remains the same.

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

BR,

Prabhith