Terminology

Models

Live Model Support

	On Premise (or SAP HEC)	SAP Cloud Platform	SAP HANA Cloud	Key References	Additional Comments
HANA v1	(A) (C) (D)	(C) (D)	n/a	System Requirements Limitations to SAP HANA and SAPCP Live Data Connections
HANA v2	(A) (B) (D)	(D) (E)	n/a		String-based time dimensions or date dimensions that you want to enrich with time-hierarchy information requires a delivery unit to be installed on HANA. See KBA 2723743
HANA Cloud	n/a	n/a	(F)
BW SAP BW running on any DB SAP BW running on SAP HANA SAP BW/4HANA		n/a		Support Matrix for SAP BW SAP Note 2415249  - Using SAP Analytics Cloud as Client for SAP BW queries on BW 7.50 SAP Note 2715030 - Considerations when using SAP BW and SAP S/4HANA Live Connections in SAC SAP Note 2788384 Unsupported features with SAP BW, SAP S/4HANA and SAP BPC Embedded Model Live Connections in SAC	SAP Note CDS Transient Provider: CX_RODPS_OBJECT_NOT_FOUND shows additional requirements on BW Supported versions: SAP BW 7.5 SP13+ (SP16 recommended) SAP BW 7.4 SP17+ SAP BW/4HANA 1.0 SP8+ SAP BW/4HANA 2.0 SP0+ (SP4 recommended) Latest correction notes must be applied for the versions listed above. See SAP Note 2541557. Can connect to ABAP-based CDS queries (these can also be acquired using the BW acquisition connector)
BPC		n/a		Planning functionalities supported in SAC live connection to BPC Embedded Model SAP Note 2788384 Unsupported features with SAP BW, SAP S/4HANA and SAP BPC Embedded Model Live Connections in SAC	Embedded model
S/4				SAP Note 2715030 - Considerations when using SAP BW and SAP S/4HANA Live Connections in SAC SAP Note 2788384 Unsupported features with SAP BW, SAP S/4HANA and SAP BPC Embedded Model Live Connections in SAC	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		n/a			Universes are hosted within on-premise software. The on-premise software can be hosted in the Cloud with a supported IaaS provider. An additional license on the BI Platform is no longer required when connecting to a BI Platform 4.2 SP09 patch2 or higher, 4.3 SP01 patch 5 or higher, or 4.3 SP02 server

• (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. Recommended HANA 2.0 SP2 rev 024.05 or higher) with the SAP HANA EPMMDS plugin. 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) Typical HANA live connections can only consume HANA Calculation Views. A HANA based CDS view requires a HANA Calculation View to be created on it. However, a 'Data Set', that can be used for 'Smart Predict' can consume SAP HANA tables (row store or column store), and SAP HANA SQL Views. Perhaps confusingly, 'Data Sets' can not be based off HANA Calc Views.
• (E) HANA 2.0 is supported for SAP Cloud Platform regardless of where the SAP Analytics Cloud Service is hosted. When HANA 2.0 is hosted as a service (HANA as a Service, HaaS) then there are a few limitations: GeoMaps are not supported (though this is planned to be resolved soon). Data Blending is limited to HANA Calculation Views on the same HaaS. It means browser based and SDI-based data blending is not supported.
• (F) Star date join requires calculation view to be created.

Related and useful references:

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

Live Model Connection Support

Warning - a DIRECT connection can be changed to DIRECT+CC but not back again.

Browser Desktop Live Connection Support

DIRECT+CC is not applicable for the regular browser interface.

			HANA				BW (on premise)		BPC		S/4			Universe
			HANA (on premise)		HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)					S/4 (on premise) (L)		S/4 (Cloud) (L)
Required Components	SAP Cloud Connector (SCC)
	SAP Cloud Agent
Browser (desktop)	Connection	Type	DIRECT (B)	TUNNEL	CLOUD	CLOUD	DIRECT	TUNNEL	DIRECT	TUNNEL (planned 2022.5)	DIRECT (F)	TUNNEL	CLOUD	DIRECT (C) (D)	TUNNEL
	Authentication Support	Username and password			(K)						(I)	(I)
		SSO	SAML	SAML	SAML	SAML	SAML	SAML	SAML	SAML	SAML (I)	SAML (I)	OAUTH (M)	SAML (E)	SAML
		None (delegated, such as X509,  Kerberos, SAP Logon Token)
HTTP	Protocol		1		1	1	2 (O)		1				1	1

Mobile App Live Connection Support

DIRECT is applicable for the SAP Mobile Application, but it requires the Mobile device to be connected to the organisation network either directly, via a proxy (exposing the database) or via a Virtual Private Network. Typically a 'Direct' connection for mobile applications is not preferred.

TUNNEL is applicable for the SAP Mobile Application and means that the mobile device can enjoy live connectivity to on-premise source without the need for a VPN and without the need to expose the on-premise source directly to the internet (instead SAC will act as a proxy)

			HANA				BW (on premise)		BPC		S/4			Universe
			HANA (on premise)		HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)				BPC embedded (P)	S/4 (on premise) (L)		S/4 (Cloud) (L)
Required Components	SAP Cloud Connector (SCC)
	SAP Cloud Agent
Mobile App	Reverse Proxy (DIRECT connection)	Apache												n/a
		SAP Web Dispatcher
	Connection	Type for iOS	DIRECT	DIRECT+CC			DIRECT	DIRECT+CC	DIRECT	DIRECT+CC	DIRECT	DIRECT+CC	?	(H)
		Type for Android	DIRECT	TUNNEL			DIRECT	TUNNEL	DIRECT	TUNNEL	DIRECT
	Authentication	Username and password											?	(H)
		SSO	SAML				SAML		SAML	SAML	SAML	SAML	?	(H)
		None (delegated, such as X509,  Kerberos, SAP Logon Token)
HTTP	Protocol		1		1	1	2 (O)	2	1				1	1

Schedule Publication Live Connection Support

			HANA			BW (on premise)	BPC	S/4		Universe
			HANA (on premise)	HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)			S/4 (on premise) (L)	S/4 (Cloud) (L)
Required Components	SAP Cloud Connector (SCC)
	SAP Cloud Agent
