Skip to Content

Hybrid Provider in a Nutshell

In this blog, I am defining the BW Hybrid Provider in simplest way, based on the questions that come in my training classes.


Hybrid Provider is one of the new infoproviders introduced in NW BW 7.30. Reporting users in BW have requirements for operational reporting and also real time reporting scenarios. By using Hybrid Providers they can report on real time data. It is similar to Multiprovider, as it does not store any data but the data is stored in underlying providers. The two components of the Hybrid Provider could be a standard DSO based on real-time data acquisition and a standard cube or a virtual cube and a standard cube. The data of the standard cube can be pushed in BWA for better performance.  Other reason for using Hybrid Provider is data in DSOs can be accelerated by using a Hybrid Provider in connection with an InfoCube that has BWA-only persistency.


In BW 7.30, there has been lot of improvements when it comes to modeling objects. Most of the objects are created and maintained by the system. For creating Hybrid Provider, you do not have to create a transformation, DTPs as we would in BW7.0. Depending on the requirement you can use a DSO or a Virtual provider as the leading infoprovider and rest all the objects are created by the system. When hybrid provider based on DSO (with RDA capability) is activated system creates hybrid provider, standard cube, transformation and DTP between DSO and Infocube, and process chains for generated DTPs.  You can add or remove infobjects from the Hybrid Provider but not from the generated objects.


Hybrid Providers can be used as infoprovider to create queries. It can be used as part of Multiprovider but they cannot be used as source objects in the dataflow.


Modeling and creation of Hybrid Provider is part of DBW73 and BW330 courses.   For information about Hybrid Provider creation, please refer to link on the Help Portal.

1 Comment
You must be Logged on to comment or reply to a post.