Using the Datasphere OData API with SAP Analytics Cloud
An OData API is available to allow SAP Analytics Cloud (SAC) and third party tools to acquire Datasphere data, (formerly known as Data Warehouse Cloud (DWC)). Acquisition of data within SAC is often required for SAC Planning scenarios.
2022.11 Initial release of the Datasphere OData API. Access was restricted to consumption from SAC.
2022.20 General Availability of the OData API for all clients to consume
2023.02 ODATA APIs have been renamed to SAP Datasphere Consumption APIs.
For bi-directional integration betweem Datasphere and SAC, refer to another blog post I shared – Using the SAC Data Export API with Datasphere and Data Intelligence.
This blog post covers the steps required to import Datasphere data into SAC.
- Identify the OData Source (Data Service URL) in Datasphere
- Lookup your redirect URI in SAC
- Create the OAuth Client in Datasphere
- Create OData Connection in SAC
- Import from OData Connection
** Note currently I recommend using the Alternative URL as it was more reliable for me than the Public API URL **
1. Identify the OData Source in Datasphere (Data Service URL)
We could use the documentation to construct our OData URL, alternatively we can copy and paste that from our space assets.
First we can browse the available spaces using a URL such as
# Public API URL https://datasphere-tenant.eu10.hcs.cloud.sap/api/v1/dwc/catalog/spaces # Alternative URL https://datasphere-tenant.eu10.hcs.cloud.sap/dwaas-core/odata/v4/catalog/spaces
By specifying the space, we can see the assets in there.
# Public API URL https://datasphere-tenant.eu10.hcs.cloud.sap/api/v1/dwc/catalog/spaces('I049374')/assets # Alternative URL https://datasphere-tenant.eu10.hcs.cloud.sap/dwaas-core/odata/v4/catalog/spaces('I049374')/assets
Identify the dataset you require and then copy assetRelationalDataUrl, this is your Data Service URL in the SAC OData Connection.
Note My JSON response is being formatted by a browser extension, yours may be JSON returned in plain text.
If we click on the assetRelationalDataUrl, we receive the metadata from the OData Service.
We can see the data from the OData service by appended the dataset name a second time.
2. Lookup your redirect URI in SAC
The redirect URI comes from the SAC connection properties, as SAC establishes this connection to Datasphere
Create a new OData Connection in SAC and we can identify the URI
Note, my SAC tenant is in eu10 but strangely the Redirect URI is in us1.
3. Create the OAuth Client in Datasphere
A new OAuth Client needs to created in Datasphere
Navigate to System -> Administration -> App Integration
Add a New OAuth Client, paste the Redirect URI from step 1, ensuring there are no leading spaces.
Once created copy the OAuth Client ID and Secret
We also need to the copy the following from the OAuth Client URLs
4. Create OData Connection in SAC
We can now create the SAC OData Connection.
The SAC connection points to a single dataset/view from Datasphere,
You now have the 5 connection parameters and can copy and paste these values.
Data Service URL = assetRelationalDataUrl
OAuth Client ID
All being well we can save the connection.
5. Import from OData Connection
We can now create either a model or dataset from our OData connection.
In this blog post you can see that we can now import Datasphere data into SAC. This (in conjunction with the SAC OData/CDI API) provides support for bi-directional integration that helps with SAC Planning scenarios.
For further reading checkout Max’s Blog on the bi-directional SAC Planning and Datasphere scenarios.