Schedule Publication	Connection	Type	DIRECT+CC (N)			DIRECT+CC				DIRECT+CC	TUNNEL
	Authentication	Username and password
		SSO
		None (delegated, such as X509,  Kerberos, SAP Logon Token)

(the above table needs many improvements)

• 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)
• 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.
• F) previously this was not supported, though it is now. The documentation may appear to limit this to PATH only, however DIRECT connection is also supported
• G) Option to 'Save this credential for all users on this system'
• H) Currently not supported, please refer to the SAP Roadmap for details on the plan
• I) Username and password not supported (SAML is required instead) when S/4HANA on-premise is federated through an SAP S/4HANA Front-end server (FES) / SAP Fiori Front-end server (FES). Setup of the connection requires the user to have access to the S/4HANA backend system.
• K) HANA as a Service (HaaS) version 2 does not support username/password authentication, only SAML SSO is supported. When HANA is hosted on Cloud Foundry a custom IdP is required, the default IdP is not sufficient.
• L) S/4HANA means consumption via CDS views and not BW queries. BW query consumption is technically possible but not recommended.
• M) Could optionally use a different Identity Provider compared to SAP Analytics Cloud (unlike when S/4HANA is on-premise, when the same IdP must be used)
• N) Requires HANA 2.0
• O) HTTP 2 is 'disabled' when SPNego authentication is used, instead HTTP 1.1 is used which means a possible performance impact compared to other Authentication methods. Consider X509 certificate in this case. KBA 3126093
• P) Tunnel connection support for BPC embedded is only supported for the browser and not for SAC mobile applications.

Reverse Proxy Support

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

Limitations to SAP HANA and SAPCP Live Data Connections

Useful or related articles

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

BW System Requirements changes by wave

This table shows, by wave release, when on-premise BW system requirements change to benefit from additional SAP Analytics Cloud features for BW.

Importantly this is NOT a list of the changes to minimum BW System requirements. Please refer to the official System Requirements page found within the help pages within your SAP Analytics Cloud Service.

In general, we recommend applying the latest SAP Notes referenced by SAP Note 2541557 even if your SAP Analytics Cloud service is not yet on the related version. An 'older' Quarterly Release version will always be supported on the most recent notes referenced by SAP Note 2541557.

We strongly suggest for NW BW customers to upgrade at least to NW BW 7.50 SP16. For BW/4HANA customers we recommend to go to BW/4HANA 2.0 SP 4 which is planned for 2.2020. For S/4 customers we recommend release 1909. See also note 2715030 for the planned features on NW BW 7.50 SP16 ECC , BW/4HANA 2.0 SP 4 and S/4 in detail.

Live BW Support

BW feature		Supported in SAP Analytics Cloud
Table	Hierarchy - Show node above
Table/Chart	Use a fixed value for a dynamic variable (customer/BW exit variables)

Requirements https://launchpad.support.sap.com/#/notes/2541557

Live BPC Support

BPC feature	Supported in SAP Analytics Cloud
workstatus
Disaggregation
Formula
Cell Locking

Live Universe Support

SAP Analytics Cloud Wave and Live Universe Connector Support Matrix

Live Universe Connector Version	SAP Analytics Cloud Wave 2020.02 and onwards
Version 2.03 (v2 SP3)
Version 2.04 (v2 SP4)

KBA 2771921 Version 2 Release information and download

• Live Connection System Requirements
• Limitations to SAP Universe Live Data
• A single Universe context is supported, multiple Universe Contexts resulting in more than 1 dataset isn't supported.

Acquired Model Support

Agent Versions by Analytics Cloud Service Version

• A) There is no direct dependency between the SAP Analytics Cloud Agent and the SAP Cloud Connector. The versions listed are intended to be read 'for the SAP Analytics Cloud version (or wave)' listed only.
• B) The SAP Cloud Connector supported version is as listed, however this requirement is actually and currently only applicable for when SAP Analytics Cloud is hosted on a non-SAP data centre (Cloud Foundry) due to the IP addresses changing over time. See SAP KBA 2822078. If SAP Analytics Cloud is hosted on an SAP data centre then this technical issue will not be present and an older version of the SAP Cloud Connector can be used. This is not officially documented or communicated, the official documentation will state this version.  It is likely SAP Product Support would request an update to this version should an issue occur.

Acquired Model and Dataset Scheduling Support (Import and Export)

	Import		Export
	Model	Dataset	Model	Dataset
Universe
CSV, Excel	(B)
Odata Cloud
Odata on-premise
HANA via OData	(A)
HANA via JDBC	(C)
HANA (via Query Builder accessing all view types) or HANA (via Freehand SQL accessing all tables and procedures)	(G)
BW 7.5			(F)
BW4/HANA 2.0			(E)
SAP S/4HANA
BPC (D)			(Planned)
SAP IBP (SAP Integrated Business Planning)	(Planned)

Please note the table above is for 'schedule' support. There are many other data sources supported for manual exporting compared to scheduled exporting

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.
• Exports of model data is limited to 6 million rows of fact data and 1 million rows of calculations

References

• A) Expose as an Odata source, then consume the odata source in SAP Analytics Cloud see help
• B) The agent requires a small configuration change (see blog). Importing directly through the web browser is also supported, however only schedule imports can be made via Agent
• C) By using the 'Generic JDBC driver' option in SAP Analytics Cloud Agent
• D) For data acquisition (import), regardless of any scheduling, see SAP Note 2755379 to reduce memory consumption on BPC side.
• E) Requires BW4/HANA 2.0 Support Pack 4. SAP Note 2838883 - SAC BW Writeback - Part 1 for details on current restrictions
• F) Requires BW 7.5 SP18 SAP Note 2942754
• G) XS Classic and XS Advanced (XSA) Views are supported (XSA is the successor of XS Classic). XSA is supported with HANA 1.0 SPS12 and HANA 2.0.  XSA HAVA Views are not restricted to schema location of _SYS_BIC. XSA View prompts are supported)

Acquired Model Combining Data Support.

Modelling Supported Features

	Live Connections							Import Data Connections
	HANA (On-Premise)	HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)	BW	BPC	S4	Universe	Models	Datasets
