{{Infobox
bodystyle = width:20em; |
title = Forecast versions for Hyperion |
titlestyle = |
headerstyle = |
labelstyle = width:33% |
datastyle = |
image = !Hfmlogo_large.gif! |
imagestyle = |
header1 = |
label1 = Type |
data1 = CXO-Cockpit Tips and Tricks |
header2 = |
label2 = Audience |
data2 = CXO-Cockpit Captain |
header3 = |
label3 = Difficulty |
data3 = High |
label4 = Applies to |
data4 = Hyperion Enterprise & Hyperion Financial Management |
Most Hyperion Financial Management and Hyperion Enterprise applications contain Forecasts. Some of these applications, even contain different versions of the Forecast, typically named like Version1, Version 2 and Version 3 or F1, F2 and F3.
In the CXO-Cockpit, we have the Version VER dimension, which is typically used for this purpose. In order to set it up in a user friendly way, you need to do something extra. By default, if you put the version dimension in the CXO-Cockpit and switch to e.g. Version1, then not only the Forecast, but also the Actuals will be retrieved for Version1, which is not correct. Since you only want to apply this dimension to the Forecast category, we recommend the following actions:
1. Map your data to specific versions
For example, to V1, V2 and V3
2. Create custom members for Versions, for example CXO_V1, CXO_v2 and CXO_V3 in the VER dimension:
Example for CXO_V1 (and the same has to be done for CXO_V2, CXO_V3):
CASE
WHEN
CAT.CAT.CurrentMember.Name='Forecast'
THEN
ELSE
VER.VER.NA /* or whatever you use as a default on your application */
END
3. In the security, make sure that only the custom VER member CXO_V1, CXO_V2 and CXO_v3 are included in the Point of View.
4. Change the Dimension Alias of VER (Version) in System Settings / Dimension Mapping to 'Forecast version' of 'Fcst version'
