SAP S/4 HANA (on-premise and Cloud) Integration with SAP Data Warehouse Cloud
When it comes to connecting SAP Data Warehouse Cloud to your on-premises systems, you have a variety of options.
In this blog, we’ll look specifically at SAP S/4 HANA on-premise and Cloud solutions and how we can integrate them into your SAP Data Warehouse Cloud.
Connections via OData and SAP ABAP
Currently, SAP S/4 HANA on-premise users have the option of connecting to SAP Data Warehouse Cloud via a generic OData and an SAP ABAP adapter. While connecting via OData works without a Data Provisioning Agent, the SAP ABAP adapter requires the set-up of a Data Provisioning Agent.
When using an OData connection with SAP S/4 HANA on-premise, users need to expose their OData endpoints in the public. Of course, the authorization concept ensures that no one has access to those endpoints that is not privileged.
Connection via SAP Cloud Connector
As an alternative, SAP S/4 HANA on-premise users can use the SAP Cloud Connector in the SAP Cloud OData Provisioning Service available in Neo to establish a connection to their on-premise systems. IConnecting to Customers who choose to go through the SAP Cloud Connector tneed to install the SAP Cloud Connector and configure the connection betweenSAP Cloud Platform and the on-premise installation. After the connection works, they can leverage the OData Provisioning service (in the SAP Cloud Platform Neo environment) and generate the ODATA endpoints.
By doing so, the exposed endpoints are only visible to applications running inside the SAP Cloud Platform.
Soon, it will also be possible to use Cloud Data Integration (CDI) to establish a connection between SAP S/4 HANA on-premise and SAP S/4 HANA Cloud and SAP Data Warehouse Cloud, in addition to the OData adapter. With the CDI connection, it will be possible to connect to CDS views that are extraction-enabled. These extraction-enabled views are basic views (also often called Interface Views, IVs), that is unaggregated data, that can be federated and replicated.
If users – for example because they are interested in getting immediate access to already aggregated, structured data and views – wish to get to Consumption Views/Analytic Queries, they can choose the connectivity via the OData adapter, not the CDI connection. This, in turns, requires public exposure of the endpoints for every Consumption View individually.
It is important to note that a connection via CDI can only reach the lower level, meaning the Basic Views of any database, not the Consumption Views. For those customers who are exclusively interested in the Consumption Views/Analytic Queries and aggregated data, a connection via OData is – for now – inevitable.