2. SAP ANALYTICS CLOUD(SAC)
● SAC is a Software-as-a-Service-Platform and cloud data
visualization tool from SAP.
● SAC offers a complete solution when it comes to
business Intelligence , analytics and planning
capabilities in a cloud environment.
● SAC is the analytics layer of the SAP Business
Technology Platform.
3. ● To connect your data sources , we should set up
some connections.
● SAC supports Live Data connections and Import Data
Connections.
● With data connected to SAC, we can set up Datasets
and Models.
● Build stories based on those models, create
dashboards, update data visualizations and perform
online analysis.
CONNECTIONS IN SAP ANALYTICS CLOUD
4. ● SAC connect both cloud and on-premise data sources
using live data connection.
● In live connection any changes in data will be reflected
in related dashboards .
● Builds the queries required to see your data in your
browser.
● Visualizations are rendered with the help of live data
connection in the Browser.
LIVE DATA CONNECTION
5. ● A direct live connection (using CORS) from SAC to your
SAP on-premise data source is a cross-site scenario.
● Data sources issues cookies for authentication and
session management. Every cookie has a domain
associated with it.
● The cookie’s domain doesn't match the SAC domain in
the user's address bar
● configure your SAP on-premise data source to issue
cookies with SameSite = None ; secure attribute.
SAMESITE COOKIE CONFIGURATION
6. ● Get/Post requests from the Web browser to SAP Analytics
Cloud are dedicated to metadata
● Get/Post requests from the Web browser to the IdP are
dedicated to SAML assertions.
● Get/Post requests from the Web browser to the on-premise
data source are dedicated to data.
LIVE CONNECTION INSIDE A ORGANIZATION DOMAIN
8. ● A reverse proxy is used with the specific purpose of publishing the on-
premise data source to the public Internet and again allowing a direct
CORS connection to the data.
● Your browser directly connects SAP Analytics Cloud, your IdP, and
backend data sources by securely unlocking the same-origin policy.
● Because of no additional devices, a direct connection enables better
performance.
● This configuration is easy to set up.
CROSS-ORIGIN RESOURCE SHARING LIVE CONNECTION
10. TUNNEL LIVE CONNECTION
● The Tunnel connection type is used to expose some of your data to
users outside of your corporate network, without giving them VPN
rights.
● Tunnel connections are slower than direct connections.
● Without the VPN access to Consultant’s network, tunnel connection
can give access to the report and its data, without compromising
Consultant’s network.
● you can access SAC URLs securely from your personal laptopDesktop
and mobile devices.
11. IMPORT DATA CONNECTION
● Data is imported (copied) to SAC, and changes made to the data in
the source system don't affect the imported data.
● The SAC Agent Simple Deployment Kit allows you to quickly get
your import data connections working.
● SAC agent is an on-premise data connectivity component that is
used to establish import data connections for the data sources
● share a connection ,this will allow user to create models as well as
delete and refresh data sources that are based on the connection.
12. ● While exporting a story to Google Slides, it will allow users to sign in to their
Google account and save the story to their personal Google Drive.
● A non administrator user must have the connection shared with them
before they can use the export to Google Slides option in the Stories area.
● A new administrator users can only manage the connection in the
Connection area only if the connection is first shared with them.
GOOGLE EXPORT CONNECTION
13. PERFORMANCE OPTIMIZATION TECHNIQUES
● Loading Invisible Widgets in Background to improve the application startup
performance
● Use the Pause Refresh API to optimize the performance of charts and tables
● Bind data directly using “Script variables” option for data source type. This way
you will be able avoid multiple loops.
● Use Hierarchies , Rank , Beta tables to Show Additional Details.
● Filter widget uses one reference data source.The same dimension filters have to
be applied to other data sources in the application.
14. PERFORMANCE OPTIMIZATION
❏ SAP Analytics Cloud enables you to perform analysis on large volumes of data.
❏ complex scenarios can sometimes lead to less than ideal performance times
for end-users.
❏ This performance optimization includes
❏ Modeling and Data
❏ Explorer
❏ Charts and Tables
❏ Filters
❏ Geo map
❏ Performance optimization is key consideration for usability of the application
15. MODELING AND DATA
● In Model Preferences under Data and Performance, toggle on “Optimize
Story Building Performance” prevents the automatic refresh of data during
story design
● When editing a story, designers can manually refresh data when desired
using the data refresh prompt in the builder.
● Whenever possible, choose to show unbooked data so that the software has
to spend less time differentiating between booked and unbooked data.
● Avoid specifying Exception Aggregations in the Model instead use the
Restricted Measures or Calculation functionality in your stories.
16. STORY DESIGN
● Use Responsive pages to re-flow the content depending on
the screen size it is being viewed on.
● you can add a hyperlink to a different page, story, external
website for reference.
‘
● Use pages to category story, limit pages and create different
stories for each use-case or audience.
● To ensure performance when working with blended data,
avoid creating Linked Dimensions on Calculated Dimensions.
● Keeping the no of models linked minimum will improve
overall speed and performance.
17. EXPLORER
● To cut down on scrolling and makes it easier to find the dimensions,
choose to show particular dimensions rather than all in the explorer .
● By turning off “Automatically Synchronize Visualization” button while
using explorer you can change your measure and dimension selections
without auto-refreshing the visualization.
● click the “Synchronize Visualization” button to update your
visualization.
● Story designers can choose to enable the explorer on charts and tables
while in view-mode.
18. CHARTS AND TABLES
● Lowering the no of individual data points make stories
easier to read and analyze.
● To display more cells , edit the drill limitation.
● Limit cells , the more cells you include, the harder SAC has
to work to display them.
● Use table filters to keep a manageable amount of
information visible in your tables.
● For a Dimension with a large Hierarchy use the chart drill
capability for best performance
19. GEOSPATIAL
● In SAC ,a bunch of Geo Map layers are there
which can be customized according to user
needs
● To optimize your bubble layer, switch on
Location Clustering and choose thousand for the
maximum no of display points.
● If you are working with thousands of locations
consider using the choropleth layer that
aggregates your data into shapes .
20. FILTERS
● For Stories based on the same information, try adding story
filter capabilities instead of individual filters for pages, charts, or
tables
● For members with large hierarchies, you can limit the number
of levels available in the filter for easy navigation.
● When drilling down, you can jump several levels at once to
avoid unwanted loading levels .
● Toggling off the Cascading Effect feature reduces query
volumes and can speed up filter performance.
21. BEST PRACTICES
● Reduce the no of foreach Functions and Limit Their Scope as Much as Possible
and replace foreach Functions with data Functions.
● Use the break Keyword to Avoid Unnecessary Iterations in foreach Functions or
reduce the Scope of foreach Functions.
● Larger images take longer to load , so use images less than 1 MB.
● Enable Planning on Tables Only When Planning Is Used.
● Expanded input control refreshes often and may affect the application's
performance,so use collapsed input control.