Planning Models
Single Date Dimension							(E)
Multiple Date Dimensions								(C)
Parent-child hierarchy on Dimensions								(F)
Level-based hierarchy on Dimensions								(B) (F)
Hierarchy on Measures
Hierarchy on Date (Years to Days, which is 'Time')				(D)
Hierarchy on Time (Hours to milliseconds)
Convert a date or string-based time dimension into a time hierarchy (aka time enrichment)	(A)	(A)
Version (aka Category) (i.e. supports actuals, budgets etc.)
Cross Calculations on tables and charts

• A) Requires HANA 2.0 and HANA Model Date Enrichment DU. Enables consumption of time based features without the need to model in the source system. String-based time dimensions supports formats YYYYMMDD, YYYYMM and YYYYQ
• B) Maximum 8 levels
• C) Supported for both Analytical and Planning Models. For Planning models, only 1 fiscal date is supported, i.e. you can not currently have different dates for different fiscal periods.
• D) Supported for time series charts
• E) Supported to have a date dimension, but there are no date driven charts or calculations
• F) A dimension can have one or more level-based hierarchies, or one or more parent-child hierarchies, but not both.

Universe Support Matrix

General Support for Universes

	Feature	Live (2.0)	Live (2.1)	Live (2.2)	Live (2.3)	Live (2.4)	Import Data into a Model	Import Data into a Dataset
Build an SAP Analytics Cloud Model off a...	UNV Universes
	Relational UNX Universes (Single and Multi Source)
	Stored Procedure Universe
	JavaBeans Universe
	Multi-dimension Universes based off OLAP connection
	Web Intelligence Data Model (Web Intelligence document)
Platform	Minimum BI Platform Version	BI 4.2 Support Pack 5 or greater	BI 4.2 Support Pack 5 or greater	BI 4.2 Support Pack 5 or greater	BI 4.2 Support Pack 6 or greater	BI 4.2 Support Pack 7 or greater (but SP8 is recommended)	BI 4.1 Support Pack 5 or greater
	Web Application Server	Tomcat 7 and 8+ (C)	Tomcat 7 and 8+ (C)	Tomcat 7 and 8+ (C)	Tomcat 7 and 8+ (C)	Tomcat 9	Tomcat 7
Capabilities	Model enrichment	(D)	(D)	(D) (Planned)	(D) (Planned)	(D) (Planned)
	Define Universe Query as a data source for model definition
	Multi language support	(B)	(B)	(B) (Planned)	(B) (Planned)	(B) (Planned)
BI Platform authentication	Enterprise
	LDAP
	SAP
	Windows Active Directory
	Others

• A) Recommended to use BI 4.2 Support Pack 5 Patch 4 due to performance improvements with large data sets and scalability
• B) 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
• C) Needs JRE 8 or higher. SSL must also be configured. You cannot deploy BI Platform REST Web Services and Live Data Connect on the same Tomcat application server if you use SAML authentication
• D) Except you can: change data source, set dimensions to be hidden, rename dimensions and group dimensions.

Query as a data source Support Features

The live connector (v1.05 onwards) provides a query panel at the time of building a model in SAP Analytics Cloud. This section describes the features available with that query

		Live Connector Version 2.1	Live Connector Version 2.2	Comments
Results pane	Dimensions (with Data Type 'String', 'Numeric')
	Dimensions (with Data Type 'Date' and 'DateTime')			Objects of type 'Date' (not DateTime) are required for 'Time Series' Charts Objects of type 'Date' and 'DateTime' can not be filtered in the Story 'By Range', only 'By Member'
	Attributes (Detail objects)	(A)		A) They are not shown and so cannot be selected. For both measures and dimensions.
	Measures (with Project function: sum, count, average, min, max)
	Measures (with Project function: database delegated)			Due to the change in architecture with v1.05 this object type is no longer supported (officially it never was supported before, but it did work).
	Add a combined Query			It means performing a union, minus or intersect is not supported
	Maximum number of objects	150	150	Can be adjusted by editing the 'boe.properties' file and setting boe.nbMaxObjects to the number desired
Filters pane	Business Layer Filter			These can include prompts with/without list of values
	Dimensions of Types: String, Numeric			'String' data type objects in filters can have the following operators: Equal to, Except, Contains, Does not contain 'Numeric' data type objects in filters can have the following operators: Equal to, Except, Greater than, Greater than or equal to, Less than, Less than or equal to
	Dimensions of Type Date			'Date' data type objects in filters can have the following operators: Equal to, Except, Before, Before or Including, After, After Including
	Measures			'Numeric' data type objects in filters can have the following operators: Equal to, Except, Greater than, Greater than or equal to, Less than, Less than or equal to
	Prompts			Defining a new prompt is not supported. Prompts need to be defined in the Universe.
	Sub Query
	Database Ranking
	Nested filters with AND/ORs
List of values	Simple List of values			However there is a current restriction for objects defined with Index Awareness. It means the list of values shown in the query panels filter pane, when building the model, will show the Index Awareness values and not the actual 'SELECT' values as expected. This will cause the query to return no rows should any of the 'Index' values be selected. This is being tracked and under investigation (internal reference FPA55-852). It means you need to either enter the values manually, or avoid using a list of values on an Index Aware object.
	Cascading List of values
Display	Business Layer Views			Business Layer Views are supported, but you can not select the Business Layer View in the query panel to filter the objects seen.
	By Navigation Path			Hierarchies are supported, but you can change the view of objects to be listed by Hierarchies.
	Object Description			Shown as tooltip

Relational Universe Features

	Feature	Live (2.x)	Import Data	Comments
Data Foundation	Multiple Contexts			(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 types	Numeric	(D)		(D) All numerics will be given a decimal format 0.00
	Character
	Date, DateTime
Measure Objects	Projection Function 'sum'	(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'	(Planned)		(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'	(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'
	Projection Function 'average'	(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
Details	Detail Objects
Object Properties	Descriptions	(N)		(M) they are ignored (N) they are displayed as tooltips in the Query Panel when defining the model
List of Values	Simple List of values (just a single column of values)			(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.
	Multiple columns
	Cascading Prompts (which form a hierarchy)
	Nested, Hierarchical			These are list of values that are based on a custom hierarchy
Security	Universe Overload / Business Security Profiles and Data Security Profiles / Security Access Level			(C) though any Business Security Profile is ignored to determine if a context is used at model creation time. Only 1 context is supported.
Filters	Filters (defined in the query panel) or BI Sets
@ functions	@Prompt (E), @WHERE, @SELECT, @AGGEGATE_AWARE, @Variable (H)	(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)	(L)		(G) The universe can be index aware but SAC will ignore any index awareness properties (L) Currently this means the list of values shown in the query panels filter pane, when building the model, will show the Index Awareness values and not the actual 'SELECT' values as expected. This will cause the query to return no rows should any of the 'Index' values be selected. This is being tracked and under investigation (internal reference FPA55-852). It means you need to either enter the values manually, or avoid using a list of values on an Index Aware object. Objects with Index Awareness defined can be used in the model.
	SQL Optimisation (ANSI_92), Inline views (BOUNDARY_WEIGHT_TABLE) (I)			(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.

Planning Models

	Model based off ...
SAP Analytics Cloud Feature	BPC Live connection	BPC Import Data	File (generic Planning model)
Advanced Planning (Spreading / Allocations)
Predictive
Data Action
Value Driver Tree

Model and Dataset Formula

Model and Dataset Exception Aggregation Support

	Live Connections					Import Connections (Acquired Data)
	HANA	BW	BPC	S4	Universe	Models	Datasets
Count
Avg
Sum
Min
Max
First
Last
First Quartile	(A)
Median	(A)
Third Quartile	(A)

A) Requires HANA baseline level 5

Acquired Datasets Wrangling, Model Wrangling and Model Formula Support

(click to sort)	Available in Data Wrangling for Datasets	Available in Data Wrangling for all Import Data Connections (available before model creation). Also known as 'Basic Data Preparation'	Available in Modeller for Acquired Data Sources (available after model creation)
If		maximum depth 97 levels
SubString/SubStr
Trim
Contain/Contains
Concat/Concatenate
Replace
Length
Like
LowerCase
UpperCase
DateDiff
DateAdd
DayOfWeek
ToDate
MakeDate
Abs
Link
LookUp
Log
Log10
Int
Float
Double
Exp
GrandTotal
%GrandTotal
Mod
Min
Max
Sqrt
Power
Restrict
RestrictLookup
Round
ToNumber
ToText/ToString
Trunc
Ceil
Floor
Not
IsNull
CAGR (Compound Annual Growth Rate)
SMA (Simple Moving Average
YoY (Year over Year)
element
in
exp10
Inverse
InverseIf
FindIndex
Right
Left
EndsWith
To Integer
TitleCase
Split
Position
ReplaceContent
DayOfYear
DurationDiff
SecondsDiff
ToTime
TimeAdd
MakeTime
ExtractDay
ExtractMonth
ExtractYear
ExtractQuarter
DayName
MonthName
ToQuarterFormat

Geospatial

Model Building

		Reference page(s)	Comments
Geo coding by longitude and latitude		Creating a Model with Coordinate or Area Data for Geospatial Analysis
Geo coding by name		Creating a Model with Coordinate or Area Data for Geospatial Analysis	Countries, Region and Subregion are supported. Country can be ISO2, ISO3 or English names and is mandatory Regions and Subregions must be English names and are optional

Points of Interest

Points of Interest			Reference page(s)	Comments
Create point of interest from a	model		Creating points of interest	Currently the model must be acquired model, either a normal Analytic model or a Planning model. (SAP internal reference: FPA00-8140)
	CSV or an Excel File		Creating Point of Interest Data from a CSV or an Excel file
	ESRI shape file		Creating Point of Interest Data from an Esri Shapefile

Planning

General Planning

	BPC Live Connection	Data Import Connections
Data Actions
Value Driver Tree

Microsoft Office Integration

There are two products from SAP that offer integration between Microsoft Office and SAP Analytics Cloud

	SAP Analysis for Office Edition for SAP Analytics Cloud	SAP Analytics Cloud Add-in for Microsoft Office
Microsoft Excel On-line (and thus supported on non-Windows platforms)		(B)
Microsoft Excel Desktop		(A)
Available on all data centres		Cloud Foundry Only (SAP Data Centres are not supported)
Life-cycle management support for SAP Analytics Cloud (C)

A) Windows requires Microsoft Office edition 2002, or 2004, or 2005.

B) Supported browsers: Chrome, Safari, Firefox, Microsoft Edge.

C) Life-cycle Management support for SAP Analysis for Office edition for SAP Analysis for Office is supported when managed via the SAP BI Platform. Life-cycle Management is not currently supported with SAP Analytics Cloud since the Workbooks are not currently hosted inside SAP Analytics Cloud as a native application preventing them from being transported from one Service to another and allowing the workbook relationship to Service to be respected. i.e. the Model Service URL will always point to the current service where the Workbook would be stored in.

SAP Analysis for Office Edition for SAP Analytics Cloud

SAP Analysis for Office Edition for SAP Analytics Cloud (not standard edition)

		Planning use-case (write back)	Analysis use-case (read only)
Acquired	Analytical Model
	Planning Model
Live	HANA
	BW
	S/4
	Other

Useful links

• YouTube connect to SAC from Analysis for Office.
• KBA 2787445 - Live Model Support

SAP Analytics Cloud Add-in for Microsoft Office

		Planning use-case (write back)	Analysis use-case (read only)
Acquired	Analytical Model	n/a
	Planning Model
Live	all		Planned. DWC live connections expected first

Consumable Artifacts

Stories

Link Models (aka 'Blending'. Multiple data sources within a single visualisation)

Matrix to show which models can be blended to other models based upon the connection underlying the SAC model.				Secondary Model
				Live Connections							Import  Connections
				HANA		BW		S/4 HANA			Models	Datasets
				HANA	SAP Cloud Platform	BW on HANA or BW/4HANA	BW (on any DB)	S/4HANA On-Premise	S/4HANA Cloud	Others
Primary Model	Live Connections	HANA	HANA	NATIVE (A)							SDI (B) BROWSER (G)	SDI (B) BROWSER (G)
			SAP Cloud Platform		NATIVE (F)						(L)	(L)
		BW	BW on HANA or BW/4HANA			SDI (I) BROWSER (J)(E)	BROWSER (J)(E)	SDI (I) BROWSER (D)(J)			SDI (C)(D) BROWSER (J)(E)(D)	SDI (C)(D) BROWSER (J)(E)(D)
			BW (on any DB)			BROWSER (J)(E)	BROWSER (J)(E)	BROWSER (J)(E)			BROWSER (J)(E)(D)	BROWSER (J)(E)(D)
		S/4 HANA	S/4 HANA (On-Premise)			SDI (I) BROWSER (J)(E)	BROWSER (J)(E)	NATIVE (H)			SDI (C)(D) BROWSER (J)(E)(D)	SDI (C)(D) BROWSER (J)(E)(D)
			S/4HANA Cloud
			Others
	Import  Connections	Models		SDI (B) BROWSER (G)	(L)	SDI (C)(D) BROWSER (J)(E)(D)	BROWSER (J)(E)(D)	SDI (C)(D) BROWSER (J)(E)			NATIVE	NATIVE
		Datasets		SDI (B) BROWSER (G)	(L)	SDI (C)(D) BROWSER (J)(E)(D)	BROWSER (J)(E)(D)	SDI (C)(D) BROWSER (J)(E)			NATIVE	NATIVE

• A) 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. Story and Page Filtering on a measure is not supported with blended models.
• B) Requires HANA 2.0. Remote Blending will require aggregated data to be moved to SAP Analytics Cloud servers (and temporarily stored there) if the primary data model is the acquired model. Equally if the primary data model is HANA, then aggregated acquired data will need to be moved to HANA (and temporarily stored there) unless the model to blended is an account model, then the blending will occur in the SAP Analytics Cloud server. The SAP HANA system must have a full use license (currently), an SAP HANA runtime (REAB) license is planned to be supported. Data size limit (of the aggregated data) is 1 Million cells (and not limited by the 2 MB size as for Browser Based Blending)
• C) Requires SAP BW on HANA or SAP BW/4HANA. Blending is always processed in the SAP Analytics Cloud. BW aggregated data is held in SAP Analytics Cloud for 1 hour for blending purposes and then deleted. Restrictions: Two structure queries, Key Figure Model (temporarily restriction). SAP Note 2715871.  Tuple filters (filtering with multiple dimensions using the AND and OR operators) (which itself requires BW/4HANA 2.0 or BW on HANA 7.5 SP16 is not supported when blending.) For the minimum HANA requirements please see SAP Note 1600929
• D) Blending of date dimensions with BW is currently not supported.
• E) Tuple filters (filtering with multiple dimensions using the AND and OR operators) is not supported when using browser-based blending.
• F) Requires HANA 2.0. 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).
• G) Requires HANA 2.0 version 2.00.024.05 (EPMMDS 1.00.201815.00) or higher.  Blending will require aggregated data to be moved to SAP Analytics Cloud servers (and temporarily stored there) if the primary data model is the acquired model. Equally if the primary data model is HANA, then aggregated acquired data will need to be moved to HANA (and temporarily stored there)???. Data size limit (of the aggregated data) is 2 MB
• H) Story level linking is supported when the data sources are S/4HANA with a Live Connection to the same or different S/4HANA instance/tenant using the same or different connection as defined inside SAP Analytics Cloud
• I) Requires SAP BW on HANA or SAP BW/4HANA. Blending is always processed in the SAP Analytics Cloud. BW aggregated data is held in SAP Analytics Cloud for 1 hour for blending purposes and then deleted. Restrictions: Two structure queries, Key Figure Model (temporarily restriction). SAP Note 2715871.  Tuple filters (filtering with multiple dimensions using the AND and OR operators) (which itself requires BW/4HANA 2.0 or BW on HANA 7.5 SP16 is not supported when blending. Blending of 2 different queries from 2 different BW systems is supported as long as the BW systems fulfil the system requirements for blending.
• J) Requires one of the following:
  • BW 7.5 (On any database. See SAP Note 2737952 for more details)
  • OR SAP BW4/HANA 1.0 SP12 (See SAP Note 2737953 for more details).
  • OR SAP S/4 HANA on-premise.
    Data size limit (of the aggregated data) is 6 MB. Blending is always processed in the SAP Analytics Cloud. Aggregated data is held in SAP Analytics Cloud for 1 hour for blending purposes and then deleted. Restrictions: Two structure queries, Key Figure Model (temporarily restriction).
  • SAP Note 2715871. Blending of 2 different queries from 2 different BW systems is supported as long as the BW systems fulfil the system requirements for blending.
  • SAP Note 2541557. For S/4 HANA (on-premise) browser based blending support status and this includes the S/4 HANA (on-premise) with BW versions
• L) Not supported, but browser based blending does work with the combination of SAP Cloud Platform hosting HANA 2.0 when SAP Cloud Platform itself is on Cloud Foundry (not NEO)

Linking Variables (multiple data sources linked by the prompt/variable)

Matrix to show which models can be linked to other models based upon the connection underlying the SAC model.		Live					All Import connections (Models and Datasets)
		HANA	BW	S/4	BPC	Universe
Live	HANA
	BW		(A)
	S/4
	BPC
	Universe
All Import connections (Models and Datasets)

When linking variables there are two options: link 'intersecting data only', or 'all data'.

Once variables are linked, the user is only prompted once for the variable instead of multiple times

• A) BW can only 'intersect' data. BW hierarchy name and node variables are not supported

General features

Stories, Pages, Table and Charts

This section applies to tables and charts, subsequent sections may break out individual features by table or chart types

Features applicable for Tables and Charts

		Live connection						Import connections
		HANA	HANA Cloud Plat- form	BW	S/4	BPC	Universe	Models	Datasets
Measures	Create Measures: Calculated Measure / Restricted Measure						(M)
	Restricted Measures with constant selection on subset of dimensions									This is allows measures to have restrictions on dimension(s) such that those dimension(s) are fixed/constant, and hence all other filters or breakdowns should be ignored. This enables complex comparison calculations between multiple members of the same dimension. Examples include calculations across versions, comparison to exception aggregation, comparing all dimension members of one dimension to a specific member of the same dimension
	Create Measure: Difference from (this is comparisons over time periods, like YoY etc.)	(Q)
	Create Measure: Aggregation	(N)		(AI)	(AA)		(AG)			(N) SAP HANA models prior to version 122.14 do not support aggregations
	Create Measure: Date Difference (max, min, average, sum) on Y Q, M, Week, Day (B) (V)	(P) (Q)
	Filter on Measures (on: Story, Page, Widget)	(Q) (T)					(F) (Planned)
	Ranking Top N filtering on hierarchies
	Ranking Top N filtering on flat dimensions
	Sorting
	Currency Conversion						n/a
