Database Reference
In-Depth Information
Figure 3.23 Prefix/suffix setting.
element inherit the properties. This inheritance is a marked difference from deployment
properties.
It is important to understand the difference between the cube schema Essbase prop-
erties and dimension elements settings. In short, where possible, use dimension element
properties for any settings you want universally applied. Leverage cube schema proper-
ties to further refine settings prior to a specific cube deployment.
For example, for general concatenations of product codes, you can use the dimension
element properties to ensure consistency of Sku-level names regardless of hierarchy
in a specific cube. you might, however, decide for a given cube that the product family
name needs to be appended to the Sku as you drill down the hierarchy. In this particu-
lar case, you can leverage the prefix capabilities of the cube schema's Essbase properties
to ensure that the name is appended as desired for that specific cube (Figure 3.23).
3.5.4 Simple Hierarchy Types
Before we get into detail on specific techniques for creating dimension or hierarchical ele-
ments, we should discuss the fundamental hierarchy types within Studio. While this may
seem an obvious topic, there is often confusion around the three Studio hierarchy types:
1. Standard hierarchy: This basic Studio hierarchy type is most often used.
hierarchies of this type can represent Any base dimension type in Essbase
(including accounts/measures, and time). The only exception to this is the Date-
time dimension type.
2. measure: This is a specialized measure/accounts hierarchy. Whether you use
this hierarchy type or a standard hierarchy type depends on the nature of table
you are leveraging for the build (more on this topic in a moment).
3. Calendar: This is a specialized hierarchy type specifically for the creation of an
Essbase Date-time calendar dimension. The Date-time dimension type was
introduced in version 9.x of Essbase to allow for more complex Date-time logic
in Essbase. The assumption when using a Date-time dimension is that your
model only requires a single time dimension representing a true date continuum.
This hierarchy type is not commonly used in both Studio and Essbase in general.
3.5.5 When to Use the “Measures” Dimension
one of the most common questions when working with hierarchies in Studio pertains
to the use of standard hierarchy versus “measures” hierarchies for the creation of an
Essbase accounts dimension. The answer to this question is that it depends on the struc-
ture of the table(s) you use to build the dimension.
If you use a dimension table that enumerates the accounts in a level/generation fash-
ion, or if you are using a fact table with multiple fact columns, then you can leverage a
“measures” hierarchy type. For example, look at the table in Figure 3.24.
Search WWH ::




Custom Search