Introduction

A Dimension Split is a concept used for Free Models that allows you to split an OLAP dimension into two or more CXO dimensions. Typical examples of dimensions that need to be split are:

A Period dimension that contains both periodic and accumulated members. CXO requires a separate View dimension, so this dimension should be split into Period and View.
A Time dimension that contains years and months. CXO requires a separate Year dimension, so this dimension should be split into Period and Year.

CONTENT

The second example is illustrated in the following figure:

Set up a Dimension Split

In order to set up a valid Dimension Split you will have to complete 4 steps

Create a new dimension split based on a dimension of the source system
Add the destination dimensions
Split the source members to target members of each destination dimension
Map the destination dimensions to valid CXO dimensions

Create a Dimension Split

The Dimension Splits can be opened through the System Settings in the Design Studio. In the dimension split /wiki/spaces/CXO/pages/2806776565 you can simply add a new dimension split. Specify the source dimension you would like to split.

Setup Destination Dimensions

You can add the destination dimensions. Typically these are 2 dimensions, but it is also possible to split to more then 2 dimensions.

Split the Members

Every source member can now be split to a member of the destination dimensions. You can decide to leave certain members unsplit, but once you specify a new member, you will need to split this member for any combination with the other dimension. For example: If you split 2008 for all period members, and you want to split 2009.Jan as well, you will have to split all period members for 2009 as well.

Map the split dimensions to CXO dimensions

Once a dimension is correctly split it can be mapped. In the example above the Time.H1 dimension was split to Year and Period. In the screenshot below you can see how the Year is mapped to the CXO dimension YER and Period is mapped to PER. Read more about mapping in the Dimension Mapping article.

Documentation