Dimensions	Hierarchical Drill						(AK)			need to revalidate, might not be supported
	Hierarchical expand / collapse
	Filter on Dimensions				(H)
	Dimension Linking (not blending)						(Planned)
	Calculated Dimension by concatenating two dimensions						(Planned)
	Calculated Dimension by grouping members	(B)
	Calculated Measure-based Dimensions	(Q)
	Custom Sorting of Dimensions	(Planned for tables. Charts supported today) (R)		(AM)
	Dynamic Filter									Dynamic Filter is ability to set the widget to use a different variable compared to the story variable
	Custom Hierarchy			(AJ)
Advanced Filter (tuple filters)	Tuple General Support (AND/OR)			(AE) (AO)	(AH) (AO)	(AE) (AO)
	Can Exclude
	Can contain Hierarchy			(AE)	(AH)	? (AE)
	Can filter Currency Unit
	Can be used with Blending
	Linked analysis support if the receiver widget already has a tuple filter applied
	Linked Analysis				(I)
	Dynamic Text in titles (Charts already supported, planned for tables)
	Thresholds			(Y)	(Y)
	Positioning of Currency/Scale (i.e. €50 v 50€) based on Service setting	(Q)		(S)				Planned?
	Hyperlink (enables dynamic URL containing dimension value)									Limited to 1 URL per widget (chart/table). Measure values can not be included in the URL. If needed, create a dimension of the measure. If more than one URL is needed consider Application Building

• M) requires BI 4.2 SP4 Patch 3
• AA) requires S/4HANA On-premise 1909 (SAP Note 2977218 is required) or S/4HANA Cloud 1911
• AE) requires BW/4HANA 2.0 or BW on HANA 7.5 Support Pack 16. Queries with two structures are not supported
• AG) requires your SAP Analytics Cloud service to be on version 2019.16 or greater. Supports Count, Count excluding Null, Count excluding 0 and null, Min, Max, Average. Conditional aggregation is not yet supported
• AH) requires S/4 HANA 1909 (on-premise) or S/4 HANA 1911 (cloud)
• AI) requires BW 7.5 Support Pack 16 or BW4/HANA with 2.0 SP0. See SAP Note 2715030.  First and Last aggregations can only contain one aggregation dimension, while other aggregations will have a limit of 5 dimensions
• AJ) also works with input controls. Requires BW 7.5 SP16 and SAP Note 2541557
• AK) supports universe drill paths (UNX) or universe custom hierarchies (UNV) and choose aggregation level in charts and tables (requires SAP Analytics Cloud 2020.5 (or 2020 Q2 QRC))
• AM) Requires BW/4HANA 2.0 SP4 or greater. See SAP Note 2715030
• AO) SAP Note 2788384 - "Unsupported Features with SAP BW, SAP S/4HANA and SAP BPC Embedded Model Live Connections in SAC" lists this as unsupported but that is only because the button, in the user interface, called 'Advanced Filtering...'  is not available. Advanced filters can still be created by selecting data points in the widget, its just the create dialogue isn't available.

Features particular to Charts

		Live connection							Import connections
		HANA (On-premise)	HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)	BW	S/4	BPC	Universe	Models	Datasets
Waterfall Charts	General Support				(Z) (AF)
Time Series Charts	General Support	(B)
	Apply fixed and dynamic filters to Time series charts (Y, Q, M, D, Hr, Min, S, mS, Current Y/Q/M)
	Time series chart hierarchies supported in the x-axis				Y, M, D
Variance	Measure compared with another Measure	(A?)
	Based on Version	(A)
	Based on Time Hierarchy	(U)			(X)	(X)
Histogram	General Support	(Q)
Dynamic Image Widget	General Support	(B)	(B)
GeoMaps	General support (see table below)	(D)	(AB)	(AN)	(E)	(AP)
	Hierarchies				(E)
	Custom Hierarchies				(AL)
Other chart types	General Support

• AB) HANA 2.0 on SAP Cloud Platform does not currently support GeoMaps. Planned feature (SAP internal reference FPA00-29155)
• AF) Waterfall charts on restricted key figures with the waterline dimension being used in the restriction or waterfall chart on 2 structure queries are not supported. See SAP Note 2415249
• AL) Requires BW/4HANA 2.0 SP4 or greater. See SAP Note 2715030. Supports also custom shapes
• AN) Attributes from location show up as dimensions when building a filter in the builder panel
• E) Supported in general, some exceptions: For GeoMap the Choropleth layer is supported for BW 7.5 SP16 or higher and BW/HANA 2.0 SP4 or higher. Please see SAP Note 2715030. The dimension needs to be configured in SAP BW as geo relevant. To use the choropleth layer in SAC, the attributes 0LONGITUDE and 0LATITUDE need to be maintained. Please refer to documentation for more details.
• X) Time granularity must include day level. Tuple filters are not supported. Variance on a single value range filters are invalid if the range is incomplete. Recommended comparisons using drill down is not supported.  Requires BW 7.5 Support Pack 16 and SAP Note 2786890. Support for BW4/HANA requires 2.0 SP4. See SAP Note 2715030. 
• AP) No support for Choropleth. Only supported with SAP delivered CDS views. Please see SAP Note 2715030 for details

Features particular to GeoMaps

		Live connection							Import connections (Models and Datasets)
		HANA (On-premise)	HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)	BW	S/4	BPC	Universe
Layer	Bubble
	Point of Interest
	Heat Map
	Choropleth			(A)
	Feature
	Flow
Geo Coding	by Long/Lat
	by Area Name
	ISO2 name
	ISO3 name
