Data Integration with SAP BW/4HANA 2.0
Dear friends of SAP BW/4HANA,
I’m working for SAP since more than 12 years and as a member of the BW product management team I received a lot of questions from customers regarding new functionalities for integrating data into SAP BW/4HANA.
SAP BW/4HANA provides a multitude of innovations in various areas. One of the focus areas are extended and simplified ways to integrate non-ABAP – typically non-SAP – data structures as well as ABAP – SAP Systems – data structures into SAP BW.
Loading and persisting data from on-premise sources as well as Cloud Applications is and will be one of the key functionalities of an Enterprise Datawarehouse (EDW).
Loading and persisting data from Cloud Applications (e.g. SuccessFactors) in an SAP BW/4HANA data warehouse is possible in many ways.
To enable such scenarios, SAP BW/4HANA 2.0 provides new capabilities in the DataStore Objects to push data in the inbound table of the DataStore Object. With this new Setting in the DataStore Object in SAP BW/4HANA 2.0 it is possible to use tools such as Data Services or via SAP Cloud Platform Integration (CPI) to PUSH data into a DataStoreObject directly.
This property can be used for all types of standard DataStore object and staging DataStore object, but not together with Inventory enabled or Planning enabled DataStore Objects.
It is possible to use RFC or http data to load data into the DataStore object. There are two possible procedures:
- Sending data without a request: For every call, a new internal request is opened
- Sending data with a request: The following sequence is used to do this: Open Request, n times Send Data (with request and package), Close Request
SAP Cloud Platform Integration and SAP Process Integration equal or higher 7.5 SP15 (see SAP Note 2757524) can use this http (REST) interface for data integration to SAP BW/4HANA 2.0.
This blog post describes the options SAP provides with SAP BW/4HANA 2.0 to push data into a write interface enabled DataStore Object.
The following options are described in detail in independent blogs posts: