Documentation for CXO-Cockpit Reporting Suite 4.2, click for CXO-Cockpit Reporting Suite 4.1 Documentation or check the CXO-Cockpit Website.

 Help

Book creator (disable)

 Add this page to your book Show book (0 pages) Suggest pages

From CXO Cockpit Reporting Suite Documentation

Load Sets

25. Go to the Load Sets tab:

In the Load Sets tab we specify the combinations of Scenarios, Years and Periods to be loaded into CXO-Cockpit. By definition, the first Load Set will be used to do a full data-load (replacing the entire existing data in the CXO-Cockpit. Each additional Load Set is an incremental Load Set, which we can use to only replace a small section of the data

The full Load Set (usually called Base Set) can consist of more than one Subset. A Subset is a more refined selection of data, to be loaded into CXO-Cockpit, based on Scenario, Year and Period. During this training we will create 4 Subsets with the following specifications:

• Subset Act prev y: Scenario Actual, Years 2007, 2008, Periods Jan - Dec
• Subset Act cur y: Scenario Actual, Year 2009, Periods Jan - Sep
• Subset Budget: Scenario BudV1, Years 2008, 2009, Periods Jan - Dec
• Subset Forecast: Scenario Forecast, Year 2009, Periods Jan - Dec 

For the First Subset, rename 'Base' into 'Act prv y' and press the Save button.

Now select Scenario Actual and select Years 2007 and 2008. For the Period dimension, first expand it to the lowest level and subsequently de-select the [Year] and Q levels.

The result mus look like:

Press Save.

To add the second Subset, click  in the Subset panel and add Act cur Y in the Edit text-box. Press Save
Make sure that you make the following selections (note: the Period dimension now only includes Jan - Sep.

Press Save.

Repeat this for Subsets Budget and Forecast (see bullet list for the definitions: make sure that you de-select the [Year] and Q levels and don't forget to Save each Subset)

Dimension Members

26. On the Load Sets tab we only select the extraction-detail for the Scenario, Year and Period dimension. The details for the other dimensions can be specified by first selecting the first Load Set and the first Subset and then click the tab Dimension Members. Here we select all members that we want to end-up in the OLAP database and - hence - in the CXO-Cockpit reports. Member-selection is done by a combination of expanding the hierarchies to the required level and by checking the box in front of each requested member :
  a. Intercompany partners:
  
  Ignore ICP

  b. Values:
  
  (only USD Total, Parent Curr Total and Entity Curr Total must be selected)

  c. Entities:
Start with checking the box of Geographical and then start expanding the tree by clicking the + sign until the desired level is reached. The lowest Entity-level is not included in our current selection. This implies that e.g. Italy is a base-entity in the CXO-Cockpit application, while it is a parent member in HFM.
  
The JointVenture node is empty in this HFM application, hence we do not select it. It is possible to flatten a hierarchy in the Cockpit. We could have decided to exclude the continent level by unchecking the boxes before United States, Europe, SouthAmerica, and ASIA. In the Cockpit the children of these continent-nodes will then become children of Geographical. This can be a very useful feature if an HFM application contains a lot technical sub-consolidations that you don’t want in drill-down paths.

  d. Accounts:
  Select the following top-accounts:
  
  … and expand the sub-trees for these accounts until the lowest (base) level. Make sure that you do not forget any account. For example CashFlow:

  e. Custom 1 members:
  Select all members, except for the [None]-member in the root:

  f. Custom 2 members:
  Select all members, except for the [None]-member in the root:

  g. Custom 3 members:
  Select all members, except for the [None]-member in the root:

  h. Custom 4 members:
  Select all members, except for the [None]-member in the root:

27. Press the Save button to keep the current selections.

Scenario Mappings

28. Go to the Scenario Mappings tab. Each selected HFM scenario must be split into (mapped to) a Category, a Rate and a Version. The members for each of these Cockpit dimensions can be maintained within the Design Studio. A sample set (sufficient for our example) is delivered with the tool:
  Category:
  

  Rate:
  
A Rate can be used to express a Category in an alternative Exchange Rate. For an HFM Scenario called 'BudgetAtActualRate' we typically use the combination Category = Budget, Rate =  Budget Rate.
  V'ersion:

  
A Version can be used to specify the version of a scenario. E.g., you can have version 1 of a Forecast.

29. To map / split the selected HFM Scenarios go to the Mapping tab:
  

Initially, none of the selected Scenarios is mapped. Create the mappings and make sure that the result looks like:

(Before you save the mappings, always click on an other row. E.g. after finishing the mapping for Forecaast, click in the Actual row.)

Custom Dimension Mappings

30. Go to the Custom Dimension Mappings tab. In the CXO Cockpit, we map the 4 Custom dimensions to tangible (Analytical) dimensions like Product, Customer, etc. This sometimes implies splitting one Custom dimension into two or even more Analytical dimensions.

31. An Analytical dimension is always based on either the root-level node or the level-2 nodes of a Custom dimension. Example: mapping of the Custom 1 dimension:
  a. Select 1 in the Custom column (click in the cell and then select 1 from the selector)
  

  b. Click twice in the Node column
  
  and then click on the member we want to map (‘TotalProducts’)

  c. Enter ‘Product’ in the Cockpit Dimension column

  d. Press Save. The remaining columns will be filled automatically with default values.

32. Do this for each of the Custom dimensions. Note that Custom 3 is split into 2 Analytical Dimensions. Make sure that – after saving – the final result looks exactly like:  

Note that the Flow dimension is a pre-defined dimension Analytical dimension in the CXO-Cockpit. By typing the exact word 'Flow' the technical dimension FLO (see last column) will be used. 

Now the ETL (Extraction, Transformation and Load) process is completely defined and we can start the actual data-extraction

Data Extraction

33. Again select the last tab:
  

34. Now we select ‘Data’ and press the ‘Start Extraction’ button.

35. Check the progress by repeatedly pressing the Show Progress button:
  

36. Wait until message:
  
  appears. Now the extraction is finished and the OLAP database can be processed.

37. Process the OLAP database by pressing the ‘Process OLAP db’ button. This will replace the sample content of the cube by the content of the HFM application. Also the progress of this process can be followed by pressing the Show Progress button.

Now the backend is ready for further creating the frontend application.