Feature	Distance Slider
	Intersection Filter
	Overlapping Geo Points
	Geo Chart Outliers
	Custom Tooltips
	Custom Choropleth Map				?

• (A) Available from Q4 2020 QRC (Wave version 2020.21 which is the QRC release). Requires 'Public Synonyms' to be enabled via System-Administration-System Configuration-Use Public Synonyms for Choropleth Layer. Requires HANA 2.0+ (SAP internal reference FPA00-29155)

Features particular to Tables

		Live connection						Import connection
		HANA	HANA Cloud Platform	BW	S/4	BPC	Universe	BW	BPC	Universe	General
Tables	Table totals, when a Top N filter is applied						(Planned)
	Sorting
	Custom Sorting of Dimensions	(Q)
	Export Data as CSV
	Re-order (custom order) measures			(AC)
	Re-order (custom order) account dimensions										(AD)

• AC) Ordering of measures is only possible when measures are not in a hierarchy
• AD) Ordering can be performed at the same hierarchy depth. You can not re-organise the hierarchy.

Explorer

		Live connection						Import connection
		HANA	HANA Cloud Platform	BW	S/4	BPC	Universe	BW	BPC	Universe	General
Exploration	Search on dimension value
	Exclude Dimension value
	Dimension sorting on hierarchies

KPI

		Live connection						Import connection
		HANA	HANA Cloud Platform	BW	S/4	BPC	Universe	BW	BPC	Universe	General
KPI	Create KPI
	Alerts				(J)							(J) except for SAP S/4HANA Cloud version 1702 when they are not supported

• A) planned to be available from wave 2018.02 and this requires HANA 122.14 or newer
• B) requires HANA 2.0
• D) Documentation reference, also SAP Note 2404590
• F) define measure filters with @Prompt in universe as workaround.
• H) Dimension members must not contain exclamation marks in description
• I) SAP S/4HANA Cloud version 1702, Linked Analysis workflows may return errors with no results. Errors may occur when filtering on a member in a chart that results in the creation of a story filter, or when filtering on a member in a chart that is pushed to other charts in the linked group.
• O) Requires HANA 2.0. Supported with Calculated and Restricted Measures. Not supported with Blended models. Calculated dimension cannot be used as aggregation context for measure based filter
• P) Also works when time is enriched
• Q) Requires HANA 2.0
• R) Requires HANA 2.0. For hierarchical dimensions siblings can only be custom sorted within its parent. i.e. you can't move a member to a different parent
• S) Requires SAP Note 270031
• T) Calculated dimensions can not be used for measure based filters
• U) Time based hierarchy must be defined in HANA 1.0, or for HANA 2.0 the hierarchy can be built directly in SAC modeller using a Date dimension
• V) Both dates need to be from the same model
• W) Re-ordering measures is support when the measures are not in a hierarchy. 
  
• Y) Threshold measure to measure comparison is not currently support for BW live or S4 live connections.
• Z) Waterfall charts require BW 7.5 (any DB, or HANA) or BW/4HANA. See SAP Note 2715030
  

Prompts

		Live connection
		HANA	HANA Cloud Platform	BW	S/4	BPC	Universe
Prompts	Date Picker

Prompts are not applicable for Imported data.

Story level formula (aggregation based functions)

	Live connection					Import Data
	HANA	BW	S4	BPC	Universe	Models	Datasets
Sum	(A)
Count, excl null, excl null 0	(A)
Min	(A)
Max	(A)
Average, excl null, excl null 0	(A)
First	(A)
Last	(A)
Median, excl null, excl null 0	(A)
First Quartile, excl null, excl null 0	(A)
Third Quartile, excl null, excl null 0	(A)
Standard Deviation	(A)

• A) Requires HANA 2.0

Story level formula (row based functions)

	Live connection					Import Data
	HANA	BW	S4	BPC	Universe
Length	(A)
SubString	(A)
Like	(A)
ToNumber / INT	(A)
ToText	(A)
%GrandTotal
ABS	(A)
Double	(A)
Float
GrandTotal
If
IsNull	(A)
Log	(A)
Log10	(A)
Not
Power	(A)
ResultLookup	(A)
Trim
Replace	(A)
Concat	(A)
LowerCase	(A)
UpperCase	(A)
Split
FindIndex
EndsWith
Right
Left

• A) Requires HANA 2.0

Commentary Widget

	Live connections					Import Connections
	HANA	BW	S/4	BPC	Universe	Models	Datasets
Commentary

Story Visualisation of GeoMaps

		Reference page(s)	Comments
Show data from a single model		Creating a GeoMap
Show data from multiple models in a single geomap visualisation			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. Plans for future (SAP internal reference FPA34-612)

Predictive

	Live connections					Import Connections
Feature	HANA	BW	S/4	BPC	Universe	Models	Datasets
'Time series' Chart time series forecast (Analytical Models)					(B)
Line Chart Time Series Forecasting (Analytical Models)
R Visualisations	(A)	(A)	(A)		(A)
Search to Insights (H)	(I)
Smart Discovery, including Simulation (E)
Smart Insights (D)	(J)						(K)
Smart Grouping (on Bubble and Scatter Plot Charts)
Smart Predict (the source is the 'Data Set') (C)	(G)					Planning Models only	(F)

• (A) limitations for the remote R server visualisations:
  • 5 millions rows and 3 million data cells.
  • 110 MB remote data size limit.
• (B) requires a 'Date' object, not a 'DateTime' object. There is currently no hierarchy support on the 'Time', for example no month, quarter, yearly view.
• (C) Feature dependent on hosting service. Requires that SAP Analytics Cloud is hosted on a non-SAP data centre. A two-digit number in your SAP Analytics Cloud URL, for example eu10 or us30, indicates a non-SAP data centre.
• (D) Dimensions with > 1,000 members are not considered, Calculated measures not supported as targets.
• (E) Data size limitation of 1 million cells, (calculated as number of measures * number of rows).
• (F) Data sets can be created from the following data sources:
• File and File Server
• SAP HANA
  • On-premise sources. Cloud sources not currently supported
  • Username/password authentication is supported only
  • Connectivity is JDBC
• SAP S/4 HANA
  • Cloud and on-premise editions supported
  • Basic Authentication or no Authentication (i.e. delegated) is supported only.
  • Connectivity is OData
