Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.

30

Applies to:
SAP BW 7.30. For more information, visit the EDW homepage

Summary
This document provides the details for creating a Hybrid Provider based DSO using real time data acquisition for SAP BW 7.30.

Author:

Lavanya Dev Sharma

th

Company: Infosys Technologies Ltd. Created on: 24 June 2011

Author Bio
Lavanya Dev Sharma is working with Infosys Technologies Limited. He has got rich experience in implementation of various projects in both SAP BW 3.5 and SAP BW 7.0.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Table of Contents
Introduction ......................................................................................................................................................... 3 Types of Hybrid Providers ............................................................................................................................... 3 HybridProviders based on Direct Access ........................................................................................................... 3 HybridProviders based on a DataStore object ................................................................................................... 3 Real-time Data Acquisition ................................................................................................................................. 3 Daemons............................................................................................................................................................. 3 Live Scenario ...................................................................................................................................................... 4 Step 1: ............................................................................................................................................................. 5 Step 2: ............................................................................................................................................................. 6 Step 3: ............................................................................................................................................................. 7 Step 4: ............................................................................................................................................................. 7 Step 5: ............................................................................................................................................................. 8 Step 6: ............................................................................................................................................................. 9 Step 7: ........................................................................................................................................................... 10 Step 8: ........................................................................................................................................................... 11 Step 9: ........................................................................................................................................................... 11 Step 10: ......................................................................................................................................................... 12 Step 11: ......................................................................................................................................................... 13 Step 12: ......................................................................................................................................................... 14 Step 13: ......................................................................................................................................................... 16 Step 14: ......................................................................................................................................................... 17 Result: ........................................................................................................................................................... 17 Related Content ................................................................................................................................................ 18 Disclaimer and Liability Notice .......................................................................................................................... 19

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Introduction
Hybrid provider consists of a DataStore object/Virtual Provider and an InfoCube. It has data flow in between them automatically generated while creating the hybrid provider. It combines the historic data with latest delta information when a query based on it is executed. The hybrid structure of this InfoProvider ensures excellent performance with near real time reporting on high volumes of data, as it provides faster access to data. This becomes even more efficient when BWA is used. Types of Hybrid Providers There are two types of Hybrid Providers: 1. HybridProviders based on direct access. 2. HybridProviders based on a DataStore object.

HybridProviders based on Direct Access

HybridProvider based on direct access is a combination of a VirtualProvider and an InfoCube. The benefit of this InfoProvider is that it provides access to real time data without actually doing any real time data acquisition. At query runtime, the historic data is read from the InfoCube. Also the near real-time or the latest up-to-date data from the source system is read using the Virtual Provider.

HybridProviders based on a DataStore object

The HybridProvider based on a DSO is a combination of DSO and InfoCube. Once this Hybrid Provider is created and activated, the different objects including (DTP, Transformation and process chain) that are used for the data flow from the DSO to the InfoCube are created automatically. One should use HybridProvider based on DSO as InfoProvider in scenarios where there is need to load data using real time data acquisition. The DTP for real-time data acquisition from a real-time enabled Datasource to the DSO loads the data to the DSO in delta mode. The daemon used for real-time data acquisition immediately activates the data. As this daemon is stopped, the data is loaded from the change log of the DSO to the InfoCube. The InfoCube acts as storage for the historic data from DSO. Following is a brief description about the real-time data acquisition and how it is done in BW. Also there is a brief description about the daemons that are used to perform the real-time data acquisition.

Real-time Data Acquisition

Real-time data acquisition enables to update data in real time. As the data is created in the source system, it is immediately updated in the PSA or the delta queue. There are special InfoPackages and DTPs that are real time enabled which are used to load data in InfoProviders. Also, to load real time data from source system to SAP BW, the Datasource should be real time enabled. Most of the standard DataSources are realtime enabled; however we can also create generic Datasource for the same purpose. Real-time data acquisition as a property of DataSources in SAP source systems is only possible technically under the following circumstances: In the source system, the BI Service API has at least the version Plug-InBasis 2005.1 or for 4.6C source systems Plug-In 2004.1 SP10.

Daemons
Daemons are used to perform the real time data acquisition in SAP BW. They are background processes that execute the InfoPackages and DTPs assigned under it at the stipulated intervals. While creating daemons, we have to specify the duration after which is it has to execute itself. Once the daemon is started, it keeps on repeating the execution of the InfoPackages and DTPs under it after the duration specified at the time of creation.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Live Scenario
DataSource Creation in Source System: Create the generic data source in R/3 system with Real Time Enable as shown in the following screen.

