Essbase - Consolidation Storage Properties:
1) Store data
2) Dynamic Calc
3) Dynamic Calc and Store
In oracle essbase
data storage properties will be defined where and when consolidations are
stored. For example members are tagged as store data then Essbase sums the
values of store data members and stores the result at parent level.
Total we have six
storage properties in Essbase:
1) Store data
Store data
property is a default storage property, when we load the data in to essbase
will store values in the cell. Store the data values with member.
2) Dynamic Calc
When we tag any
member as a dynamic calculation the values are never stored in the cell, but
values are dynamically retrive in the reports. The data associated with the
member is not calculated until requested by a user. The calculated data is not
stored.
Dynamic calculation options allow outline members to be calculated when
requested by users rather than during the batch calculation process.
Advantages:
Memory saved.
Calculatin would
be fast.
Backup would be
fast.
Retriveng would be
fast.
Disadvantages:
Reprt performance
would be slow.
3) Dynamic Calc and Store
When we tag any
member as dynamic calc and store, the value is does not store the first time.
However the value is dynamically retrived and stored in the block. Would not
calculate the data value until a user
requests it, and
then store the data value.
Advantages:
Memory saved.
Calculatin would
be fast.
Backup would be
fast.
Retriveng would be
fast.
Disadvantages:
Reprt performance
would be slow.
4) Shared member
4) Shared member
The shared member
storage property provides a way to reuse data that essbase has indexed or
calculated. Shared members, instead of storing data in multiplies places,
create a pointer to a stored member. The data value associated with shared
member comes from different member having the same name. Shared member is also
called alternative hierarchy.
Conditions of
shared member:
Shared members
should not have children below it.
The original
member and shared member should be in the same dimension and original member
should be created first only then we can create shared member.
We do not have any
formulas, attributes and UDA's to the shared members.
5) Never share
5) Never share
The data
associated with the member is duplicated with the parent and its child if an
implied shared relationship exists.
6) Label only
6) Label only
Label only used
for all grouping pupose or navigating purpose and we would not tag a 'level 0'
as lable only. Although a label only member has no data associated with it, it
can display a value.
The label only tag groups members and eases navigation and
reporting. Typically, label only members are not calculated.
