SAP Analytics Cloud content based on live vs. data import models
Live vs data import models
In this blog post you will learn about one common source for errors: Using live vs data import models. You will learn what are the differences between the two and how you can set up your content correctly.
[Please note that this post is not updated anymore and information might be outdated. If you want to learn about the latest SAP business content, please check the community page here and the latest content blog posts here]
[Last updated: 25th of May 2018, SAP Analytics Cloud Version 2018.7.0]
In SAP Analytics Cloud there are two types of connections based on which models can be created: import data connections and live data connections (find an overview here). Once there is a connection established, data can be imported to a new or existing model. For data sources that have a live connection, a model can be created based on the live connection and the data will be read on the fly.
The SAP Analytics Cloud content uses both types of models. In order to find out which package uses which types of models, check the Extended Content Directory which is attached to the Roll-out Slide Deck.
Also, the content documentation has a sub-chapter called “Data Source Connection and Integration” for every model with a table where the recommended connection type and connection source are mentioned. Furthermore, the technical name of the model includes “IM” when there is an import data connections vs “LH” for Live Hana connection and other abbreviations for other data connections.
Another way to find out ad-hoc is that every data model which has imported demo data, has an Include Data checkbox in the content library. For example in SAP Banking we have a mix of Data Import and Live Data Models.
When importing data import models from the content library, you have the advantage that the content comes with demo data and you can immediately after importing the content get an impression of the stories and the features included.
Two of our content packages come with predefined connections: SAP Business ByDesign and SAP Travel & Expense – Concur.
When importing those connections, you will notice that you still need to set them up. Check out the content documentation for more details. For Travel and Expense you will find the instructions in the chapter TE: Architecture and Abstract which will guide you through the following steps:
“Go to Menu -> Connection, select the connection “Concur Tenant (Data acquisition via Concur API connector)” and edit the connection parameters Key and Secret as provided by your Concur web service administrator (See help center topic “Import Data Connection to Concur”).”
“To import data into the models, go to Menu -> Browse -> Models, select the respective model, click on View More in the column Data Sources and click Import Data to start the import via the “Concur Tenant” connection. You can edit the import options and the schedule settings by clicking on the target name. It is recommended to use the import method Clean and Replace.”
For the SAP Business ByDesign package, you can follow similar steps.
Updating content or downloading additional packages might overwrite customer enhancements or changes to content objects or even loose customer data. Please read the chapter 3.2 of the content documentation carefully to avoid accidental loss of customer enhancements and data.
Live data models require one additional step before importing the content: you have to have a connection with the same name in place in order to see data in the stories and dashboards after importing the content.
If you do not have that connection, you will still be able to import the content but you will receive an error message, when opening the model or story:
For example, when opening the model SAP__FS_LH_CLIENTEXPOSURES, you receive the following error message:
When opening the story SAP__FS_GEN_LIQUIDITYMANAGEMENT, you will notice that a chart says “Data cannot be retrieved from the data source”.
You will find the instructions on how to establish the connection in the content documentation.
For example, for Banking it is described in the chapter FS Banking: Stories > SAP Banking: Liquidity Management (SAP__FS_GEN_LIQUIDITYMANAGEMENT):
“This story is based on a live data connection of type “SAP HANA”. The story will therefore not show any data unless a suitable connection “SAPLM” has been created. The connection may be set up prior or after the import of the content package SAP FS Banking. If the connection does not exist when the content package is imported, the live models will be imported with warnings. They will be active, but unusable until the connection has been created. The connection has to have the name “SAPLM”. Enter a suitable description. Specify the connection details for the SAP Liquidity Management backend system and provide the required credentials. Depending on your specific data, the layout in the story SAP Banking: Liquidity Management may have to be adjusted (filter values, number scaling, etc.) “
Leave us a comment below in case you have any questions or suggestions how content could be improved.
You want to stay up-to-date? Paste this into your RSS feed-reader and subscribe.