Multiprovider

Posted by on


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 doesn’t 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..














Comments

  1. UnknownJuly 5, 2013 at 3:38 AM

    hi,
    very nice description..

    ReplyDelete
  2. Mohamed AslamJuly 5, 2013 at 3:44 AM

    Thank you :)

    ReplyDelete
  3. AnonymousAugust 11, 2013 at 12:34 AM

    very good sir ji keep it up

    ReplyDelete
  4. SankameshFebruary 9, 2014 at 6:48 AM

    Very good blog ! Thanks Mohamed Aslam :)

    ReplyDelete
  5. MichaelMarch 24, 2014 at 2:40 AM

    may i know the reason that why we are using multiprovider even though we are having only one data target ? thanks in advance. ur blogspot is awesome. please keep posting some thing about virtual provider, real time data acquistion using daemon...

    ReplyDelete
    Replies
    1. Mohamed AslamMarch 24, 2014 at 3:14 AM

      thanks michael....

      in this scenario we are not using a single target... we are using a DSO and Infocube...

      will post hybridprovider soon...

      Delete
  6. UnknownDecember 16, 2014 at 4:27 AM

    have this doubt, we have added the info object customer id from the DSO and not from the infocube so while assigning why does it give option of assigning it to both the cube as well as DSO as we have dragged the IO customer id of the DSO only.
    Thanks

    ReplyDelete
  7. AnonymousJune 6, 2017 at 8:58 AM

    The way you explaining the concepts is different sir!!
    I salute you. I read so many blogs ....This is the best blog!!!!

    ReplyDelete
  8. UnknownOctober 6, 2018 at 7:49 AM

    Thank you for sharing the valuable information. What is difference between Multiprovider and info sets

    ReplyDelete
  9. AnonymousMarch 11, 2020 at 8:25 PM

    may i know..how to put navigational attri in cube to navigational attri in multprovider?

    ReplyDelete

Post a Comment