Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

In Development - please don't rely on this wiki page currently - we're in development!


The information in this wiki page is in development and MUST NOT be relied on in anyway whatsoever!

We are currently building these pages and the information held here is likely to be incorrect as we develop it.

This info will be updated when we feel the information here can be relied upon - until then please refer to the main System Requirements page



The purpose of this wiki page is to collect information from various official sources and present them together here. Where possible official references will be mentioned.

Thus, information here is not to replace anything from official System Requirements page, nor will any information held here override anything mentioned in the official System Requirements. Official source information ALWAYS overrides anything mentioned in this wiki.



Live Model Support

 CloudOn PremiseReference page(s)Comments

(tick) (C) (D)

(tick) (A) (B) (C) (D)

  • (A) If using choropleth layer when working with geospatial models you must download and import the new version of the delivery unit, SPATIAL_DATA-1.1.6.tgz. Access to this delivery unit requires an SAP HANA Spatial license.
  • (B) HANA 2.0 is supported for On-Premise: SAP HANA 2.0 SP01 or newer on-premise, with the SAP HANA EPMMDS plugin installed on your SAP HANA 2.0 system. SAP Note 2456225 and SAP Note 2444261 provide additional setup information.
  • (C) for HANA 1.0 recommended to use SPS12 revision 122.14 or higher (to benefit from blending and other capabilities such as Aggregation Calculations (avg, count, min/max), Time Calculations (Previous Year/Quarter/Month, Year/Quarter/Month To Date.'Difference From'), Variances(Time,  Version and Measure), Blending (see below))
  • (D) can only consume HANA Calculation Views


  • SAP BW running on any DB
  • SAP BW running on SAP HANA





  1. Support Matrix for SAP BW
  1. SAP Note CDS Transient Provider: CX_RODPS_OBJECT_NOT_FOUND shows additional requirements on BW
  2. Supported versions:

    1. SAP BW 7.5 SP8+ (recommendation)

    2. SAP BW 7.4 SP17+

    3. SAP BW/4HANA SP4+

    4. Latest correction notes must be applied for the versions listed above. See SAP Note 2541557.

  3. SAP Note 2541557 also contains additional information on the following:

    1. Support versions prior to SAP BW 7.5 SP8

    2. Support versions of SAP BW 7.51 SP2+ or SAP BW 7.52

    3. Support versions prior to SAP BW 7.4 SP17

  4. Can connect to ABAP-based CDS queries (these can also be acquired using the BW acquisition connector)



  1. A BEx Query is required if querying a CDS view or a HANA calculation view.

  2. A single SAP Analytics Cloud story can not display a visualisation from a BEx Query based off a CDS View, AND a visualisation from a BEx Query based off a HANA calculation view. Its one or the other, not both at the same time within the same story.

Universe (tick) 
  • Universes are hosted within on-premise software. The on-premise software can be hosted in the Cloud with a supported IaaS provider.

Related and useful references:

  1. Error "Failed to connect to system in SAP Analytics Cloud" when defining a live connection - KBA 2544696

Live HANA Support

   Reference page(s)Comments
PredictiveTime series forecast on Analytic Model(tick)Limitations to SAP HANA and SAPCP Live Data Connections
  1. A time series chart is required and the model must have a time dimension to support this.
Smart Grouping(tick)utube tutorial 
TIme series forecast on Planning Model(error)  

Smart Insights

Smart Discovery, including Simulation(error)  
Planning (error)  
Hierarchy on Dimensions and Measures? (tick) 
  1. Parent-child hierarchy support only

Useful or related articles

  • HANA On Premise: InA role missing after HANA update SAP Note 2315536

Live BW Support


Live Universe Support

  Reference page(s)Comments


Live Model Connection Support

 Reverse Proxy 'PATH'CORS 'DIRECT'Single Sign-on (SSO)Reference page(s)Comments
HANA (on premise)


(tick) (B)

  1. (B) The SSL server certificate of the HANA XS system must be a valid one that is trusted by your users’ web browsers (see SAP Note 2502174 for details)
HANA (Cloud)



BW (on premise)


(tick) (A)

  1. (A) requires BW 7.52 onwards. See blog
S/4 (on premise)(tick)(error)   
S/4 (Cloud)(tick)(error)   
Universe(tick) (C)(tick) (C) (D)(tick) (E) 
  • (C) required BI 4.2 Support Pack 4 or greater
  • (D) the web application server fronting the SAP BI Platform must be configured for SSL
  • (E) SAML setup required on BI Platform. Each user must have an enterprise alias.


Reverse Proxy Support

Sometimes a reverse proxy server is required between the users browser and the SAP Analytics Cloud when connecting to an on premise data source.

Reverse Proxy Support for 'PATH' connections

The following table summarises what is supported.

 ApacheSAP Web DispatcherReference Page(s) 
