Official partner
Connect SAP HANA to Power BI and your Azure data warehouse
SAP HANA data through XS OData
Yres does not read SAP HANA directly on its SQL port: a direct database or ODBC connection does not exist in Yres. HANA data comes in through an XS OData service, an address ending in .xsodata that your HANA administrator publishes, or through an export route such as SAP Business Data Cloud. Yres connects the service as an OData source, using a HANA/XS user or OAuth, and loads the data into an Azure SQL database in your own Azure tenant. There it is historized and available to Power BI.
At a glance
- Connection
- XS OData service with an address of the form https://<host>:<port>/<path>.xsodata, connected as an OData source
- Direct database connection
- Not available. Yres has no HANA or ODBC source type; the HANA server's host name and SQL port are not used
- Sign-in
- Basic with a HANA/XS user and password, anonymous if the service is open, or OAuth if the service is set up for it
- Integration runtime
- The cloud runtime if the service is reachable over the internet; a self-hosted integration runtime if it sits behind a firewall
- Paging
- Through the next link in the OData response
- Alternative route
- Export via SAP Business Data Cloud: files in Azure storage, connected with a SAS token
- Storage of sign-in details
- As secrets in the Azure Key Vault of your environment; Yres does not keep them itself
What you arrange yourself
- 1Agree with your SAP/HANA administrator how your HANA landscape exposes data: through an XS OData service or through an export to SAP Business Data Cloud.
- 2Have the administrator confirm the correct service address (ending in .xsodata).
- 3Request a HANA/XS user with a password that has read authorization on the objects behind the service.
- 4Check whether the service is reachable from the internet. If it sits behind a firewall, install a self-hosted integration runtime in that network.
- 5Add an OData source in Yres with the service address and the user, and choose what you want to load.
When you need this — and when you don't
A standalone connector is enough if…
If you have one report reading one published HANA service and no need to look back in time, a direct connection from your reporting tool is the shortest path.
Yres adds value if…
Yres earns its place once HANA data has to sit next to other sources in Power BI, you want to keep changes that HANA itself overwrites, or several services need to be loaded and monitored on a fixed schedule.
Frequently asked questions: SAP HANA
Can Yres log in to SAP HANA directly through ODBC or the SQL port?
No. Yres has no HANA or ODBC source type, neither in the source picker nor in the load engine. You retrieve HANA data through an XS OData service or through an export route such as SAP Business Data Cloud.
What do I need from my HANA administrator?
The address of the XS OData service (ending in .xsodata) and a HANA/XS user with a password that has read access to the objects concerned. You do not need the host name and SQL port of the database server itself.
Do I need a self-hosted integration runtime for SAP HANA?
Only if the XS OData service sits behind a firewall and cannot be reached from Azure. If the service is reachable over the internet, you choose the standard cloud runtime of Azure Data Factory.
When do I choose the export route instead of XS OData?
When your HANA landscape does not publish data as an OData service but offers it as files through SAP Business Data Cloud. That route works with a SAS token on Azure storage and runs on the cloud runtime. Which route fits is something to agree with your SAP/HANA administrator.
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.