Describing Embedded Analytics
Describing Embedded Analytics
Describing Embedded Analytics
Objectives
After completing this lesson, you will be able to:
Describe the embedded analytical applications and capabilities
Analytics are embedded in SAP S/4HANA Cloud, which means the business data and analytical
applications that consume this data live within the same software stack. In addition, SAP Analytics
Cloud (SAC) is the engine running behind the scenes to power several analytical applications through a
live connection. This means a customer doesn't need to log into a separate SAC system to view analytical
reports; everything is in the SAP Fiori apps in SAP S/4HANA Cloud.
Note
An SAP Analytics Cloud (SAC) tenant will be visible in a customer's SAP Cloud Identity Services systems
(Authentication and Provisioning), because it's required to support the live connection between SAP
S/4HANA Cloud and SAC. Customers cannot log into the SAC system directly; they access it through the
relevant SAP Fiori apps (for example, Manage KPIs and Reports → Stories tab).
To understand the architecture of embedded analytics, visualize the SAP HANA database as
the foundational layer, where business data lives. Next, think of the top layer as the SAP Fiori
analytical applications where end users consume business data. These two layers cannot speak to each
other without something in between that's capable of transforming data from the database into different
types of analytical structures for the relevant Fiori apps. This middle layer is called the Virtual Data
Model (VDM), and is represented by Core Data Services (CDS) views.
Remember that many of SAP's cloud solutions previously existed as independent companies that were
acquired. This means the way in which data was structured and the coding language(s) used
were different for each solution. We needed a common language that could be used to understand data
from any of these solutions, in addition to data from third-party solutions, and bring it into analyses that
make sense with SAP S/4HANA Cloud business data.
The answer to this was Core Data Services (CDS), which provide a common set of domain-specific
languages and services for defining and consuming semantically rich data models. Essentially, CDS is
a universal language to read and process data across different software stacks. The VDM is a
structured representation of CDS views and provides direct access to SAP business data by exposing it
through a library of predelivered CDS view templates. You can also create your own custom CDS view
templates.
This information is relevant to partner LoB configuration experts because many standard business
processes have analysis tasks using analytical apps in the test script, or sometimes the entire purpose of
a business process test script is to identify and review relevant CDS views for a specific use case (for
example, Analytics - Purchase Order Visibility and Procurement Spend (2QU)). During the Fit-to-Standard
workshops, you will demonstrate and discuss relevant analytical application(s) with your customer
LoB experts to determine if there are requirements you need to implement to make the app(s) work for
their needs. For example, if there was a requirement to add a custom field to an app used in the business
process flow, you likely need to add that same field to the relevant analytical app or report. Or perhaps you
review the predelivered CDS views with your customer experts and none of the templates exactly fit what
they need. In this case, you could make a copy of the CDS view that's closest to what they need and add the
additional fields, dimensions, or other characteristics required. After creating the CDS view, how should
the data be visualized? The CDS view is a data source that can be pulled into different types of reports or a
custom analytical query. The analytical query can then be used as a data source for Data Analyzer Reports,
Multidimensional Reports, Review Booklets, and SAP Analytical Cloud Stories.
Note
Use the View Browser app to get an overview of all available Core Data Services (CDS) views (released
by SAP and customized) and run an analysis with a CDS view. If the existing CDS views don't meet the
needs of the customer, use the Custom CDS Views app to copy and customize an existing CDS view, or
create your own entirely custom CDS view.
To create a Cube or Dimension view for use in analytical scenarios. For example, you could create
a custom analytical query or a KPI (Key Performance Indicator) analysis from a CDS view.
To generate an external API to expose data from the SAP HANA database with an OData service.
For example, you could use the OData API to populate your custom selection of data fields in a
custom KPI or report. You could also use the OData API to expose a custom selection of data fields
to another SAP solution or third-party app for an integration scenario.
Note
Find the standard SAP-delivered CDS views for each line of business here and learn how to create custom
CDS views here.
Query Browser and Custom Analytical Queries Fiori Apps
Use the Query Browser app to get an overview of all available analytical queries (released by SAP and
customized) and run an analysis in the Web Dynpro Grid tool. If the existing analytical queries don't
meet the needs of the customer, use the Custom Analytical Queries app to copy and customize an
existing analytical query, or create your own entirely custom analytical query.
An analytical query is a collection of one or more fields of business data, with parameters and filters
defined to narrow down the data set. Analytical queries are multidimensional models, meaning they
combine several data inputs (dimensions) into one analysis, and are often consumed in multidimensional
reports, although they can be used as the data source input to generate any of the following:
Use the Manage KPIs and Reports app to view all SAP-delivered KPIs, Reports, and SAP Analytics
Cloud (SAC) Stories. You can also create your own custom KPIs, Reports, and SAC Stories based on data
sources from CDS views or analytical queries.
Note
You cannot edit SAP-delivered KPIs, Reports, and SAC Stories directly - you must first make a copy of the
original. However, only KPIs, Reports, and SAC Stories that are based on released CDS views or analytical
queries can be copied.
The following analyses can be created from the Manage KPIs and Reports app:
You can generate an SAP Fiori app to display on the launchpad for permissioned users from KPIs, SAC
Stories, and Reports (Generic Drilldown, Analytical List Page, Data Analyzer). Within the Manage
KPIs and Reports app, select the custom KPI, Report, or Story, then navigate to the Applications
tab to create an application for the launchpad.
Make sure to assign the app to a custom business catalog in the Custom Catalog Extensions app,
and assign the catalog to a business role. You'll also need to add the app to a custom launchpad page,
or to an existing launchpad page already assigned to the launchpad space mapped to the business
role so that it will actually display on the launchpad (instead of just being searchable through the enterprise
search). Customizing a launchpad space and page will be covered in a future lesson.
Note
As a partner LoB configuration expert, you are responsible for anything that falls within your line of
business expertise. This means if a business process is supported by one of the embedded intelligent
scenarios, there will likely be set-up instructions in SAP Signavio Process Navigator with prerequisites that
must be completed in the customer's development system tenant(s) to make the process function correctly.
Note
Learn more about Intelligent Scenario Lifecycle Management here.