HANA (on premise)



HANA (Cloud)    
BW (on premise)(tick) (A) 
  1. (A) Live Data Connection to SAP BW via HTTP Server
S/4 (on premise)    
S/4 (Cloud)    
Reverse Proxy Support for 'DIRECT' connections

Here the reverse proxy is just translating the CORS HTTP Headers so the remote data source sees that the source application is the reverse proxy. Don't forget that the source must trust the reverse proxy!

 ApacheSAP Web DispatcherReference Page(s)Comments
HANA (on premise)    
HANA (Cloud)    
BW (on premise)    
BW (Cloud)    
S/4 (on premise)    
S/4 (Cloud)    

Requirements for all direct connections

  • Communication from the browser to the database must use HTTPS and thus the browser must trust the SSL certificate being used. Some organisations have special policies around the use of which Trusted Authorities can be used.
  • The browser must support 3rd party cookies
  • The browser must allow pop-ups

Import Model Support


On premise source

via SAP Analytics Cloud Agent

Cloud sourceScheduleReference Page(s)Comments
Universe(tick) (C) (tick) 
  • (C) requires BI 4.1 SP5 or greater, or BI 4.2 or greater
Excel(tick) (tick)
  1. Blog on how to setup the Agent for scheduled imports
  • (A) The agent requires a small configuration change.
  • (B) Importing directly through the web browser is also supported, however only schedule imports can be made via Agent

Expose as an Odata source, then consume the odata source in SAC

SAC Agent requirements:

  • SAP Cloud Connector must be installed and configured on premise. Blog on how to setup the SAP Cloud Connector
  • If running the SAC Agent as a windows  services, then Environmental variables may not be read if the service runs as 'Local System Account', so for the properties path either start the service as a user (rather than Local System) or use the '-D' parameter.


  Reference Page(s)Comments
Hierarchy on Dimensions(tick) 
Hierarchy on Measures(tick) 
Hierarchy on Time(tick)
  1. Year-Quarter-Month-Day levels


Connection support (live verse acquired)


General Support for Universes
UNV Universes(tick)(error) 

Relational UNX Universes (Single and Multi Source)

Stored Procedure Universe(tick)(error) 
JavaBeans Universe(tick)(error) 
Multi-dimension Universes based off OLAP connection(error)  
Minimum BI Platform VersionBI 4.2 Support Pack 4 (A)BI 4.1 Support Pack 5
  • (A) Recommended to use BI 4.2 SP5 due to performance improvements made with that version
Web Application ServerTomcat 7Tomcat 7 
Model enrichment(error) (B)(tick)
  • (B) Planned
Query as a data source(error) (C)(tick)
  • (C) Planned
