A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for analysis purposes. The MultiProvider itself. Overview. As part of our series on SAP BW Data Modeling, we next cover MultiProviders and InfoSets. MultiProviders and. InfoSets enable you to combine other. 3 Jul Multiprovider. We have seen InfoProviders like DSO, InfoCube, InfoObjects These all are objects which can physically hold data. we have.

Author: Nikokus Mebei
Country: Libya
Language: English (Spanish)
Genre: Art
Published (Last): 5 January 2018
Pages: 480
PDF File Size: 20.26 Mb
ePub File Size: 3.3 Mb
ISBN: 283-3-40533-322-8
Downloads: 83336
Price: Free* [*Free Regsitration Required]
Uploader: Voodoosida

Its data comes entirely from the InfoProviders on which it is based.

Otherwise the value is totaled incorrectly in the MultiProvider because it occurs several times. As a comparison, see InfoSet. If a key figure is contained in a MultiProvider, you have to select it from at least one of the InfoProviders contained in the MultiProvider.

These joins only combine values that appear in both tables. These InfoProviders are connected to one another by a union operation.

MultiProviders only exist as a logical definition. Technically there are no restrictions with regard to the number of InfoProviders that can be included in a MultiProvider. If this is not clear, you have to specify the InfoObject to which you want to assign the characteristic in the MultiProvider.

what is multiprovider

In general, one InfoProvider provides the key figure. The MultiProvider itself does not contain any data. In this case, select just one of these InfoObjects in the assignment table.

A query based on a MultiProvider is divided internally into subqueries.

Dividing a MultiProvider Query into Subqueries. A union operation is used to combine the data from these objects in a MultiProvider. You do this when you define the MultiProvider. Integration MultiProviders only exist as a logical definition. However, there are cases in which it is better to select the key figure from more than one InfoProvider: In a MultiProvider, each characteristic in each of the InfoProviders involved must correspond to exactly one characteristic or navigation attribute where these are available.

List of Slow-Moving Items. List of Slow-Moving Items Example: In contrast to a union, joins form the intersection of the tables.

The data continues to be stored in the InfoProviders on which the MultiProvider is based. Modeling MultiProviders with more than 10 InfoProviders is also highly complex.

SAP BW – MultiProvider

However, if 0SALES multiproovider stored as an actual value in one InfoProvider and as a planned value in another InfoProvider and there is no overlap between the data records in other words, sales are divided separately between several InfoProvidersit is useful to select the key figure from more than one InfoProvider.

However, we recommend that you include no more than 10 InfoProviders in a single MultiProvider, otherwise splitting the MultiProvider queries and reconstructing the results for the individual InfoProviders takes a substantial amount of time and is generally counterproductive. These subqueries are usually processed in parallel.

A MultiProvider allows you to analyze data based on several InfoProviders. Here, the system constructs the union set of the data sets involved; all the values of these data sets are combined. A MultiProvider can consist of different combinations of the following InfoProviders: The following sections contain more detailed information: See the following examples: If the 0SALES key figure is stored redundantly in more than one InfoProvider meaning that it is contained fully in all the value combinations ij the characteristicswe recommend that you select the key figure from just one of the InfoProviders involved.

In contrast to a union, joins form the intersection of the tables As a comparison, see InfoSet. InfoSets are created using joins.