A frequent use case in hybrid data warehousing scenarios is to enrich existing data models in SAP BW/4HANA with analytical data models from SAP Datasphere.
Data from SAP Datasphere is to be transferred to SAP BW/4HANA to enrich the existing data flow in the on-premise system with public cloud data.
The following blog describes how data stored in the SAP HANA Cloud database of SAP Datasphere can be consumed in an on-premise SAP BW or SAP BW/4HANA system.
In the first step, the space from which data is to be read must be opened in Space Management. There, a database user with Read Access authorization must be created.
In the second step, it is necessary to enable the property Expose for Consumption for the view that is to be used in SAP BW/4HANA.
After the view has been activated for consumption, the Database Explorer can be used to check whether the view is accessible in SAP HANA Cloud in the corresponding schema and is supplying data. To do so, go back to Space Management and call the Database Explorer.
In the next step, a remote source of type hanaodbc must be created in the SAP HANA database of SAP BW/4HANA. The credentials of the database user created in SAP Datasphere are used for this remote connection.
The SQL code below can be used to create the remote source. The technical name, the SAP HANA Cloud Endpoint, and the credentials must be adjusted accordingly.
After the remote source has been successfully created, the objects exposed in SAP HANA Cloud of SAP Datasphere can be consumed in the on-premise SAP HANA database of SAP BW/4HANA.
In the next step, it is necessary to create a SAP HANA_SDA source system for the remote source to SAP HANA Cloud. For this source system, a DataSource must be created to consume the view exposed for consumption in Datasphere. This DataSource can be used to extract data into a DataStore object. Like this, data stored in SAP Datasphere can be reused in SAP BW/4HANA.
As can be seen in the previous sections, existing analytical data models from SAP Datasphere can also be easily integrated into other SAP analytics products.As of today, we have not planned a standardized connection for SAP Datasphere as a source for SAP BW/4HANA. In SAP BW bridge, on the other hand, we are currently working on a solution for using SAP Datasphere as a source.
https://roadmaps.sap.com/board?range=FIRST-LAST&PRODUCT=73555000100800002141#Q4%202022;INNO=000D3AAA...
Please let me know, if you have any detailed question!
Regards,
Dominik
Data from SAP Datasphere is to be transferred to SAP BW/4HANA to enrich the existing data flow in the on-premise system with public cloud data.
The following blog describes how data stored in the SAP HANA Cloud database of SAP Datasphere can be consumed in an on-premise SAP BW or SAP BW/4HANA system.
Overview about the Scenario
Useful Links:
- Create SAP HANA Remote Source https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/275839492fef49318d92d0e...
- Import certificates SSL https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/86e96624e9a74e77994f754...
- Create Database User
- https://help.sap.com/docs/SAP_DATA_WAREHOUSE_CLOUD/be5967d099974c69b77f4549425ca4c0/798e3fd6707940c3...
- Integrating Data and Managing Spaces
- https://help.sap.com/docs/SAP_DATA_WAREHOUSE_CLOUD/be5967d099974c69b77f4549425ca4c0/8f98d3c917f94452...
- SAP DataWarehouse Cloud - First Guidance
- https://assets.cdn.sap.com/sapcom/docs/2021/09/8a0fc7ca-f67d-0010-bca6-c68f7e60039b.pdf
Prereqisite:
- Certificate for SSL Connection to Remote sources is created and imported in SAP HANA Database under SAP BW/4HANA
- IP Allowlist in SAP Datasphere Core is adjusted with relevant External IP from SAP BW/4HANA
Step-by-step:
In the first step, the space from which data is to be read must be opened in Space Management. There, a database user with Read Access authorization must be created.
Create Database User
In the second step, it is necessary to enable the property Expose for Consumption for the view that is to be used in SAP BW/4HANA.
Expose relevant View for Consumption
After the view has been activated for consumption, the Database Explorer can be used to check whether the view is accessible in SAP HANA Cloud in the corresponding schema and is supplying data. To do so, go back to Space Management and call the Database Explorer.
Database Explorer
In the next step, a remote source of type hanaodbc must be created in the SAP HANA database of SAP BW/4HANA. The credentials of the database user created in SAP Datasphere are used for this remote connection.
Remote source creation
The SQL code below can be used to create the remote source. The technical name, the SAP HANA Cloud Endpoint, and the credentials must be adjusted accordingly.
CREATE REMOTE SOURCE <HANA1> ADAPTER "hanaodbc"
CONFIGURATION 'Driver=libodbcHDB.so;ServerNode=<HANA_Cloud_endpoint>;
encrypt=TRUE;'
WITH CREDENTIAL TYPE 'PASSWORD' USING 'user=<user_name>;password=<password>';After the remote source has been successfully created, the objects exposed in SAP HANA Cloud of SAP Datasphere can be consumed in the on-premise SAP HANA database of SAP BW/4HANA.
Remote Source
In the next step, it is necessary to create a SAP HANA_SDA source system for the remote source to SAP HANA Cloud. For this source system, a DataSource must be created to consume the view exposed for consumption in Datasphere. This DataSource can be used to extract data into a DataStore object. Like this, data stored in SAP Datasphere can be reused in SAP BW/4HANA.
HANA_SDA Source System
Conclusion:
As can be seen in the previous sections, existing analytical data models from SAP Datasphere can also be easily integrated into other SAP analytics products.As of today, we have not planned a standardized connection for SAP Datasphere as a source for SAP BW/4HANA. In SAP BW bridge, on the other hand, we are currently working on a solution for using SAP Datasphere as a source.
https://roadmaps.sap.com/board?range=FIRST-LAST&PRODUCT=73555000100800002141#Q4%202022;INNO=000D3AAA...
Please let me know, if you have any detailed question!
Regards,
Dominik
- SAP Managed Tags:
6 Comments