Multi language support(error) (D)(error)
  • (D) the connection to the BI Platform specifies the language used to connect to it and it does not change dynamically. The model thus uses the language and this is why a single language is currently supported. @Variable('PREFERRED_VIEWING_LOCALE’) will not change


Relational Universe Features
Data FoundationMultiple Contexts(error) (A) 
  • (A) Multiple contexts in the universe is possible. The requirement is a single 'run-time' context. All active objects (so ignoring all hidden/deprecated objects) must use only 1 context at run-time. For example multiple contexts are supported when used with @Aggregate_Aware objects as only 1 context is used. Multiple contexts resolved with JOIN_BY_SQL are not currently supported. There can not be any context prompt. Any Business Layer Security Profiles are ignored to determine the use of contexts when creating the model.
Data typesNumeric(tick) (D) 
  • (D) All numerics will be given a decimal format 0.00
Date, DateTime(error) (E) 
  • (E) Not currently supported. So any dates should be returned as Year, Month, Day numeric objects.
Measure ObjectsProjection Function 'sum'(tick) (B) (F) 
  • (B) The SQL must have an aggregation function (sum, min, max, avg, count etc.), this is best practice anyway.
  • (F) Display format is not supported, defaults to decimal 0.00
Projection Function 'database delegated'(tick) (B) (F) 
  • (B) The SQL must have an aggregation function (sum, min, max, avg, count etc.), this is best practice anyway.
  • (F) Display format is not supported, defaults to decimal 0.00
Projection Function 'min', 'max'(tick) (B) (F) 
  • (B) The SQL must have an aggregation function (sum, min, max, avg, count etc.), this is best practice anyway.
  • (F) Display format is not supported, defaults to decimal 0.00
Projection Function 'count', 'count without empty'(error)  
Projection Function 'average'(tick) (B) (F) 
  • (B) The SQL must have an aggregation function (sum, min, max, avg, count etc.), this is best practice anyway.
  • (F) Display format is not supported, defaults to decimal 0.00
DetailsDetail Objects(error)  
List of ValuesSimple List of values (just a single column of values)(tick) 
  • (J) Associated List of Values on objects are used by @Prompt only. For 'Data View', 'Input Control' and filtering, the list of values used is the list generated by the SELECT statement when run on its own. It means the object must be able to be run on its own in order to generate a list.
Complex List of Values (multiple columns, nested, hierarchical, prompt)(error) (K) 
  • (K) Planned feature
SecurityUniverse Overload / Business Security Profiles and Data Security Profiles / Security Access Level(tick) (C) 
  • (C) though any Business Security Profile is ignored to determine if a context is used at model creation time. Only 1 context is supported.
FiltersFilters (defined in the query panel) or BI Sets(error) (D)  
@ functions@Prompt (E), @WHERE, @SELECT, @AGGEGATE_AWARE, @Variable (H)(tick) (E) (H) 
  • (E) though there are currently limitations to the list of values
  • (H) @Variable('PREFERRED_VIEWING_LOCALE') is not currently supported. Means a multi-lingual universe requires an SAC model per language. The language of the model is the language used in the SAC connection to the BI Platform. so the value of PREFERRED_VIEWING_LOCALE is fixed and set at model creation time.
Universe Optimisations

Index Awareness, Select optimisation (DISTINCT_VALUES)

(error) (G) 
  • (G) The universe can be index aware but SAC will ignore any index awareness properties
SQL Optimisation (ANSI_92), Inline views (BOUNDARY_WEIGHT_TABLE) (I)(tick) 
  • (I) BOUNDARY_WEIGHT_TABLE is supported, however a linked universe will ignore this setting, instead the linked universe must be included and the table row count set for this to work.




Model Building

  Reference page(s)Comments
Geo coding by longitude and latitude(tick)
  1. Creating a Model with Coordinate or Area Data for Geospatial Analysis
Geo coding by name(tick)
  1. Creating a Model with Coordinate or Area Data for Geospatial Analysis
  1. USA State and County data only
  2. Plans for other countries (SAP internal reference FPA00-3706)


Points of Interest

Points of Interest Reference page(s)Comments
Create point of interest from a model


  1. Creating points of interest
  1. Currently the model must be acquired model, either a normal Analytic model or a Planning model.
  2. (SAP internal reference: FPA00-8140)
Create point of interest from a CSV or an Excel File(tick)
  1. Creating Point of Interest Data from a CSV or an Excel file

Creating point of interest from ESRI shape file(tick)
  1. Creating Point of Interest Data from an Esri Shapefile




SAP Analysis for Office

AcquiredAnalytical Model(tick) 
AcquiredPlanning Model(tick) 
Live (error) 

Useful links

  • utube connect to SAC from Analysis for Office


Stories and visualisations

Linking/Blending Models

Models Reference page(s)Comments
Model based off a Live Data with Model based off a Live Data(warning) 
  1. Story level linking is supported when the data sources are HANA with a Live Connection to the same HANA instance/tenant using the very same connection as defined inside SAP Analytics Cloud (2 connections sharing the same connection properties are not enough). For HANA 1.0 this requires SPS12 revision 122.14 or higher and for HANA 2.0 this requires SAP Notes 2456225 and 244261 (SAP internal reference FPA34-396)
Model based off a Import Data with Model based off a Live Data(error)  
Model based off a Import Data with Model based off a Import Data(tick)  


General features

  Live connectionImport connection 
Table and ChartsHierarchies and drill   (error)         
Create calculations   (error)         
Filter on Dimensions(tick)(tick)(tick)(tick)(tick)(tick)(tick)      
Filter on Measures   (error) (F)        
  • (F) define measure filters with @Prompt in universe
ChartRanking Top N filtering on hierarchies for charts and tables(tick)(error) (error)         
Ranking Top N filtering on flat dimensions(tick)(tick) (warning) (C)        
  • (C) officially not supported, but mostly works
Sorting   (tick)         
Waterfall Charts (tick)(error) (E)           
Time series Charts (tick) (B)(error) (E) (error)        
  • (B) limitations may apply... validating it soon
Variance Charts (tick) (A)(error) (E)          
  • (A) planned to be available from wave 2018.02 and this requires HANA 122.14 or newer
Geo features (tick) (D)(error) (E) (error) (error)      
TableTable totals, when a Top N filter is applied(tick)(error) (error)         
 Sorting   (error)         
  • (E) Planned to be resolved end of Q2 2018

Story Visualisation of GeoMaps

  Reference page(s)Comments
Show data from a single model(tick)
  1. Creating a GeoMap
Show data from multiple models in a single geomap visualisation(tick) 
  1. Currently linked models do not work in a GeoMap. This means if model A is Geo-coded, you can't link to it, from another model B, and expect the data to be geo-coded in Model B.
  2. Plans for future (SAP internal reference FPA34-612)




  • No labels