Here we have a generic Datasource in BW. This data source is real time enabled and extracts data from an R/3 source system.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Step 1: We have to first create an Init Infopackage for the Datasource and schedule it. Then we can create a RDA Infopackage. Same is done below.

Please do not forget to check the tick box for Real-Time data acquisition.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Thus, the Infopackage for Real-Time data acquisition is created for the Datasource.

Step 2: Now we have the Datasource ready, we come to modeling of Hybrid provider based on DSO. Go to Data flows in RSA1.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Step 3: We drag and drop Datasource icon from the sidebar, then right click on the icon. Click on use existing object to use the data source mentioned in the previous steps.

Step 4: Once we get the Datasource, right click and Show Direct Dataflow Before. Then it shows both the InfoPackages for the Datasource. Remove the Init Infopackage from the flow.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

The flow will now look something like this:

Step 5: Now drag and drop DSO from side menu. Right click and Create. Create a new DSO. Assign the data and key fields. Save and activate it. Come back to original screen.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Step 6: Now, drag and drop Hybrid Provider from side bar right click and Create. Create a new Hybrid Provider based on DSO. Assign the previously created DSO to this hybrid provider. Save and activate it. Come back to original screen.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

While creating the hybrid provider, it shows a warning as follows:

This means that the DSO can no longer be used as a standalone DSO. It will behave only as a part of hybrid provider. The data fields and the key fields in the DSO are automatically included in the Hybrid Provider. Step 7: Once created, it show a system created Infocube under that Hybrid Provider. The DSO is also linked with the Hybrid Provider. Here, the Hybrid Provider and the InfoCube have the description same as DSO; however we have flexibility to give a new name to Hybrid Provider when creating it.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Step 8: Now, draw arrows from the Datasource to the DSO. The first arrow will create the transformation. The second arrow will create the DTP.

Step 9: Double click on the transformation, do the mappings and activate it. Return to data flow, double click on DTP. Make the DTP RDA enabled as shown, and then activate it. Return to dataflow.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Please ensure that you choose the DTP type as DTP for Real-Time Data Acquisition. Step 10: Once Transformation and DTP are active, we need to assign the RDA Infopackage and the RDA DTP to a RDA daemon. Right click on the RDA Infopackage and select Assign RDA daemon. It will navigate to RDA Monitor. Create a daemon from left top corner create button and then assign the both of them to the daemon.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 12

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Creating RDA daemon: In the daemon settings, the Daemon specifies the technical number of daemon, short description specifies the description and the period specifies the duration after which it repeats the execution.

Step 11: We include the Datasource in the RDA daemon; it will automatically include both Infopackage and DTP.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 13

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

As you can see above both the Infopackage and DTP are listed under the RDA daemon.

Step 12: Now come back to Dataflow screen. Activate the data flow. All the objects used and create in the flow will be visible on the left side context menu.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 14

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Drill down the Infocube menu and click on the DTP. Now click on Process Chain maintenance. It will open a system generated process chain which contains DTP from DSO to Cube.

The auto generated process chain is as below:

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 15

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Step 13: The flow is complete. Go to transaction RSRDA (it is RDA Monitor). Run the daemon and the data in realtime gets update from source system to DSO.

The daemon has now run successfully. The request is running in daemon, it is loading data in DSO.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 16

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Step 14: Once the daemon is stopped, the data gets updated from DSO to Cube by the automatic triggering of the process chain shown in previous steps. Request is closed in daemon, now the process chain with DTP from DSO to Cube will run.

Following is the successful run of the process chain.

The new data updated in DSO is now updated into InfoCube after this process chain has run.

Result: So in this way, we can update the real-time data from the source system to BW system. The only thing needs to be taken care of is the scheduling of RDA daemon. Also the real-time data updating works similar to delta functionality. So whatever new data is created in the source system, it gets automatically updated in BW.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 17

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Related Content
Hybrid Providers HybridProvider Structure Based on a DataStore Object Real-Time Data Acquisition Design Consideration for 7.30 InfoProviders For more information, visit the EDW homepage

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 18

Hybrid Provider based on DSO using Real Time Data Acquisition in SAP BW 7.30

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 19