Grouping of InfoObjects in InfoProviders

This post to is to remember one nice functionality available in RSA1. It is related to InfoProviders and grouping of key figures. It comes very handy in case of huge InfoProviders with hundreds of KPIs.

In case of InfoCube/MultiProvider/VirtualProvider/HybridProvider objects - only for Key figures, characteristrics are grupped already through dimensions:

Here how does it look like:

 In case of DSO objects – available for grouing of Data Fields:

 

Limit on cubes per multiprovider ?

Sometimes BW developers are keen on to reach limits of BW. Like they want to try what are limits from any angle of BW. The angle may really very vary. Very common BW limits know to every developer are on term of no of InfoObjects (248) per dimension, no (233) Key figures in cube, no (13) of custom Dimensions (3 by default:  request, time, and unit). Also there can be no more than 2 billion (2.000.000.000) SIDs for one single IO. Therefore there can only be a max of 2 billion different values for the respective characteristic (note 1331403). Another example would be no of attributes that characteristic can have (was 250 attributes in BW 2.0 and 750 attributes in BW 3.0+). 

Following by some other limitation that I published in by blog:

Limitations of DTP’s filter

How long BEx report in Excel can be?

Here comes a doubt related to limit (if there is any) with regards of no of objects which are assigned to particular multiprovider. This goes along with performance. Actually which user runs a query against multiprovider OLAP processor is doing split of query to sub queries which every runs against particular infoprovider (e.g. base cube) which assigned into multiprovider. OLAP processor uses algorithm to run the sub queries. Depending on available systems work processes system runs them on certain amount of work processes in parallel. As a rule of thumb it is recommended to no go with more than 10 cubes per multiprovider. So in case you creating very patulous this can be bottleneck. 

For details see following SAP Notes:

629541 - Multiprovider: Parallel Processing

728017 - Multiprovider processing - exclusion of part providers

Tricky error while trying to view data in MProvider

I recently faced an error relate to Multiprovider. I needed to add one more cube into existing Multiprovider. While I was testing assignment of infoobjects coming from this newly added cube in Multiprovider I got following error:

INVALID_INPUT Infoprov Not Found RSD_TREX100

Caused by this message I was not able to see the data from this cube in “RSA1 -> Modeling -> Display data” neither in TA LISTCUBE. Data in Multiprovider in particular was still readable but no data was coming from newly added cube. Moreover error message popped up and no date was shown.

While I was trying to fix this issue I came to know that there are 3 possible reasons for it:

1. Wrong design of cube: I tried to test my newly created cube in TA RSRT (Analysis and Repair of BW objects). This linked me into the issue that some of key figures were not properly maintained in transformation used to load the data into the cube. After I corrected this issue I was able to read the data from the cube via Multiprovider.

2. You facing an issue as per note 1758050 - Display data raises 'INVALID_INPUT' error for valid values. The note is valid for BW 7.3 SP07. The Note fixing side effect of other note 1673230  - Display data of MPRO dumps on invalid input for 0INFOPROV. So it may happen that you implemented note 1673230 and this caused the issue. Therefore you need to implement other note: 1758050

Possibilities of BW projects documenting – InfoProviders and MultiProviders

Here’s another post from series how to document BW projects. Other posts were dedicated to queries and transformations. 

Even for infoproviders like cube, DSO, SPO, multiproviders we can reuse BW metadata repository. This feature is very simple accessible just by selecting particular InfoProvider and hitting F1 key. A new web browser session is opened with details on particular object:

 

However you won’t see here any assignments of objects. But for this you can hit F1 key on corresponding transformation. 

In case of multiproviders situation is different. It is because there is no assignment of infoobject from underlying cubes provided in BW metadata repository. One possibility I found is to use FM BAPI_MPRO_GETDETAIL. This FM is documenting multiprovider mappings.

You will get nice overview of all dimensions/infoobjects of that multiprovider. Basically what I smost important here is table PARTINFOOBJECTSIDENT where all the assigment of IOs from particlar cubes are happening.

For documenting of other types of BW’s objects use following FMs:

InfoCube - BAPI_CUBE_GETDETAIL

InfoObject Catalog - BAPI_IOBC_GETDETAIL

InfoObject - BAPI_IOBJ_GETDETAIL

InfoPackage - BAPI_IPAK_GETDETAIL

InfoSet - BAPI_ISET_GETDETAIL

DSO - BAPI_ODSO_GETDETAIL