Generic OData Service - Datasphere Integration

[narasingha]

Hello all,

Welcome back again to my series of blog posts on various objects in the SAP datasphere. In this blog post, we will see how Generic OData Service - Datasphere Integration works.

It is easy in SAP Datasphere to connect to a generic OData service. There may be a question of why we need to integrate OData service with SAP Datasphere, but it depends on the business case. 

In earlier days, to send SAP data to the outside world, we used to create files stored in the AL directory, or we used to create open hub destinations, which further needed to be connected to third-party ETL tools like SAP BODS, etc., to load to a third-party system.

Then came the OData service concept, and we can generate OData on CDS views, ADSOs, and even on Bex queries (conditions apply) and can send the SAP data to the outside world.

Now let us get set to go!

To start with, I will go with the generic OData service, which is readily available publicly on the internet.

Odata service URL : https://services.odata.org/V4/NORTHWIND/NORTHWIND.SVC/ 

The OData service is working as expected. Now test this odate service in Postman and see if it works. It sh

So this OData service is working and tested perfectly. it supports only GET methods. Cool!

Now let us go to our SAP datasphere tenant and try to establish a connection. SAP DataSphere provides excellent connectivity to the majority of stakeholders to bring the data into SAP DataSphere with a data federation mechanism. As of now there are 43 different connections I have seen, including Azure, AWS, Google BigQuery in GCP, and even Alibaba Cloud.

Now see!

Now go to SAP data sphere then Connectionsand choose "Generic Odata" connection. Please find the below picture.

Give the relevant details and click on save. As this OData service does not require any authentication, it is publicly available, and we do not need to give any authentication details such as a user name, host, or password, etc.

 Once we save, the connection is successfully established with the Odata service.

Validate and see the result.

Real-time replication status is not applicable as we are consuming the API in real time only.

The point to be noted here is for a generic Odata service Data flows, remote tables are supported, but replication flows are not supported.

So now we're all set, and we consumed the API in SAP Datasphere.

Now let us go how it looks like. Let us go to dataflow area in data builder and try to create a data flow on the entities in the API.

Now, as we see the oDATA service API is available in SAP datasphere and we can create a dataflow or graphical view or SQL view on top of the tables.

This is how we can perform Generic OData Service - Datasphere Integration

Thank you,

Narasingha