Database Reference
In-Depth Information
many of the form elements share similar coding needs, the goal here is to provide a few
templates that you can use to create your applications.
10.4.7 Managing Combo Edits
Consider a planning and budgeting cube. using this cube, among other things, we
budget product revenues. our example company has products in a dimension called
“Segments,” channels for peddling those products in a dimension called, you guessed
it, Channel, and an Entity dimension containing various business units by geographical
unit (Figure 10.4).
Although it isn't visible from Figure 10.4, we know from a business perspective that:
•  only some entities can sell through some channels.
•  only certain products are sold through each channel.
Thus, the relationship of valid data intersections may be represented as: Segment ->
Channel -> Entities: A given product only has valid data intersections for x list of
channels, which are only valid for y list of entities. This relationship is commonly called
a sparse interdimensional relationship.
In Figure  10.5, we see that, for instance, the only valid places to plan operating
revenue for Latin America is in the government channel for all products, and EmEA
sells neither Audio Systems nor televisions, but has some data in all Channels. At this
point, you may realize the challenge here. how do you prevent planners from placing
data into intersections that are invalid? If you do not enforce some of these restrictions,
planners will inevitably enter data into the wrong combination. trying to find this mis-
placed data later is not easy and can eat up an administrator's time.
10.4.8 Creating a Combo Edits Lookup Table for Valid Sparse Combinations
Several proven methods exist in Essbase to handle this situation, each with its draw-
backs usually involving added dimensions and members, and extra maintenance.
Figure 10.4 Sparse interdimensional relationships.
Search WWH ::




Custom Search