Official partner
SAP S/4HANA data into Azure and Power BI
ERP data from SAP S/4HANA
Yres retrieves SAP S/4HANA data along two routes, depending on how your SAP landscape exposes data: through OData services of the SAP Gateway (the usual route) or via files from SAP Business Data Cloud. There is no direct connection to the underlying HANA database. In both cases the data lands in an Azure SQL database in your own Azure tenant, is historized and is usable in Power BI alongside your other sources. No separate SAP middleware is required.
At a glance
- Route A: OData (recommended)
- OData service from the SAP Gateway, with Basic sign-in or OAuth2. Paging through the OData nextLink
- Route B: SAP Business Data Cloud
- Files in Azure storage, connected with a SAS token
- Network
- If SAP is on-premises or behind a firewall, the connection runs through a self-hosted integration runtime in your own network. If the service is reachable over the internet, none is needed
- Incremental loading
- Yes, where the service or table offers a change column. Full loads are always possible
- History
- Every change is kept (SCD2), even where SAP only returns the current state
- Where credentials live
- The SAP user and password are kept only in the Key Vault of your own Azure environment
What you arrange yourself
- 1Agree with your SAP/Basis administrator which route fits: OData services or Business Data Cloud.
- 2For OData: have the required services activated in the SAP Gateway (transaction /IWFND/MAINT_SERVICE) and request a communication user with read access.
- 3Determine whether SAP is reachable from the internet. If not, install a self-hosted integration runtime in the network where SAP lives.
- 4Add the source in Yres with type OData or SAP BDC, and select the services or files you want to load.
When you need this — and when you don't
A standalone connector is enough if…
If you report exclusively inside SAP and the embedded analytics or SAP Analytics Cloud are sufficient, you do not need a separate data warehouse.
Yres adds value if…
Yres earns its place once SAP figures must sit next to other sources in Power BI, reporting has to keep running during a migration from SAP ECC to S/4HANA, or you want to build history that SAP does not retain.
Frequently asked questions: SAP S/4HANA
Does Yres have its own SAP S/4HANA connector?
No, deliberately. S/4HANA exposes data through standards such as OData services and Business Data Cloud. Yres uses those standard routes, so you do not depend on a vendor-specific component inside your SAP landscape.
Does this work when SAP is on-premises?
Yes. You install an Azure Data Factory self-hosted integration runtime in your own network. It makes an outbound connection to Azure, so you do not have to open inbound ports to SAP.
Will my reporting keep working during a migration to S/4HANA?
That is a common reason to use Yres. The data warehouse keeps the history from the old system and loads the new one alongside it; reports read from the data warehouse and do not notice the switch.
Which URL and port does Yres need from SAP?
For OData, the service root in the form https://<host>:<port>/sap/opu/odata/<namespace>/<service name>. Host and port are those of the SAP Gateway, usually 443 or 5<instance>43. Your Basis administrator can test the service beforehand with transaction /IWFND/GW_CLIENT.
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.