Official partner
Read SAP Analytics Cloud (SAC) into Azure and Power BI
Planning & analytics data from SAC
Yres retrieves data from SAP Analytics Cloud through the data export API of your SAC tenant. You create an OAuth client in SAC with the Client Credentials grant; the pipeline uses it to request a token and then reads the export API. Because SAC is reachable over the internet, this runs on the cloud runtime of Azure Data Factory. The data lands in an Azure SQL database in your own Azure tenant, where it sits next to your other sources and is usable in Power BI.
At a glance
- Connection
- The data export API of your SAC tenant, with an address such as https://tenant-name.eu10.hcs.cloud.sap/api/v1/dataexport/
- Sign-in
- OAuth2 with the Client Credentials grant: a client ID and client secret from SAC, plus the token URL
- Fields in Yres
- Url, Authentication url, Client Id and Client Secret
- Integration runtime
- Cloud. SAC is reachable over the internet; no self-hosted integration runtime is needed
- Incremental loading
- Yes, with one or two delta columns. Full loads are possible too
- Where the client secret lives
- In the Azure Key Vault of your own environment. The pipeline fetches the token; Yres does not keep the values itself
What you arrange yourself
- 1In SAP Analytics Cloud, go to System → Administration → App Integration and choose Add a New OAuth Client.
- 2Under Authorization Grant choose Client Credentials and save the client.
- 3Copy the OAuth Client ID and the Secret that SAC then shows.
- 4Note the Token URL on the same page; you enter it in Yres as the Authentication url. Also note the address of your tenant's data export API, with your tenant name and region.
- 5Add the SAC source in Yres with these four values.
When you need this — and when you don't
A standalone connector is enough if…
If all your analysis and planning rounds take place inside SAC itself, there is no need to take the data out.
Yres adds value if…
Yres earns its place when figures from SAC have to appear in Power BI next to data from other systems, or when you want to record what those figures looked like at earlier points in time. You no longer need manual exports for that.
Frequently asked questions: SAP Analytics Cloud
Which type of OAuth client do I create in SAC?
A client with the Authorization Grant Client Credentials. That is a system-to-system sign-in: Yres uses the client ID and client secret to fetch a token from the token URL itself, without anyone having to log in.
Where do I find the two addresses Yres asks for?
The Token URL is shown in SAC on the System → Administration → App Integration page; you enter it as the Authentication url. The other address is your tenant's data export API: your tenant name and region followed by /api/v1/dataexport/.
Do I have to install anything in my own network for SAC?
No. SAC is a cloud service reachable over the internet, so the standard cloud runtime of Azure Data Factory is sufficient. A self-hosted integration runtime is not needed.
A SAC load fails at sign-in. Where do I look first?
Check whether the OAuth client still exists in SAC and whether the client ID, client secret and token URL are still correct. The pipeline fetches the token with these details; if the secret was replaced in SAC, it has to be updated in Yres 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.