Multiproviders/Infosets

MultiProviders and InfoSets 

An InfoProvider is a BI Content object for which BI queries can be created or executed in the  BEx.InfoProviders are the objects or views that are relevant for reporting. A MultiProvider as well as an InfoSet do not physically store data, but display logical views.

• A MultiProvider builds up a data union of basic InfoProviders.

The complete data of all basic InfoProviders are available for reporting. A MultiProvider is interpreted

at runtime as independent BI queries on each basic InfoProvider where the results are merged into a

single result set.

• An InfoSet builds up a data join of basic InfoProviders.

The valid combination of records from the basic InfoProviders is determined by the join condition ofthe InfoSet.

1 Do’s and Don’ts for MultiProviders and InfoSets

MultiProviders

• When the reporting scenario is to be extended, use a MultiProvider as central interface between query definition and basic InfoProviders. When another InfoProvider is added to the MultiProvider definition, the technical name of a query based on the MultiProvider remains unchanged.

• Use a MultiProvider to reduce the size of the basic InfoProviders. Advantages: parallel access to underlying basic InfoProviders, load balancing, resource utilization, query pruning.

• Make sure that your MultiProvider only retrieves data from relevant basic InfoProviders at query runtime by

o Using constants in the design of the basic InfoProviders

o Using different key figures in the design of the basic InfoProviders

o Using characteristic 0INFOPROV when designing a query on the MultiProvider

• Are you planning to use a MultiProvider? If so, you have to ensure that the characteristics you want to report exist in all basic InfoProviders.

• Do not use more than one non-cumulative InfoCube (InfoCube with at least one non-cumulative key figure) because this could lead to incorrect query results.

• Do not use calculations before aggregation on MultiProvider because this may lead to wrong query results.

• Do not combine basic InfoProviders having inhomogeneous data models in a MultiProvider. Use the report-report interface between queries defined on the basic InfoProvider instead.

• Avoid using only parts of compound characteristics in the constituent basic InfoProvider of a

MultiProvider/

InfoSets

• Do not use more than 10 InfoProviders in one InfoSet. It is better to create multiple InfoSets

depending on reporting needs.

• Do not use more than 10 joins in one InfoSet (especially if you expect high a data volume).

• InfoSet queries can be used for DataStore objects without the activated BEx Reporting indicator.

See also the Performance Aspects section of this document.

• Do not use calculations before aggregation on InfoSet because this may lead to wrong query results.

• If there are InfoSets with time-dependent master data, do not restrict the data by the fields Valid from (0DATEFROM) and Valid to (0DATETO). See also an example in the Data Models using InfoSets section of this document.

Performance Aspects of MultiProviders and InfoSets

MultiProviders

• These are the advantages of MultiProviders:

Local queries (on each basic InfoProvider) versus global queries (on MultiProvider, parallel

execution).

 Independent (and parallel) data load into the basic InfoProviders.

 Small total data volumes: basic InfoProvider have less redundant data; they are sparsely

filled and less complex.

• As a general rule, we recommend assigning up to 10 basic InfoProviders to a MultiProvider. If the

number of basic InfoProviders is significantly higher, the overhead in combining results at BI query

runtime may become excessive.

• If a MultiProvider contains at least one basic InfoProvider with non-cumulative key figures, all queries

are processed sequentially.

• The performance optimizing tools of the OLAP (such as caching, aggregation) only work for a

MultiProvider if all constituent basic InfoProviders of the MultiProvider support these tools.

InfoSets

• InfoSets do not have the set of performance tools as InfoCubes (such as aggregates, partitioning,

and compression).

• Use left outer joins in InfoSets only when necessary. A left outer join has a significantly worse

performance than a corresponding inner join.

• If your reporting requirements on a DataStore Object are very restricted (that is, you want to display

only very few, selective records), use an InfoSet on top of the DataStore object and disable the BEx Reporting indicator. This results in better data loading performance, but also in worse performance at BI query run time if more than 10 records are selected from the DataStore Object.

MultiProviders:

1.Go to the info area where you want the multiprovider; right click and chose create multiprovider.
2. Chose a technical name and also choose the infoproviders that you make part of this 

multi provider.
3. When you confirm your entries, you will get a infocube maintenance screen; on the right side, you will see the characteristics available in al the basic cubes that you choose in the first step. 
4. Select the chars that you wish to be in the multiprovider and similarly for time chars, key figs, and nav attributes ( if any).
5. Choose to create dimension and you will get a system msg whether to create from any of the basic cubes.
6. Either select to create your own dimension and insert all the chars in to the approprate dimensions.
7. Go back to chars tab and there will be tab for "identification" click that and here is where you specify which are the chars form each cube you want into the multiprovider. And likewise for the key figure.
8. Activate the multiprovider.

InfoSets

The step by step procedure  

1.Go to InfoProvider tree of the Modeling function area in the Data Warehousing Workbench.

Or RSA1 --InfoProvider.

Under your InfoArea -Rclick -Create InfoSet

2.Enter the following descriptions for the new InfoSet:

 Technical name

 Long name

In the Start with InfoProvider section, you determine which InfoProvider you want to use to start defining the InfoSet.

Select one of the object types that the system offers you:

 DataStore object

 InfoObject  

     Sdastard InfoCube

If you want to choose an InfoObject, it must be a characteristic with master data. The system provides you with the corresponding input help.

3.Create relationships by mapping like fields , default is Inner Join. You can change to OUTTERJOIN by selecting the join and change the option from context menu.

4.Now save & activate the InfoSet.