Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Integrated Planning
Modeling
•Design of an InfoProvider
•MultiProvider in Planning
P1 100 50 75
Account Model
Product Price Cat Price The price category characteristic
P1 Sales Price 100 replaces the key figures of the key
P1 Mfg. Price 50 figure model, namely in connection
P1 Mean Price 75
with one single key figure
• You can approach the planning with two different modeling strategies, although you must already decide which of the modeling versions you want to use,
the “key figure model” or the “account model”, when you are creating an InfoProvider
• The above illustration uses a simple example to show how the terms key figure model and account model are defined.
• you are working with a limited, and in particular a constant, number of key figures and
• all or at least a large proportion of these key figures of a data record are also used in the other data records
• You should use the account model when
• you are working with a high and in particular, a varying number of key figures and
• most of the key figures within a data record would be empty in the key figure model
• It is easy to add another price category (see example above) in the account model, because the data structure does not have to be changed. In the key
figure model, on the other hand, an additional key figure must be added to the InfoProvider. The extent to which this difference can be seen as an
advantage or disadvantage largely depends on the frequency with which the changes are to be expected.
The decision “Key Figure Model or Account Model” should generally be based
on which model is better suited to the respective planning process!
• The transaction data is stored in the BW system. Investigations have shown that the reading time largely depends on the number
and not the size of the data records.
• The previous example shows that a switch from the key figure model to the account model increases the number of data records by a factor
of 3, resulting in longer reading times. The increase factor depends on whether all key figures are used in every data record in the key figure
model, because if you switch to the account model, only those data records are created for which the key figure is not equal to zero.
• The transaction data is stored in main memory of the application server after it is read from the BW system. The
amount of memory required depends, among other things, on the number and length of the data records, whereby the
length is influenced by the selection of the data model:
in the key figure model, the data records are longer than in the account model, and they therefore require more memory per
data record.
• Depending on the relationship between the data record length and number, either the key figure model or the
account model will take up less memory.
• The performance of a planning function strongly depends on the number of data records. Therefore, it should be possible to
execute it faster in a key figure-based model than in an account-based model. On the other hand, the data records in a key figure model can
also become large, which also has an impact on performance. Thus a planning function sometimes can be slower in the key figure-based
model.
• The table above lists the advantages and disadvantages of the key figure model.
Modifications during
configuration are simpler.
Simply add a hierarchy
node or a characteristic in
• The table above lists the advantages and disadvantages of the account model.
•Design of an InfoProvider
•MultiProvider in Planning
MultiProvider
MultiProvider
InfoProv
ider
DataStore Aggregation
InfoCube MasterData InfoSet
Object Level
Data Selection
InfoProvider 2
MultiProvider
DataStore Aggregation
InfoCub MasterData InfoSet
Object Level
MultiProviders are used very often in practice because they are very flexible
An advantage is that if new InfoProviders are created, they can very easily be included in the modeling of the MultiProvider, and
that the queries already existing for the MultiProvider do not have to be adapted
New queries for the MultiProvider with reference to the subsequently integrated InfoProvider can be correctly addressed with
reference to the “InfoProvider” field in the query
A disadvantage with respect to a simple InfoProvider is that in a MultiProvider scenario, at runtime a split is always effected for all
selections, as to which InfoProvider subordinate to the MultiProvider the selection comes from. In contrast to BW-BPS, the
related rad statements in the BW-Integrated planning are not executed sequentially but in parallel, with the aid of the file
manager.
MultiProvider
InfoProvider
Real-Time DataStore
InfoCub InfoProvide InfoObject
Object
As you will notice, all the aggregation levels are created on the MultiProvider, so that both the planning -that is, the planning
functions - and the plan queries can be set up on the same aggregation level. This reduces the frequency of errors and the
granularity of the planned and reported data is the same!
If reference data is required for the actual status, it can be read from the “InfoCube” or the “DataStoreObject”, for example.
Aggregation Levels
Real-Time
Real-Time InfoCube
InfoProv
The above illustration shows a second modeling option for MultiProvider.
Here a MultiProvider is placed on at least one aggregation level, but otherwise also additionally on other InfoProviders, so that
the above MultiProvider is only suitable for reporting.
A planning function, on the other hand, must be created on an aggregation level - this is not possible directly on a MultiProvider
The advantage of this model approach is that the underlying aggregation levels and other InfoProviders and their data records
can have a different granularity.
Thus the plan data from real-time providers could be planned on a quarterly level, and the actual data of the InfoCube could be
kept on a monthly level.
In a query on the MultiProvider that combines this data, the granularities could be “mixed”, for example by corresponding
selection in the data columns of the query.
Please note that multiple aggregation levels can be used in a query simultaneously
MultiProvider
Mandatory!
Real-Time MultiProvider
InfoProvider
Real-Time
InfoProvider InfoCube DataStore InfoObject
In general, an aggregation level can be defined on a real-time InfoProvider. This is then known as a simple aggregation level.
1. To define an input-ready query, you can choose between two basic models:
1. Directly on a complex aggregation level
2. Directly or by means of a MultiProvider on a simple query.
Please note that aggregation levels and MultiProviders cannot be nested, which means that one aggregation level cannot be located in another aggregation
level
P! PG1 V1 2010 10
P2 PG2 V1 2010 20
P3 PG3 V1 2010 42
Product Product Version Year Group Delta record in fact table of the real-time
Group Sales
InfoProvider
-># For product that was not included in
planning of aggregation level
# PG1 V1 2010 10
PG1
V1 2010 30
InfoProvider Product Product Version Year Profit Data records in the MultiProvider or in
Group the aggregation level of the
MultiProvider
InfoCube1 P1 PG1 V1 2010 10
InfoCube2 # PG2 V2 2010 30
In the case of a more complex aggregation level that is created on a MultiProvider (compare the figure “Modeling Prerequisites for an Input-Ready Plan
Qyery”), the above figure shows that in the related aggregation levels, the “InfoProvider” characteristic must always be included in order to enable the
reading and writing of data on a source-related basis
This characteristic of the MultiProvider enables you to, for example, copy actual data from one InfoProvider to another, whereby the copy function for the
aggregation level of the MultiProvider must be created.
The MultiProvider technology is thus an option in BW-Integrated Planning for the cross-InfoProvider processing of data.
Reporting Planning
DTP
Actual
Plan Data
Data
Actual Plan Actual Plan
Advantages of separate data storage:
Is used when actual and plan data are structurally very similar, whereby the granularity of the actual or plan data can be finer or coarser
Reporting is difficult if the granularity of actual and plan data differs too greatly
The structure of the data can be changed with respect to the original data, so that decoupled, shared reporting of actual and plan data is possible
?
MultiProvider with Planning Function
Actual Plan
Advantages of the data transfer process
Less memory is needed on the server as no buffering mechanism is used
Before writing into the database you can drop the database indices, write the data, and then create the indices again. This is considerably faster
than updating the indices after each new data record.
Due to the optimization of the parallelization, this process is faster than a planning function
As you are using a real-time InfoProvider as target you have to switch it to “load enabled” before the staging process starts and back to “planning
enabled” afterwards. During that time and during the load process, nobody can perform planning on the InfoProvider
•Design of an InfoProvider
•MultiProvider in Planning
Aggregation Aggregation
MultiProvider
Level Level
Aggregation
MultiProvider
Level
Actual Actual
Plan InfoCube Plan InfoCube Plan InfoCube
InfoCube InfoCube
For the BI-Integrated planning, the user basically needs the same authorizations as for the analysis of data in a query
In addition, along with the authorization for displaying data, the authorization for changing data is also required in the analysis authorization.
The user requires the authorization for the InfoProvider on which the query is defined.
For a query on an aggregation level that was itself defined on a MultiProvider, the aggregation level is authorized for the field RSINFOCUBE in S_RS_COMP. In the
analysis authorizations, on the other hand, you use the MultiProvider
Authorization Objects
Dig Deeper in BW
365 Course S_RS_PLSE Authorization for working with planning functions
The above illustration shows the authorization objects for business planning in object class RS