• SQL Databases (On-premise sources)
• Generic OData (Cloud and On-premise sources)
• SAP SuccessFctors
• SAP Business ByDesign
• SAP Cloud for Customer
• SAP Cloud for Customer Analytics
• SAP Integrated Business Planning
• AP Cloud Platform Open Connectors (including but not limited to: Amazon S3, Dropbox, Egnyte. Microsoft Dynamic CRM, Microsoft OneDrive, Netsuite CRM 2018 Release 1)
  Please remember note (C) applies.
• (G) Support for HANA on-premise only. When HANA is hosted in the Cloud it is NOT supported. SAP HANA Cloud is also not supported. Supported on-premise HANA versions are SAP HANA 1.0 SPSP12 rev 122.04 and beyond; SAP HANA 2.0 SPS00, SPS01, and SPS02; SAP HANA 2.0 SPS03 and beyond are supported (always check the official documentation and SAP Note 2444261). Supported: SAP HANA tables (row store or column store), and SAP HANA SQL Views. Not supported: HANA Calc views. Please remember note (C) applies.
• (H) Supported on live models that have an index created on them. Once a live model is indexed, metadata such as dimension and measure names, and dimension members, is stored on SAP servers. Measure values are never stored. Index a model by editing the model preferences. Acquired (imported data) models are supported when there is no data access controls defined upon them. Supported on SAC mobile app for iOS, currently not supported on Android.
• (I) Requires SAP HANA 1.0 SPS12 rev 122.14 or higher
• (J) Official documentation. Official limitations include No support for: SAP BTP (aka SAP Cloud Platform), Tunnel Connection, HANA Cloud, i.e. its only HANA Direct connections that are supported.  Blog: How to setup Smart Insights on Live HANA
• (K) Smart insights on a variance chart is supported for acquired models and not for acquired datasets.

Applications

API

Functionality
postMessage()
onPostMessageReceived
OData Services

Data Analyzer

	Live connections					Import Connections
	HANA	BW	S/4	BPC	Universe	All import connections
Connect to and query

Odata Service (export) API

	Odata export
	HANA (On-premise)	HANA (SAP Cloud Platform)	HANA (SAP HANA Cloud)		BW	S/4	BPC
Odata Service export API

Features in Stories, not yet in Applications

Feature	Available in Applications
GeoMaps	Planned
Blending
Mobile Support	(B)
Export to XLS/CSV
Digital Boardroom Integration	(A)

• A) Story filter is not supported in the app. Story styling overrides created in the Digital Boardroom canvas are not supported on mobile.
• B) Support for iOS. Planned for Android

Life Cycle Management

Import/Export Support

	Object		Import (Upload)	Export (Download)	Content Network	Comments
Security	Team					Performs an 'add' operation/action for the team to role relationship in the target. i.e. when TeamA is a member of Role1 in the target, a TeamA is a member of Role2 in the source, the result of TeamA in the target will be a member of Role1 and Role2. User membership of teams is not transported. Unsupported sample scripts 9xx transports these relationships. The samples also provide many other operations/actions for relationships between source and target. Team transports via the Content Network mean (for non-SAP data centres) the SCIM API can not be used to manage them (see wiki), so team transport is necessary for team folder content (see below 'Team Folder Contents') or use unsupported sample scripts just mentioned.
	Role
	User					Unsupported sample scripts 9xx transports users and teams (the sample don't really transport a user or a team, as users' personal folders and team folders are not transported. User and team properties are simply read and written from source to target)
Public Folder Contents	Acquired Analytics Model
	Acquired Planning Model	Public Versions
		Private Versions
	Live Model
	Dimensions
	Story	Story
		Comments
		Translated Text
		Value Driver Tree
	Digital Boardroom
	Analytical Application
	Custom link (friendly URL)					The custom link to the Story or Digital Boardroom object is stored and remains in the service where it is defined, even if an updated version of the object (identified by the ID) is transported in. i.e. the custom link remains valid even when the underlying object is updated. Custom links can not be transported.
	Metadata of content published to Analytics Catalogue					Currently content published to Analytics Catalogue can not be imported/exported. It may be supported that the file itself (like a Story, Digital Boardroom etc.) can be imported/exported, but the additional Analytics Catalogue metadata associated with the file is not.
	Bookmarks	Global	(see comments)			Default bookmarks are always included. However, 'suggested defaults' are not imported. A 'suggested default' occurs when more than 1 global bookmark is shared, each with their own default. Here a user selects which one is the 'default' and this is 'suggested default'.
		Private	(see comments)			User (who owns the bookmark) must already exist in target system for private bookmarks to be preserved, otherwise they are 'dropped'. The sharing relations are always preserved when imported into a target system, even if the recipient user doesn’t exist yet. Once the user has been created it will automatically be granted access to the bookmark. The user is identified by the userID, so the userID will need be consistent across systems.
	Custom Widgets
	Predictive Scenario
	Data Set
	Point of Interest
	External Content (URL)
	Predictive Scenario
Personal Folder Contents	(all files)
Teams	The team itself					Team membership is not included, i.e. any users in the team are not transported. Unsupported sample scripts 9xx "transports" the user, and user to team relationships (though the users' personal folder isn't transported. The user isn't really transported. See the link mentioned for details)
Team Folder Contents	(all files)
Data Models etc	Dimension
	Wrangler
	Currency
	Allocation Step
	Allocation Process
	Value Driver Tree (legacy)
	Point of Interest
Task	(Calendar) Task					Generally not expected to be an object that should be 'transported'. Contact your SAP representative for feature availability
Process	Process					Generally not expected to be an object that should be 'transported'. Contact your SAP representative for feature availability
Connections	Connection - Live
	Connection - Acquired
	PAi (Predictive Analytics Integrator)
SAP Analytics Hub (A)	Asset Structure
	Asset Structure - Facets
	Branding
	Branding - Header
	Branding - Home Page
	Hub Contents - Assets (Visible, Hidden)
	Hub Contents - Assets (Drafts)
	Hub Contents - Uploaded pictures
	Hub Contents - User Data
	Hub Contents - User Data - Favourites
	Hub Contents - Picked for you
	Hub Contents - Usage Data