Official partner
SAP Datasphere data into your Azure data warehouse and Power BI
Business data from SAP Datasphere
Yres connects SAP Datasphere as a storage source. A Datasphere administrator exposes a view or analytic model for consumption and writes the data to an Azure Data Lake or Blob container. You connect that container in Yres with a SAS URI, a container name and a SAS token, using the same form as SAP Business Data Cloud. Yres reads the files on the Azure Data Factory cloud runtime and loads them into an Azure SQL database in your own tenant, ready for Power BI. Alternatively, connect the Datasphere OData API.
At a glance
- Connection
- Azure Data Lake/Blob endpoint (dfs.core.windows.net) holding the Datasphere export, connected with a SAS token
- Fields
- SAS URI (host name only, with a trailing slash), container and SAS token
- Place in the wizard
- No separate Datasphere option: you connect through the SAP Business Data Cloud form. They are nevertheless two different SAP products
- Integration runtime
- Cloud. The storage endpoint is reachable over HTTPS, so no self-hosted integration runtime is needed
- Tables
- Yres reads the structure from the exported files; you add one table per file or file pattern and choose a load type
- Alternative
- The Datasphere consumption/OData API, connected as an OData source with OAuth
- Secrets
- SAS URI, token and container are stored as secrets in the Azure Key Vault of your own environment
What you arrange yourself
- 1Have a Datasphere administrator mark the required view or analytic model as Expose for Consumption.
- 2Write the exposed data to an Azure Data Lake or Blob container.
- 3Generate a SAS token on that storage account with at least read and list permissions and an expiry date (Azure Portal → storage account → Security + networking → Shared access signature). Save the token straight away: it is shown only once.
- 4Add a source in Yres through the SAP Business Data Cloud form and enter the SAS URI, container and SAS token. Also enter the credentials expiry date, so Yres warns you in time.
- 5Add one table per file or file pattern and choose the load type.
When you need this — and when you don't
A standalone connector is enough if…
If Datasphere already is your central data layer and you report directly on it, a second data warehouse in Azure adds little.
Yres adds value if…
Yres earns its place when Power BI and Azure are your reporting platform and Datasphere is one of the sources: the Datasphere export then ends up in the same database as your non-SAP sources, with the same scheduling, monitoring and history.
Frequently asked questions: SAP Datasphere
Why is SAP Datasphere not listed when I add a source?
Datasphere is not a separate option in the wizard. Its connection has the same shape as that of SAP Business Data Cloud (Azure storage with a SAS token), so you use that form. They remain two different SAP products.
Which Datasphere objects can I bring into Azure?
Views and analytic models that a Datasphere administrator has marked as Expose for Consumption. That data is written to an Azure Data Lake or Blob container, where Yres picks it up.
Can it be done without a file export, directly through an API?
Yes. Datasphere can also offer data through a consumption/OData API. You connect it in Yres as an OData source with OAuth. For that, the administrator creates an OAuth 2.0 client under System → Administration → App Integration, which provides the client ID, client secret and token URL.
Does Yres read the data model from Datasphere itself?
Not on the export route. Datasphere is then a file source: Yres derives the columns from the exported files in the container, not from a database catalog. You create one table per file or file pattern.
Full technical description in the knowledge base →·Last reviewed:
Data warehouse automation that runs in your own Azure
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.