Multiprovider We have seen InfoProviders like DSO, InfoCube, InfoObjects...

These all are objects which can physically hold data.... we have some more infoproviders on which reporting can be performed, but they cannot physically hold data... and they wont be having any tables also.. They are virtual Infoproviders..

Multiprovider Infoset Virtual Cube

Lets see what is a Multiprovider and What are its uses?

The design of a data target such as an Info Cube or DSO is based on one business process, for example, one Info Cube for sales billing processing and another one for sales order processing. In this way BI will have multiple Info Cubes, each supporting an individual business process. In real time we will get scenarios where data from two different Info Cubes needs to be joined. SAP BI Supports queries based on a single Info Provider. To support reporting requirements across multiple data providers, we need not to load data from the individual data providers to the new data provider. The system provides a better way to handle this situation with the object Multi Provider. A Multi Provider is a logical definition that doesnt physically store data. The data lies in the underlying data provider on which the Multi Provider is created. We can create a Multi Provider with combination of the following objects.

Info Cube Data Store Object Info Object Info Set

lets see how we create a multiprovider on a DSO and Cube..

lets create a multoprovider on top of the highlighted Cube and DSO..

drag and drop the dimensions and keyfigures needed...

Now we have to identify the characteristics included in the Multi Provider and match them to the characteristics or navigation attributes in the base info cubes.

Identify characteristics for all characteristics and keyfigures.. And activate Multiprovider

now reporting can be done on Multiprovider..