The document discusses MultiProviders in SAP BW Rel. 3.0. A MultiProvider combines data from multiple InfoProviders, such as ODS objects, InfoCubes, and InfoObjects, using a union operation. It does not store physical data but defines characteristics and key figures to be collected from participating InfoProviders. Mapping is used to identify characteristics in the MultiProvider and select key figures, which can be aggregated from multiple sources. Examples demonstrate how a MultiProvider can combine sales data from an ODS and InfoCube uniformly for analysis and avoid data redundancy. The outlook discusses potential future extensions like integrating query data and interchanging MultiProviders with InfoSets.

1. MultiProvider Concepts
in BW Rel. 3.0
Dr. Bernhard Hornung
SAP Portals BI Platforms- MetaData

2. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 2
Overview

BW Architecture

InfoProvider / MultiProvider

Union-Operation to collect Data

Mapping: Identification and Selection of InfoObjects

(Abstract) Example

(Concrete) Examples

Summary and Outlook

3. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 3
SAP BW Architecture

4. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 4
InfoProvider

Definition of InfoProvider:

„Every object in BW MetaData Repository suited for Reporting with
Business Explorer“
 InfoObject (Characteristics with Master Data)
 ODS (Operational Data Store, contains consolidated and cleansed
transaction data at documentation level)
 InfoCube
(Data organized by star schema in facttable and dimensions)
 InfoSets
(Data from multiple Infoproviders – JOIN) (Rel. 3.0)
 MultiProvider
(Data from multiple Infoproviders – UNION) (Rel. 3.0)
© SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 4

5. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 5
InfoCube
InfoSet
InfoObject
Master
Data
ODS Object
MultiProvider
MultiProvider

6. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 6
MultiProvider

Definition of MultiProvider:

„An object combining the data of several infoprovider.
Data are brought together via union-operation“
 New Object Type in Administrator Workbench
 1 ... n participating infoprovider
(ODS / InfoCube / InfoObject / InfoSet)
 Definition similar to InfoCube
 No physical data storage
(data contained in part. Infoproviders only)
© SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 6

7. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 7
MultiProvider: Definition

Multi
Provider
ODS Object
MultiProvider, consisting of 1 ODS-Object and 1 InfoCube
C = Characteristic / K = Key Figure
MultiProvider, consisting of 1 ODS-Object and 1 InfoCube
C = Characteristic / K = Key Figure
InfoCube
C1
K1
C2
C2 C3 K3
K2
K2
C1 C2 K3
K1 K2
Object Structure

8. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 8
Mapping: Identification of characteristics
Country ........
Candidates for characteristic „Country“ in MultiProvider:
Infoobject „Country“ or Nav. Attr. „Customer__Country“ in ODS
Candidates for characteristic „Country“ in MultiProvider:
Infoobject „Country“ or Nav. Attr. „Customer__Country“ in ODS
Country Customer....
Customer__Country
InfoObject
Nav. Attribut
Object Structure

Multi
Provider
ODS Object
Master
Data

9. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 9
MultiProvider: Definition

Multi
Provider
ODS Object
MultiProvider, consisting of 1 ODS-Object and 1 InfoCube
C = Characteristic / K = Key Figure
MultiProvider, consisting of 1 ODS-Object and 1 InfoCube
C = Characteristic / K = Key Figure
InfoCube
C1
K1
C2
C2 C3 K3
K2
K2
C1 C2 K3
K1 K2
Object Structure

10. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 10
Mapping: Selection of Key Figures

Multi
Provider
ODS Object
Selection of each Key Figure from at least 1 infoprovider –
K2 may be selected from ODS AND / OR InfoCube
Selection of each Key Figure from at least 1 infoprovider –
K2 may be selected from ODS AND / OR InfoCube
InfoCube
K1
K3
K2
K2
K3
K1 K2
Object Structure
Aggregation (e.g. SUM):
K2 (Multi) =
K2 (ODS) + K2 (Cube)
Aggregation (e.g. SUM):
K2 (Multi) =
K2 (ODS) + K2 (Cube)

11. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 11
(Abstract) Example

MultiProvider
InfoCube IC1
ODS Object ODS1 K2K1C2_C1C2C1
K3K2C3C2C1
K3Origin K2K1C2C1
IC1IC1
ODS1ODS1

12. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 12
(Abstract) Example

MultiProvider
100700XGB
300200YGA
700
600
K3
500XHB
400XGA
K2C3C2C1
1007000IC1GB
K1
700
600
300
K3
5000IC1HB
400
200
0
0
IC1G
G
A
A
K2OriginC2C1
InfoCube IC1

13. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 13
(Abstract) Example
100700XGB
300200YGA
700
600
K3
500XHB
400XGA
K2C3C2C1
IC1
IC1
IC1
Origin
1007000GB
K1
700
900
K3
5000HB
6000GA
K2C2C1
MultiProvider
InfoCube IC1

14. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 14
(Abstract) Example
700600400AHA
100
200
K1
100
400
K3
100BGB
100BGA
K2C2__C1C2C1
ODS1
ODS1
Origin
700600400HA
K1
400
100
K3
100
100
200
100
G
G
B
B
K2C2C1
MultiProvider

ODS Object ODS1

15. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 15
(Abstract) Example
700600400AHA
100
200
K1
100
400
K3
100BGB
100BGA
K2C2__C1C2C1
ODS1
ODS1
Origin
700600400HA
K1
500
K3
200300GB
K2C2C1

ODS Object ODS1

MultiProvider

16. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 16
(Abstract) Example
700600400ODS 1HA
K1
500
K3
200300ODS 1GB
K2OriginC2C1
... from Cube... from Cube
... from ODS... from ODS
1007000IC1GB
K1
700
900
K3
5000IC1HB
6000IC1GA
K2OriginC2C1

MultiProvider

17. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 17
(Abstract) Example
500
100
200
700
300
0
ODS1 IC1G
G
B
B
700600400ODS1HA
7005000IC1HB
K1
900
K3
6000IC1GA
K2OriginC2C1

MultiProvider

18. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 18
(Abstract) Example
600900300GB
700600400HA
7005000HB
K1
900
K3
6000GA
K2C2C1

MultiProvider

19. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 19
(Concrete) Example: „Unselling Products“
400
0
0
Sales
600
P3
P2
P1
P4
Product

InfoCube: Sales
InfoObj: Product

MultiProviderMaster
Data

20. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 20
(Concrete) Example: „ ODS Invoice / Billing“
...
...
...
0
30
0
O.Q.
– I.Q.
...
...
...
0
5.000
1.000
N.O.V.
–
N.I.V.
40.000
60.000
75.000
30.000
20.000
40.000
Net
Order
Value
20039.00020000010001
18030.0001800003
...
...
...
120
Invoice
Quantity
...
...
...
15.000
Net
Invoice
Value
0003
0002
0001
0002
Item
Number
300
400
500
150
Order
Quantity
0002
Order
Number

ODS: Purchase 
ODS: Invoice

MultiProvider

21. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 21
(Concrete) Example: „ ODS Sales / Cube Sales“
...
30.000
20.000
40.000
Sales
Amount
(ODS)
4.80035.2000001
2.00028.0000003
...
0
Sales(ODS) –
Sales(Cube)
...
20.000
Sales
Amount
(Cube)
...
0002
Product

ODS: Sales 
InfoCube: Sales

MultiProvider

22. © SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 22
Summary and Outlook

Summary: (Features you can do with a MultiProvider)
 Uniform Combination of Data from several infoproviders
no matter what type of
 Avoid Redundancy of Data (no additional storage of records)
 Hide Complexity of definition in Business Explorer (query on
multiprovider)
 Analyze Functions (like compare) for objects of different
levels of staging

Outlook:
 Integration of Query Data (treat query as infoprovider)
 Interchange with Infosets (allow any combination of
UNION- and JOIN- operation)
© SAP AG 2001, PT2D2P5, TechED 2001 (Hornung) / 22