Get SAP ERP (ECC) data into Azure and Power BI
Classic SAP ERP / ECC data
Yres has no separate connector for SAP ERP (ECC) and does not read SAP tables directly. You connect an SAP system through the generic routes Yres also uses for S/4HANA. The usual route is an OData service that your Basis administrator activates in the SAP Gateway; Yres reads it with a communication user or OAuth2. If SAP runs on-premises, the connection goes through a self-hosted integration runtime. The data lands in an Azure SQL database in your own Azure tenant, where Power BI connects to it.
At a glance
- Connector
- No dedicated SAP ERP source type. In Yres you choose the OData source type, or OData OAuth if the SAP Gateway uses OAuth
- Service address
- https://<host>:<port>/sap/opu/odata/<namespace>/<service_name>/ — host and port of the SAP Gateway, often HTTPS port 443 or 5<instance>43
- Sign-in
- Basic with an SAP (communication) user that has read authorization, or OAuth2 with Client Credentials or Authorization Code (then with a refresh token)
- Network
- On-premises or behind a firewall: a self-hosted integration runtime that can reach the SAP Gateway. Publicly reachable: the cloud runtime
- Load types
- FULL, DELTA, OVERWRITE, RELOAD, IMAGE and ADDITIONAL. Only OVERWRITE removes existing history
- File route
- If SAP data is offered as files through SAP Business Data Cloud, you connect it with a SAS token
- User and password
- Are written to the Azure Key Vault in your own tenant; the connection in Data Factory refers to them
What you arrange yourself
- 1Check with your Basis administrator whether your SAP system offers OData services through an SAP Gateway. That is the precondition for this route.
- 2Have the required services activated with transaction /IWFND/MAINT_SERVICE: add them via Add Service, choose the system alias of the back end and activate. The status must be Active.
- 3Request an SAP (communication) user with read authorization on the underlying data, or have an OAuth client set up in the Gateway.
- 4Install and publish a self-hosted integration runtime in the network where SAP lives, if the Gateway cannot be reached from the internet.
- 5Add one OData source per service in Yres, with the service address and the sign-in details.
When you need this — and when you don't
A standalone connector is enough if…
If your ECC system stays as it is for now and all reporting comes from SAP itself, there is no reason to bring the data into Azure.
Yres adds value if…
Yres earns its place when a move to S/4HANA is coming: what was loaded from the old system stays in the data warehouse with its history, and you connect the new system next to it along the same OData route. Without a migration the same holds as soon as SAP figures have to sit next to other sources in Power BI.
Frequently asked questions: SAP ERP
Does Yres read SAP tables directly, through RFC or a table connector?
No. Yres has no SAP table connector and no direct database connection to SAP HANA. You expose SAP through OData services from the SAP Gateway, or through files from SAP Business Data Cloud. What you can load is therefore determined by the services your administrator activates.
How do I test an OData service before connecting it in Yres?
Your SAP administrator can call the service with transaction /IWFND/GW_CLIENT in the SAP Gateway. If the service works there and its status in /IWFND/MAINT_SERVICE is Active, you use the same address in Yres.
What happens to the loaded ECC data when we move to S/4HANA?
It stays in the data warehouse. Yres keeps history (SCD2): the FULL and RELOAD load types preserve it, only OVERWRITE discards existing history. You add S/4HANA as a new source through OData, so old and new are available to your reports in the same database.
Basic or OAuth: which sign-in do I choose?
That depends on how your SAP Gateway is set up. Basic works with an SAP (communication) user and password. OAuth requires an OAuth client in the Gateway, with a client ID, client secret and token address; if you choose Authorization Code, a refresh token is mandatory as well.
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.