...
- Load Set for a full data refresh. When executing such load set (of which you can only have one!) first all data and dimensions in the CXO Cockpit databases are cleared and then refilled with new data. This only needs to be done when:
- No extractions have been done yet
- Data in the past have changed
- New HFM metadata have been loaded
- You want to make an alternative selection from the HFM dimensions (more / less details from the Entity dimension, Account dimension, more Scenarios. I.e., any action that require rebuilding of the dimensions in the CXO-Cockpit application.
- Incremental Load Sets: these can be used to quickly replace a slice of data usually one Scenario, one Year and one Period. The CXO dimensions are not refreshed.
...
- . Incremental Load Sets can be executed manually but can also be used for Real-Time Synchronization.
Base Set and Subsets
A Base Load Set (type 1) looks like:
...
Now for this Subset we select Scenario = Actual, Year = 2007 and Period = Jan, Feb:
This perfectly illustrates why Subsets are useful: for 2007 we are only interested in two months, while for 2006 (the history) we want all periods.
We also make a special Subset for the Budget scenario: two full years:
Other HFM dimensions
To complete a Base Load Set we must also select at least one member from each of the other HFM dimensions.
Value
A typical selection from the Value dimension is:
This will extract each Entity in it's own currency and all Entities in USD (provided the Entities are translated into USD within HFM).
Include the [None] member if you want to report on / use Currency Conversion rates.
Note that we will not extract 'XXX Total' itself: always the underlying 'XXX' and 'XXX Adjs' members are extracted. In the example of 'USD Total', in CXO we will see:
Entity
When selecting members from the Entity dimensions you should expand the tree to the level you want to include. For example:
In this example, in HFM more levels exist, but we deliberately decided to leave out details. It is not needed to expand to a fixed level. We could have decided to only expand EastRegion further.
It is also possible to skip a parent node. Suppose we don't want to have UnitedStates as an intermediate node in CXO, then we can de-select it:
This would move EastRegion and WestRegion one level up, making them children of Geographical.
From a functional perspective you should not do this is you selected [Contribution Total] in the Value dimension, because that selection only reports correct numbers if the parent-child structure is equal to the original.
To get Currency rates in CXO, also include Entity [None] in the selection.
Account
Selecting members from the Account dimension is done slightly different:
Like with Entity, the members that you do not select will not be included in the corresponding Account dimension in CXO. A major difference is, however, that all the levels below a selected member will automatically be included in the extraction and the dimension build-up in the CXO-Cockpit application. So, even though we only selected 'NetProfit', within CXO we will include all details of the underlying members all the way down to the base-level: