Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
COMPOSITEPROVIDER
This article comes as a continuation of the previous article based on the difference
between the old objects in the SAP and the new objects created in SAP BW on
HANA. The last article talked about the classic DSO (Data Store Object) and the
new ADSO (Advanced DSO), that replaces 4 of the classic objects in SAP: InfoCube,
DSO, Hybrid Provider and PSA.
In this article we continue the same theme referring to different topics. The
subject of this article will be the difference between Multi Provider and Composite
Provider.
At first, I will talk about the classic Multi Provider and its functionalities. Then I’ll
talk about the CompositeProvider and the differences between it and the Multi
Provider.
THE CLASSIC MULTIPROVIDER
What is a MultiProvider?
A Multi Provider is an InfoProvider that combines data from multiple InfoProviders
and makes it available for reporting. It does not contain any data: its data comes
entirely from the InfoProviders on which it is based.
The MultiProvider is most used to create queries based on multiple InfoProvider.
Sap BI supports queries based on a single InfoProvider. The best way to avoid
loading data from an InfoProvider to another and so on, is to create a
MultiProvider based on the Provider you need for the query.
2.Scenario:
For example, you can combine data from 2 InfoCubes. One Infocube is for Actual
data and the second is for Plan data.
By using MultiProvider we can compare data from these two InfoProviders. When
you want to create a MultiProvider you can use multiple InfoProviders and any
type of InfoProvider is accepted. You can analyze and report the data based on this
Multiproviders. If we want to create a query based on a MultiProvider is important
to know that, this query is divided internally into subqueries. There is a subquery
for each InfoProvider included in the MultiProvider. These subqueries are usually
processed in parallel.
Now, that we through with the MultiProvider topic, let’s take a closer look at the
other concept of this article: the CompositeProvider.
COMPOSITEPROVIDER
What is a CompositeProvider?
The CompositeProvider is an Info Provider, which combines data from several Info
Providers and makes this data available for reporting and analysis, using an SAP
HANA database. These new InfoProvider forms the Virtual Data Mart layer in the
BW on HANA system.
The CompositeProvider consolidates the number of InfoProviders types and
harmonizes the modeling of mixed BW on HANA scenarios:
Also, in this tab you can select the primary key common joins, by right click on the
field which you want to join:
In the Target section are the fields that you want to see in the output.
In the Output Tab are the fields which we had selected to the output.
FIELDS IN A COMPOSITEPROVIDER
The fields of CompositeProvider can be associated with an info-object or with an
open ODS view. This will give you access not only to the navigation attributes
available for selection for the output structure of the CompositeProvider, but it will
also give you access to master data at report runtime. In conclusion, we can save
time by using fields instead of modeling with InfoObjects.
When fields are assigned to the CompositeProvider, the associations are
automatically set.
MODELING SCENARIO USING COMPOSITEPROVIDER:
Now that we managed to create a CompositeProvider, let us work based on
scenario. The scenario is the following:
Track the sales information in a company based on customer and the product sold.
1. We begin by creating a CompositeProvider to combine data from 3 DSO
(Product master data DSO, Customer master data DSO and Sales information
DSO)
2. In this case we don’t need to create an additional Infocube to have all data
available for reporting
3. The data from the sales information DSO will be taken in the
CompositeProvider using Union operation
4. We can add the customer and the product master data to the
CompositeProvider using Join operation.
5. In this way, the CompositeProvider will contain all the data from Sales DSO
with the corresponding attributes (Product and Customer).
Step 2
Select the MultiProvider which we intend to convert into CompositeProvider. Then
write a name for the new created CompositeProvider.
Note! The MultiProvider and the CompositeProvider will have the same name, so
that no Queries or Workbooks will get affected.
Step 3
This program will only work if we create a backup to the MultiProvider.
Note! If you execute the program without a backup you will receive this error
message:
“Conversion is not allowed without backup”
Step 4
Write a backup InfoProvider name and execute in Simulate mode to check if the
MultiProvider can be converted to the CompositeProvider.