# OLAP # OLAP example We have a solution - Change management \[changemanagement\] The solution contains the following lookup fields - Scope \[TYPE\] - Type \[TASKTYPE\] It also has some decimal values - Estimate \[ESTIMATE\] - Realized \[REALIZED\] In our reporting we want to see distributions by - A period hierarchy: Year / Quarter / Month - Categories by Scope, Type and Status ## Setting up the cube A new OLAP cube is set up in: "Integration" > "OLAP cubes" > "Add" ### Basic information - Name display: sample1 - Cube header: Report sample1 ### Cube definition ("Cube Schema XML") For further help to designing schemas please refer to the following ressources - [http://mondrian.pentaho.com/documentation/schema.php](http://mondrian.pentaho.com/documentation/schema.php) ```xml

Year(CreatedAt) YEAR Quarter(CreatedAt) Quarter Month(CreatedAt) Month ``` ### MDX query ("Cube Query MDX") For further help to designing queries please refer to the following ressources - [http://technet.microsoft.com/en-us/library/ms145971.aspx](http://technet.microsoft.com/en-us/library/ms145971.aspx) ```mysql SELECT NON EMPTY {([Measures].[Estimate],[Measures].[Realized])} ON COLUMNS, NON EMPTY {([Period],[Type],[Status])} ON ROWS FROM [sample1cube] ``` ## Results The cube is acccesed via this URL (or press "test" form the OLAP overview) [http://YOUR\_DOMAIN/TempusServa/olapview.jsp?query=sample1](http://your_domain/TempusServa/olapview.jsp?query=sample1) [![image.png](https://docs.tsnocode.com/uploads/images/gallery/2025-04/scaled-1680-/DT1uGurX8iq4UTEA-image.png)](https://docs.tsnocode.com/uploads/images/gallery/2025-04/DT1uGurX8iq4UTEA-image.png) [![image.png](https://docs.tsnocode.com/uploads/images/gallery/2025-04/scaled-1680-/RdSDIs4HYtgV3pWL-image.png)](https://docs.tsnocode.com/uploads/images/gallery/2025-04/RdSDIs4HYtgV3pWL-image.png) # Schema cheatsheet ## Introduction The below paragraphs contains sample snippets for your OLAP schema. Precise documentation on how to define a schema, can be found at: [http://mondrian.pentaho.com/documentation/schema.php](http://mondrian.pentaho.com/documentation/schema.php) ## Schema structure overview - Table (one): - Structure: The centre table containing the measures (FACT table) - OLAP cube: *Not displayed* - Dimensions (many) - Structure: Related tables or groupable values (FACT table relations) - OLAP cube: Columns/row "headers" in the cube - Measures (many) - Structure: Values found in the centre table (FACT table values) - OLAP cube: Numbers to be displayed in the table cells ## Defining dimensions for related values ### Standard lookup value The cube schema below only needs adjustment for the system name of the lookup field. **Structure**

Solution as displayed	"Sample solution" : "Category" = xxx
Solution system names	sample : CATEGORY = xxx
Database table names	data\_sample : CATEGORY = xxx

**Data model** - data\_sample - CATEGORY: Field containing the lookup value **Cube schema** ```xml ... ... ``` ### Simple choice value The cube schema below only needs adjustment for the system name of the lookup field. **Structure**

Solution as displayed	"Sample solution" : "My choice" = xxx
Solution system names	sample : CHOICE = xxx
Database table names	data\_sample : CHOICE = xxx

**Data model** - data\_sample - CHOICE: Field containing the lookup value **Cube schema** ```xml ... ... ``` ### Standard record Status The cube schema below can be copied directly without modification: The status properties and tablenames are allways the same. **Structure**

Solution as displayed	"Sample solution" : "Status" = xxx
Solution system names	sample : "StatusID" = xxx
Database table names	data\_sample "StatusID" = xxx

**Data model** - data\_sample - StatusID: Field containing status reference (allways the same) **Cube schema** ```xml ... ... ``` ## Defining dimensions for related records ### **Structure**

Solutions as displayed	"Some child" : "Parent" -> "Father or mother"
Solution system names	child : PARENT -> parent
Database table names	data\_child : PARENT -> data\_parent

**Data model** - data\_child - PARENT: Key to the "parent" solution - data\_parent - GRANDPARENT: Key to the "grandparent" solution - PARENTNAME: Descriptive field **Cube schema** ```xml ... ... ``` ### Note that the schemas for multi join tables are written from "inside out", that might seem counterintuitive i relation to what you want to display in the cube later. **Structure**

Solutions as displayed	"Some child" : "Parent" -> "Father or mother" : "Grand parent" -> "Grandma and Grandpa's"
Solution system names	child : PARENT -> parent : GRANDPARENT -> grandparent
Database table names	data\_child : PARENT -> data\_parent : GRANDPARENT -> data\_grandparent

**Data model** - data\_child - PARENT: Key field pointing to the "parent" solution - data\_parent - GRANDPARENT: Key field pointing to the "grandparent" solution - PARENTNAME: Descriptive field - data\_grandparent - GRANDPARENTNAME: Descriptive field **Cube schema** ```xml ... ... ``` ## Defining dimensions for inline values ### Text values **Cube schema** ```xml ... ... ``` ### Year/integer values **Cube schema** ```xml ... ... ``` ### Date / datetime values **Cube schema** ```xml ... Year(CreatedAt) YEAR Month(CreatedAt) Month ... ``` ### Enumeration values **Cube schema** ```xml ... 1 High 2 Medium ... more values ... ... ``` ## Defining measures ### Normal values Measures are allways numeric values, that can be agggated to higher levels (the levels in the dimensions)

Type	Aggregator	Examples
Sums	SUM	Time spent, costs
Average	AVG	Process time

**Cube schema** ### Calculated values # Analyse Activity User activity will display an OLAP cube for **changes and updates** to certain solutions. Changes are defined by updates to the underlying record. ## How to activate this feature - User must have the **Business analyst** property set - The solution must have **Activity monitoring** property set - The service **OLAP Activity** must be active # Analyse Flowsteps User activity will display an OLAP cube for **flow in each process step** for certain solutions. The total flow time is defined as the time span between entry and exit point in time for each flow step (status). Furthermore each status can have targets for good performance defined: - Goal: Expected process time in this step - Tolerance: Acceptable process time in this step ## How to activate this feature - User must have the **Business analyst** property set - The solution must have **Activity monitoring** property set - The service **OLAP Flowsteps** must be active # Analyse Flowtotal User activity will display an OLAP cube for **total flow** time to certain solutions. The total flow time is defined as the time span between creation and point in time where a final status i reached. Furthermore each solution can have targets for good performance defined: - Goal: Expected total process time - Tolerance: Acceptable total process time ## How to activate this feature - User must have the **Business analyst** property set - The solution must have **Activity monitoring** property set - The service **OLAP Flow total** must be active