CXO Cockpit Reporting Suite Documentation - Recent changes [en]

File:HFM Client Components.png

Aplaisier — Mon, 14 May 2012 12:38:18 GMT

deleted "[[File:HFM Client Components.png]]" Not used anymore

New page

Installation Prerequisites

Aplaisier — Mon, 14 May 2012 12:31:23 GMT

CXO-Cockpit Server Requirements:

← Older revision		Revision as of 12:31, 14 May 2012
(3 intermediate revisions not shown)
Line 3:		Line 3:
	This chapter is intended to cover the requirements needed prior to the installation of the CXO-Cockpit.		This chapter is intended to cover the requirements needed prior to the installation of the CXO-Cockpit.

-	For Oracle Hyperion Financial Management, please download the following [http://lib.cxo-cockpit.com/wiki/images/3/3c/Preparations_CXO-Cockpit_on_HFM.zip document ]and fill-in all the details.	+	For Oracle Hyperion Financial Management, please download the following [http://lib.cxo-cockpit.com/wiki/images/3/3c/Preparations_CXO-Cockpit_on_HFM.zip document ] and fill-in all the details.

	For Hyperion Enterprise, download the following [http://lib.cxo-cockpit.com/wiki/images/e/e0/Preparations_CXO-Cockpit_on_Hyperion_Enterprise.zip document]		For Hyperion Enterprise, download the following [http://lib.cxo-cockpit.com/wiki/images/e/e0/Preparations_CXO-Cockpit_on_Hyperion_Enterprise.zip document]
Line 10:		Line 10:

	For Essbase, download the following [http://lib.cxo-cockpit.com/wiki/images/c/c9/Preparations_CXO-Cockpit_on_Essbase.zip document]		For Essbase, download the following [http://lib.cxo-cockpit.com/wiki/images/c/c9/Preparations_CXO-Cockpit_on_Essbase.zip document]
-
-	~~== Hardware Requirements ==~~
-
-	~~The default requirements of an individual server should have the following specifications:~~
-
-	*'''x86 or x64 CPU'''(s)<br>
-	*'''2 GB RAM''' (4 GB is preferred)
-	*'''25GB disk space''' free (depends on the amount of data)
-
-	~~''Note: VMware server instances are supported''~~
-
-	~~== Operating System<br> ==~~
-
-	~~The server should run either a 32-bit or 64-bit version of '''Windows Server''':~~
-
-	*'''Microsoft Windows Server 2003 (SP1 or higher)'''
-	*'''Microsoft Windows Server 2008'''
-
-	The default configuration is applicable for single server installations of up to 50 concurrent users. For multiple-server configurations or configurations supporting more than 50 concurrent users, we provide customer specific recommendations. The CXO-Cockpit server can also be configured as a Virtual Server (VM Ware).
-
-	~~The CXO-Cockpit also supports LDAP. Alternatively it can use its own user repository to authenticate users.~~
-
-	''NOTE: Some older versions of HFM (version 4, System 9, EPM 11.1.1.3) are not compatible with Windows 2008. Since for HFM the client tools must be installed on the CXO-Cockpit application server, Windows 2008 cannot be used in combination with these versions of HFM.''
-
-	~~== SQL Server ==~~
-
-	The CXO-Cockpit uses Microsoft SQL Server for the [[CXO Repository]] and for storing and transforming the data extractions from HFM or Hyperion Enterprise (if applicable) and SQL Server Analysis Services (not for Essbase customers). We can use any existing database server, or install SQL Server on the same machine as the CXO-Cockpit itself.
-
-	~~We require:~~
-
-	*'''Microsoft SQL Server 2005''' (SP2 or higher) '''or 2008''' (Standard Edition or Enterprise Edition)
-	*'''Microsoft Analysis Services 2005''' (SP2 or higher) '''or 2008 '''(not required for Essbase)
-
-	~~There are no requirements with respect to Collation.~~
-
-	~~== Client tools for Hyperion-Oracle products ==~~
-
-	[[Image:HFM Client Components.png\|thumb\|right\|200px]] The following source systems require specific software on the CXO-Cockpit web server (this only applies for those source systems that are used for CXO-Cockpit):
-
-	~~=== Hyperion Financial Management ===~~
-
-	~~Install the '''HFM client components''' as shown in image on the right:~~
-
-	Once the client is installed, the HFM cluster but be registered. Futhermore, to be able to logon to HFM and to extract data a native (non-domain) HFM account is required. Read more about user accounts and permissions. <br>
-
-	~~=== Hyperion Enterprise ===~~
-
-	There is no requirement for client tools. However, during an implementation it can be convenient to have '''Enterprise client '''available for creating extracts. For scheduled extracts '''Hyperion Autopilot''' is required.
-
-	~~=== Hyperion Essbase ===~~
-
-	~~The '''Essbase client''' is required.<br>~~
-
-	~~== Other Components ==~~
-
-	~~The following components are required:~~
-
-	*'''Microsoft Internet Information Services (IIS) 6.0 or 7.0'''
-	*'''Microsoft .NET 3.5 SP1 Framework''' (see: [http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en])
-	*(Not required for Essbase) If Analysis Services is running / will be installed on another server than the CXO-Cockpit server:
-	**'''Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider''' (see: [http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en]) or, in case of Analysis Services 2008:
-	**'''Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider''' (see:[http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en])
-	*(Required only for HFM live synchronization if an Oracle database is used as a HFM datastore) '''Oracle Data Provider for .NET''' (see: [http://www.oracle.com/technetwork/topics/dotnet/index-085163.html http://www.oracle.com/technetwork/topics/dotnet/index-085163.html]). Assembly "Oracle.DataAccess" must be present in GAC, normal installation procedure places the assembly in GAC by default.
-
-	~~== <br>ASP.net ==~~
-
-	~~[[Image:Installation Prerequisitesimage003.jpg\|thumb\|right\|250px]] Check the Web Service Extensions of IIS and make sure that ASP.NET has status 'Allowed': ~~
-
-	~~<br>~~
-
-	~~<br><br><br><br>~~
-
-	~~[[Image:Installation Prerequisitesimage004.jpg\|thumb\|right\|150px]]  If ASP.NET is not included in this list, then you first have to run the .NET registration utility:~~
-
-	~~== <br><br>User accounts and permissions ==~~
-
-	~~=== Service Account<br> ===~~
-
-	To enable communication between CXO-Cockpit components and the Database Server, a Domain (or local machine in case of a combined CXO-Cockpit / Database Server) Service Account is required. This account does not require any special domain privileges.The Service Account is used to run CXO Cockpit Web Site, CXO Viewer Web Site, Print Server, HFM Integration service, CXO-Cockpit Agent Service.
-
-	The configuration of the Web Server is done automatically during the installation procedure. The content of the section Web Server is for troubleshooting only. The configuration security of the Analysis Server is a manual step (see section below).
-
-	~~==== Web Server (troubleshooting only) ====~~
-
-	~~#Open "Computer Management" and under "Local Users and Groups" - "Groups" add the service account to the relevant built-in group used by Internet Information Services:~~
-	~~#*Windows Server 2003 - IIS_WPG~~
-	~~#*Windows Server 2008 - IIS_IUSRS~~
-	#Open "Internet Information Services (IIS) Manager" and under "Application Pools" edit the properties of both the CXOCockpit and CXOViewer application pools. Modify the "Identity" to use the service account. (see thumbnail "IIS AppPool Identity")
-	#Open "Computer Management" and under "Services and Applications" - "Services" find the edit the properties of the "CXO-Cockpit Storyboard Export" service and under the "Log On" tab configure the service to logon using the service account.
-
-	~~<gallery caption="Screenshots">~~
-	~~Image:WindowsServer2003 ComputerManagement Groups.png\|Windows Server 2003 (IIS_WPG)~~
-	~~Image:WindowsServer2008 ComputerManagement Groups.png\|Windows Server 2008 (IIS_IUSRS)~~
-	~~Image:WindowsServer2003 IISManager ApplicationPool Properties Identity.png\|IIS Manager Application Pool Identity~~
-	~~Image:StoryboardExportService Properties LogOnAs.png\|Storyboard Export service "Log On As"~~
-	~~</gallery>~~
-
-	~~==== Analysis Server ====~~
-
-	~~[[Image:WindowsServer2008 AnalysisServices Properties Security.png\|thumb\|125px]]~~
-
-	#Open the "SQL Server Management Studio" and connect to "Analysis Services". Edit the properties of the server and under the "Security" section add the service account to "NT Users and Groups" (SQL Server 2005) or "Server administrators" (SQL Server 2008).
-	#*'''NOTE''': Users who want to process the Analysis Services cube using the Design Studio installed on their PC will have to have there domain account added to this same location. (see thumbnail "MS OLAP Properties")
-
-	~~=== Microsoft SQL Server Account ===~~
-
-	~~To connect to SQL Server, an account is required with db-creator role. If Hyperion Financial Management is used as a backend system, this should be a native SQL account.~~
-
-	~~=== HFM Account<br> ===~~
-
-	If Hyperion Financial Management is used as a backend system we require a native (non-domain) HFM account. The account must have permissions to read all data and meta-data and to run Extended Analytics. <br>
-
-	~~= End-user Client PC =~~
-
-	~~To take full-advantage of all features of the CXO-Cockpit, the end-user should have access to a desktop PC running the following:~~
-
-	*Any market leading web browsers, for a full overview click [[Which browsers are supported by CXO-Cockpit?\|here]].
-	*For the export features:
-	**'''Microsoft Excel 2003''' and '''PowerPoint 2003''' or higher<br>
-	**'''PDF Viewer''' (ie: Adobe Reader)
-	*'''Microsoft Excel 2007 or 2010''' for [[CXO-Excel Add-In\|Excel Add-In]]<br>
-
-	~~<br>~~
-
-	~~<br>~~

	[[Category:Installation_Documentation]]		[[Category:Installation_Documentation]]

Free Model

Wouter born — Mon, 14 May 2012 11:46:06 GMT

← Older revision		Revision as of 11:46, 14 May 2012
Line 1:		Line 1:
-	A free model is an [[Source System]] that is not connected throug an [[Integration_Adapters\|Integration Adapter]]. A free model is typicallly an OLAP system that alread exists before CXO-Cockpit was implemented.	+	A free model is a [[Source System]] that is not connected throug an [[Integration_Adapters\|Integration Adapter]]. A free model is typicallly an OLAP system that alread exists before CXO-Cockpit was implemented.

	A free model has the following characteristics:		A free model has the following characteristics:

Pie Chart Control

Wouter born — Fri, 11 May 2012 15:50:36 GMT

← Older revision		Revision as of 15:50, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~	+	== Introduction ==
-		+
-	== Introduction ~~(Upward of version 4.2)~~ ==	+

	Pie Chart controls can be used as chart on in the [[Free Format Template]] and are used to analyze the		Pie Chart controls can be used as chart on in the [[Free Format Template]] and are used to analyze the

New Reporting Period

Wouter born — Fri, 11 May 2012 15:50:02 GMT

← Older revision		Revision as of 15:50, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~
-
	=== Introduction ===		=== Introduction ===

-	~~ ~~The New Reporting Period Wizard guides you ~~throughthe~~ process of setting a new Reporting Period.	+	The New Reporting Period Wizard guides you through the process of setting a new Reporting Period.<br>
-		+
-	<br>	+

	=== Set New Reporting Period ===		=== Set New Reporting Period ===

Fact Database

Wouter born — Fri, 11 May 2012 15:49:08 GMT

← Older revision		Revision as of 15:49, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~	+	The fact database is used as a key database for [[Source System\|Source Systems]] that are connected through an [[Integration Adapters\|Integration Adapter]].

-	[[Category:Installation_Documentation]]	+	The integration adapter copies or exports the data to the [[Staging Database]]. In the staging database all necesarry transformations are done and then the data is copied to the Fact Database. The fact database is the main source for the [[Microsoft_SQL_Server_Analysis_Services_(SSAS)\|SSAS]] OLAP cube.
		+
		+	[[Image:Architectureimage With Adapter.png\|300px]]<br>
		+
		+	[[Category:CXO-Cockpit_Captain_Core_Concepts]] [[Category:Source_System_Configuration]] [[Category:Installation_Documentation]]

Staging Database

Wouter born — Fri, 11 May 2012 15:45:50 GMT

← Older revision		Revision as of 15:45, 11 May 2012
(2 intermediate revisions not shown)
Line 1:		Line 1:
-	~~{{WIP}}~~	+	The staging database is used for [[Source System\|Source Systems]] that are connected through an [[Integration Adapters\|Integration Adapter]].

-	[[Category:Installation_Documentation]]	+	The integration adapter copies or exports the data to the Staging Database. In the staging database all necesarry transformations are done. After the data is transformed it is copied to the [[Fact Database\|Fact Database]].
		+
		+	[[Image:Architectureimage With Adapter.png\|300px]]<br>
		+
		+	[[Category:CXO-Cockpit_Captain_Core_Concepts]] [[Category:Source_System_Configuration]] [[Category:Installation_Documentation]]

CXO-Cockpit Reporting Suite 4.2 Release Notes

Wouter born — Fri, 11 May 2012 15:35:54 GMT

← Older revision		Revision as of 15:35, 11 May 2012
(2 intermediate revisions not shown)
Line 25:		Line 25:
	===== Pie-chart control in Generic Template =====		===== Pie-chart control in Generic Template =====

-	One of the possible components on a Generic Template is a [[~~Pie_Chart_Control~~\|Pie Chart]].	+	One of the possible components on a Generic Template is a [[Pie Chart Control\|Pie Chart]].

	===== Enable subtraction in SUM formula =====		===== Enable subtraction in SUM formula =====

-	it is now much easier to subtract columns or rows. Read more about this in the [[~~SUM_~~&~~_SUMR~~\|SUM & SUMR]] article.	+	it is now much easier to subtract columns or rows. Read more about this in the [[SUM & SUMR\|SUM & SUMR]] article.

	===== Enabling Weekly and Daily reports =====		===== Enabling Weekly and Daily reports =====
Line 35:		Line 35:
	Charts can be optimised to show up till 365 points on the X axis.		Charts can be optimised to show up till 365 points on the X axis.

-	===== Enabling Cube-Calculations in Essbase Models =====	+	===== Enabling Cube-Calculations in [[Hyperion Essbase\|Essbase]] and [[Microsoft SQL Server Analysis Services (SSAS)\|SSAS]] [[Free Model\|Free Models]] =====

-	~~this~~ is a very powerful extension because it allows complex multi-dimensional calculations without the need to change the underlying Essbase Outline.<br>	+	This is a very powerful extension because it allows complex multi-dimensional calculations without the need to change the underlying Essbase Outline. Read more about this in our [[Calculated Members]] article.<br>

Calculated Members

Wouter born — Fri, 11 May 2012 15:32:04 GMT

← Older revision		Revision as of 15:32, 11 May 2012
Line 11:		Line 11:

	== Cube Calculations ==		== Cube Calculations ==
-
-	~~=== What are Cube Calculations? ===~~
-
-	~~Cube Calculations are a powerfull way to enrich data~~
-
-	~~Cube Calculation calculations are done in CXO-Cockpit when~~
-
-	*The calculation is not done in the source system
-	*In some organizations, adding a calculation in the source system can be a very cumbersome or time consuming tasks, due to for example compliance rules.
-	*The calculation can’t be done in the source system<br>In some systems (such as HFM) the calculation options are limited (such as dynamic rules in HFM) which can’t deal with more complex or advanced rules
-	*The calculation can be done much easier or more maintenance friendly in CXO<br>In CXO we have the most powerful and maintenance friendly language (MDX) available.
-
-	~~<br>~~

	=== What are Cube Calculations Technically? ===		=== What are Cube Calculations Technically? ===

	*Cube Calculations are Performed in the OLAP Cube		*Cube Calculations are Performed in the OLAP Cube
-	*Calculated Members are stored in the OLAP Cube
	*Calculations are made on the Fly when a Report is opened		*Calculations are made on the Fly when a Report is opened
	*Cube Calculations are written in MDX		*Cube Calculations are written in MDX
		+	*Calculated Members are stored:
		+	**In the cube for [[Source_System\|Source Systems]] that are connected through an [[Integration_Adapters\|Integration Adapter]]
		+	**In CXO-Cockpit for [[Free_Model\|Free Models]], the MDX calculation is applied at the moment of executing the query

	== Attributes ==		== Attributes ==
Line 133:		Line 122:
	<br> Examples of all of these calculations are available in reports in our on-line demo environment.<br><br>In addition, the cube calculations are also often used for simple calculations such as the sum of accounts or entities.<br>		<br> Examples of all of these calculations are available in reports in our on-line demo environment.<br><br>In addition, the cube calculations are also often used for simple calculations such as the sum of accounts or entities.<br>

-	For an overview of supported MDX functions check the Microsoft website:<br>http://msdn.microsoft.com/en-us/library/ms145970.aspx	+	For an overview of supported MDX functions check the Microsoft website:<br>http://msdn.microsoft.com/en-us/library/ms145970.aspx
-		+
-		+

	[[Category:CXO-Cockpit_Building_Blocks]]		[[Category:CXO-Cockpit_Building_Blocks]]

CXO-Cockpit Reporting Suite 4.2 Release Notes

Wouter born — Fri, 11 May 2012 15:23:45 GMT

← Older revision		Revision as of 15:23, 11 May 2012
Line 29:		Line 29:
	===== Enable subtraction in SUM formula =====		===== Enable subtraction in SUM formula =====

-	it is now much easier to subtract columns or rows.	+	it is now much easier to subtract columns or rows. Read more about this in the [[SUM_&_SUMR\|SUM & SUMR]] article.

	===== Enabling Weekly and Daily reports =====		===== Enabling Weekly and Daily reports =====

SUM & SUMR

Wouter born — Fri, 11 May 2012 15:22:46 GMT

← Older revision		Revision as of 15:22, 11 May 2012
Line 7:		Line 7:
	=== SUM ===		=== SUM ===

-	(Parameter + Parameter + Parameter + etc.)<br>~~As of version 4.2 it~~ is also possible to subtract. By clicking the "+" it changes into a "-".	+	(Parameter + Parameter + Parameter + etc.)<br>It is also possible to subtract. By clicking the "+" it changes into a "-".

	<br>		<br>

CXO-Cockpit Reporting Suite 4.2 Release Notes

Wouter born — Fri, 11 May 2012 15:22:02 GMT

← Older revision		Revision as of 15:22, 11 May 2012
(One intermediate revision not shown)
Line 1:		Line 1:
-	This article contains the rlease notes of CXO-Cockpit version 4.2. For the relase notes of 4.1 see the following article:	+	This article contains the rlease notes of CXO-Cockpit version 4.2. For the relase notes of 4.1 see the following article:

	[[CXO-Cockpit Reporting Suite 4.1 Release Notes]]		[[CXO-Cockpit Reporting Suite 4.1 Release Notes]]
Line 13:		Line 13:
	===== ‘Central Top’ as dimension initialization =====		===== ‘Central Top’ as dimension initialization =====

-	Like Initial Top (which links a sub-tree of a dimension to a report and initializes the dimension to the top of that sub-tree), but without initializing the dimension. Read more about this in the [[~~Central_Top~~\|Central Top]]	+	Like Initial Top (which links a sub-tree of a dimension to a report and initializes the dimension to the top of that sub-tree), but without initializing the dimension. Read more about this in the [[Central Top\|Central Top]]

	===== Ability to switch Actual and Reference columns =====		===== Ability to switch Actual and Reference columns =====
Line 25:		Line 25:
	===== Pie-chart control in Generic Template =====		===== Pie-chart control in Generic Template =====

-	One of the possible components on a Generic Template is a Pie Chart.	+	One of the possible components on a Generic Template is a [[Pie_Chart_Control\|Pie Chart]].

	===== Enable subtraction in SUM formula =====		===== Enable subtraction in SUM formula =====

Free Format Template

Wouter born — Fri, 11 May 2012 15:21:12 GMT

← Older revision		Revision as of 15:21, 11 May 2012
Line 86:		Line 86:
	\| The Bridge shows the positive or negative contribution of a region or any analytical dimension member to the deviation between two categories for an account.		\| The Bridge shows the positive or negative contribution of a region or any analytical dimension member to the deviation between two categories for an account.
	\|-		\|-
-	\| [[Pie Chart Control\|Pie Chart]]~~ (As of V4.2)~~	+	\| [[Pie Chart Control\|Pie Chart]]
	\| Pie Chart		\| Pie Chart
	\|-		\|-

CXO-Cockpit Reporting Suite 4.2 Release Notes

Wouter born — Fri, 11 May 2012 15:18:52 GMT

← Older revision		Revision as of 15:18, 11 May 2012
Line 13:		Line 13:
	===== ‘Central Top’ as dimension initialization =====		===== ‘Central Top’ as dimension initialization =====

-	Like Initial Top (which links a sub-tree of a dimension to a report and initializes the dimension to the top of that sub-tree), but without initializing the dimension.	+	Like Initial Top (which links a sub-tree of a dimension to a report and initializes the dimension to the top of that sub-tree), but without initializing the dimension. Read more about this in the [[Central_Top\|Central Top]]

	===== Ability to switch Actual and Reference columns =====		===== Ability to switch Actual and Reference columns =====

Dimension Split

Wouter born — Fri, 11 May 2012 15:16:53 GMT

← Older revision		Revision as of 15:16, 11 May 2012
(2 intermediate revisions not shown)
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

-	A dimension split allows you to split an OLAP dimension into two or more CXO-Cockpit dimensions. Typical example of dimensions that need to be splitted are:	+	A dimension split is a concept used for [[Free_Model\|Free Models]] that allows you to split an OLAP dimension into two or more CXO-Cockpit dimensions. Typical example of dimensions that need to be splitted are:

	*A period dimension that contains both periodic and accumulated members. CXO-Cockpit requires a seperare view dimension so this dimension needs to be splitted into period and view.		*A period dimension that contains both periodic and accumulated members. CXO-Cockpit requires a seperare view dimension so this dimension needs to be splitted into period and view.
Line 8:		Line 8:
	The second example is illustrated in the following figure:		The second example is illustrated in the following figure:

-	[[Image:Dimension Split Example.png]]	+	[[Image:Dimension Split Example.png]]

	== Setup a Dimension Split ==		== Setup a Dimension Split ==
Line 21:		Line 21:
	=== Create a Dimension Split ===		=== Create a Dimension Split ===

-	In the dimension split [[Maintenance Screen]] you can simply add a new dimension split. Specify the source dimension you would like to split.	+	In the dimension split [[CXO-Design_Studio_Maintenance_Screens\|Maintenance Screen]] you can simply add a new dimension split. Specify the source dimension you would like to split.

-	[[Image:Dimension Split Main Screen.png\|400px]]	+	[[Image:Dimension Split Main Screen.png\|400px]]

	=== Setup Destination Dimensions ===		=== Setup Destination Dimensions ===
Line 33:		Line 33:
	=== Split the Members ===		=== Split the Members ===

-	Every source member can now be splitted to a member of the destination dimensions. You can decide to leave certain members unsplitted, but once 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.	+	Every source member can now be splitted to a member of the destination dimensions. You can decide to leave certain members unsplitted, 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.

-	[[Image:Dimension Split Members.png\|300px]]	+	[[Image:Dimension Split Members.png\|300px]]

	=== Map the splitted dimensions to CXO-Cockpit dimensions ===		=== Map the splitted dimensions to CXO-Cockpit dimensions ===

Free Model

Wouter born — Fri, 11 May 2012 15:14:12 GMT

New page

A free model is an [[Source System]] that is not connected throug an [[Integration_Adapters|Integration Adapter]]. A free model is typicallly an OLAP system that alread exists before CXO-Cockpit was implemented.

A free model has the following characteristics:

*It needs to match the CXO-Cockpit [[Dimension]] requirements
*If it does not match these requirements, [[Dimension Split|dimensions need to be splitted]].
*Dimensions need to [[Dimension Mapping|mapped]]
*A [[Period Frequency|Period Frequency]] table has to be setup in order for CXO-Cockpit to understand the period structure.
*[[Point of View Security Filters|Security Filters]] might need to be applied to hide irrelevant parts of the model.

<br>

[[Category:CXO-Cockpit_Captain_Core_Concepts]] [[Category:CXO-Cockpit_Source_Systems]]

Source System

Wouter born — Fri, 11 May 2012 15:04:50 GMT

← Older revision		Revision as of 15:04, 11 May 2012
Line 6:		Line 6:

	*Adapter: Source systems that require an CXO-Cockpit application adapter		*Adapter: Source systems that require an CXO-Cockpit application adapter
-	*Direct: Source systems that can queried directly with MDX	+	*Direct ([[Free Model]]): Source systems that can queried directly with MDX

	A CXO-Cockpit application always connect to at least one source system, but it can connect to more than one source system.		A CXO-Cockpit application always connect to at least one source system, but it can connect to more than one source system.
Line 36:		Line 36:
	\| Direct		\| Direct
	\|-		\|-
-	\| [[SAP BPC]]	+	\| [[SAP BPC]]
-	\| SAP BusinessObjects Planning and Consolidation.	+	\| SAP BusinessObjects Planning and Consolidation.
	\| Direct		\| Direct
	\|}		\|}

Dimension Split

Wouter born — Fri, 11 May 2012 15:03:16 GMT

← Older revision		Revision as of 15:03, 11 May 2012
(One intermediate revision not shown)
Line 12:		Line 12:
	== Setup a Dimension Split ==		== Setup a Dimension Split ==

		+	In order to setup 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 taget members of each destination dimension
		+	#Map the detination dimensions to valid CXO-Cockpit dimensions

	=== Create a Dimension Split ===		=== Create a Dimension Split ===

-	[[Image:~~Dimension_Split_Main_Screen~~.png\|400px]]	+	In the dimension split [[Maintenance Screen]] you can simply add a new dimension split. Specify the source dimension you would like to split.
		+
		+	[[Image:Dimension Split Main Screen.png\|400px]]

	=== Setup Destination Dimensions ===		=== Setup Destination Dimensions ===

-	[[Image:~~Dimension_Split_Destination_Dimension~~.png\|400px]]	+	You can add the destination dimensions. Typically these are 2 dimensions, but it is also possible to split to more then 2 dimensions.
		+
		+	[[Image:Dimension Split Destination Dimension.png\|400px]]

	=== Split the Members ===		=== Split the Members ===

-	[[Image:~~Dimension_Split_Members~~.png\|300px]]	+	Every source member can now be splitted to a member of the destination dimensions. You can decide to leave certain members unsplitted, but once 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.
		+
		+	[[Image:Dimension Split Members.png\|300px]]

-	=== Map the splitted dimensions to CXO-Cockpit dimensions ===	+	=== Map the splitted dimensions to CXO-Cockpit dimensions ===

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

		+	[[Image:Dimension Split Mapping.png\|400px]]

	[[Category:Source_System_Configuration]]		[[Category:Source_System_Configuration]]

File:Dimension Split Mapping.png

Wouter born — Fri, 11 May 2012 14:48:57 GMT

uploaded "[[File:Dimension Split Mapping.png]]"

New page

Dimension Split

Wouter born — Fri, 11 May 2012 14:41:38 GMT

← Older revision		Revision as of 14:41, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~
-
	== Introduction ==		== Introduction ==

Line 10:		Line 8:
	The second example is illustrated in the following figure:		The second example is illustrated in the following figure:

-	[[Image:~~Dimension_Split_Example~~.png]]	+	[[Image:Dimension Split Example.png]]
		+
		+	== Setup a Dimension Split ==

-	~~== Setup a Dimension Split ==~~

-	~~=== Create a Dimension Split ===~~

-	=== ~~Setup Destination Dimensions~~ ===	+	=== Create a Dimension Split ===

-	~~=== Split the Members ===~~	+	[[Image:Dimension_Split_Main_Screen.png\|400px]]

-	== ~~Splitting & Mapping~~ ==	+	=== Setup Destination Dimensions ===

		+	[[Image:Dimension_Split_Destination_Dimension.png\|400px]]

		+	=== Split the Members ===

		+	[[Image:Dimension_Split_Members.png\|300px]]

		+	=== Map the splitted dimensions to CXO-Cockpit dimensions ===



	[[Category:Source_System_Configuration]]		[[Category:Source_System_Configuration]]

File:Dimension Split Main Screen.png

Wouter born — Fri, 11 May 2012 14:35:54 GMT

uploaded "[[File:Dimension Split Main Screen.png]]"

New page

Dimension Split

Wouter born — Fri, 11 May 2012 14:34:15 GMT

Introduction:

← Older revision		Revision as of 14:34, 11 May 2012
Line 1:		Line 1:
	{{WIP}}		{{WIP}}

-	== Introduction ==	+	== Introduction ==

-	A dimension split allows you to split an OLAP dimension into two or more CXO-Cockpit dimensions. Typical example of dimensions that need to be splitted are:	+	A dimension split allows you to split an OLAP dimension into two or more CXO-Cockpit dimensions. Typical example of dimensions that need to be splitted are:

-	*A period dimension that contains both periodic and accumulated members. CXO-Cockpit requires a seperare view dimension so this dimension needs to be splitted into period and view.	+	*A period dimension that contains both periodic and accumulated members. CXO-Cockpit requires a seperare view dimension so this dimension needs to be splitted into period and view.
	*A time dimension that contains years and months. CXO-Cockpit requires these dimension sperate so this time dimension should splitted into period and year.		*A time dimension that contains years and months. CXO-Cockpit requires these dimension sperate so this time dimension should splitted into period and year.
		+
		+	The second example is illustrated in the following figure:
		+
		+	[[Image:Dimension_Split_Example.png]]
		+
		+	== Setup a Dimension Split ==
		+
		+	=== Create a Dimension Split ===
		+
		+	=== Setup Destination Dimensions ===
		+
		+	=== Split the Members ===
		+
		+	== Splitting & Mapping ==
		+
		+
		+
		+



	[[Category:Source_System_Configuration]]		[[Category:Source_System_Configuration]]

File:Dimension Split Example.png

Wouter born — Fri, 11 May 2012 14:05:25 GMT

uploaded "[[File:Dimension Split Example.png]]"

New page

Dimension Split

Wouter born — Fri, 11 May 2012 13:24:25 GMT

← Older revision		Revision as of 13:24, 11 May 2012
Line 1:		Line 1:
-	{{WIP}}	+	{{WIP}}

-	[[Category:~~Source System Configuration~~]]	+	== Introduction ==
		+
		+	A dimension split allows you to split an OLAP dimension into two or more CXO-Cockpit dimensions. Typical example of dimensions that need to be splitted are:
		+
		+	*A period dimension that contains both periodic and accumulated members. CXO-Cockpit requires a seperare view dimension so this dimension needs to be splitted into period and view.
		+	*A time dimension that contains years and months. CXO-Cockpit requires these dimension sperate so this time dimension should splitted into period and year.
		+
		+
		+
		+	[[Category:Source_System_Configuration]]

VAR

Wouter born — Fri, 11 May 2012 13:12:35 GMT

← Older revision		Revision as of 13:12, 11 May 2012
(One intermediate revision not shown)
Line 1:		Line 1:
-	~~{{WIP}}~~	+	== Introduction ==
-		+
-	== Introduction ==	+

	The VAR formula allows you to Calculate the variance of two values. The Variance can be expressed as an absolute number or as a relative value.		The VAR formula allows you to Calculate the variance of two values. The Variance can be expressed as an absolute number or as a relative value.
Line 27:		Line 25:
	[[Image:CXO-Cockpit - Design Studio - Create Formula - Report - VAR.png]]		[[Image:CXO-Cockpit - Design Studio - Create Formula - Report - VAR.png]]

-	[[Category:CXO-Cockpit_Building_Blocks~~]] [[Category:4.2_Functionality~~]]	+	[[Category:CXO-Cockpit_Building_Blocks]]

SUM & SUMR

Wouter born — Fri, 11 May 2012 13:11:23 GMT

← Older revision		Revision as of 13:11, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~
-
	== Introduction ==		== Introduction ==

Line 33:		Line 31:
	[[Image:CXO-Cockpit - Design Studio - Create Formula - Report - SUM.png]]		[[Image:CXO-Cockpit - Design Studio - Create Formula - Report - SUM.png]]

-	[[Category:CXO-Cockpit_Building_Blocks~~]][[Category:4.2_Functionality~~]]	+	[[Category:CXO-Cockpit_Building_Blocks]]

Rows List

Wouter born — Fri, 11 May 2012 13:10:29 GMT

← Older revision		Revision as of 13:10, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~
-
	== Introduction ==		== Introduction ==

Line 96:		Line 94:
	\|}		\|}

-	[[Category:CXO-Cockpit_Building_Blocks~~]] [[Category:4.2_Functionality~~]]	+	[[Category:CXO-Cockpit_Building_Blocks]]

Report Dimensions

Wouter born — Fri, 11 May 2012 13:09:58 GMT

← Older revision		Revision as of 13:09, 11 May 2012
(One intermediate revision not shown)
Line 57:		Line 57:

	*Central: no specific value is specified and the value from a previous report is used. This is usually applied to the Entity, Year and Period dimension: when you selected a specific member for these dimensions on a previous report, you want to use these selections also on the current report		*Central: no specific value is specified and the value from a previous report is used. This is usually applied to the Entity, Year and Period dimension: when you selected a specific member for these dimensions on a previous report, you want to use these selections also on the current report
-	*[[Central Top]]: with Central Top you can set a different node as Top Node. (Navigation is like "Central")	+	*[[Central Top]]: with Central Top you can set a different node as Top Node. (Navigation is like "Central")
	*Initial: irrespective of the member selected in a previous report, the dimension is initialized to the specified member.		*Initial: irrespective of the member selected in a previous report, the dimension is initialized to the specified member.
	*[[Initial Top]]: with Initial Top you can set a different node as Top Node. (Navigation is like " Initial")		*[[Initial Top]]: with Initial Top you can set a different node as Top Node. (Navigation is like " Initial")
Line 77:		Line 77:
	\|-		\|-
	\| Narrative Key		\| Narrative Key
-	\| The narrative key defines the if this dimension is used to store the [[~~POV comments~~\|POV comments]]. If the entity, period and year dimensions are checked, this means that you see different comments for every entity, period and year combination. Normally you check the narrative key field for every dimension that has a POV Order higher than 0. An exception could be the currency/value dimension which can be part of the POV but does not require specific comments for every different currency.	+	\| The narrative key defines the if this dimension is used to store the [[Comments_and_Narratives#POV_Comments\|POV comments]]. If the entity, period and year dimensions are checked, this means that you see different comments for every entity, period and year combination. Normally you check the narrative key field for every dimension that has a POV Order higher than 0. An exception could be the currency/value dimension which can be part of the POV but does not require specific comments for every different currency.
	\|}		\|}

-		+	<br>

-	~~== Tips and Tricks ==~~	+	[[Category:Report_Configuration]]
-		+
-	*[[Recommendation: don´t change the narrative keys other than for very specific cases to avoid loosing existing narratives]]	+
-		+
-	[[Category:Report_Configuration~~]][[Category:4.2 Functionality~~]]	+

Generic Report Parameters

Wouter born — Fri, 11 May 2012 13:08:12 GMT

← Older revision		Revision as of 13:08, 11 May 2012
Line 32:		Line 32:
	\| Allows you to create a custom footer used to indicate the scaling of the numbers within the report eg amounts in '000 thousands. List of used tokens: [PREC], [SCALE] (equals to [SCALE].Text), [SCALE].Number. Since this parameter is a Dynamic Label, you can also include information from other dimensions. If you enter 'Amounts x [SCALE].Number [VAL]' you will get something like 'Amounts x 1000 EUR'.		\| Allows you to create a custom footer used to indicate the scaling of the numbers within the report eg amounts in '000 thousands. List of used tokens: [PREC], [SCALE] (equals to [SCALE].Text), [SCALE].Number. Since this parameter is a Dynamic Label, you can also include information from other dimensions. If you enter 'Amounts x [SCALE].Number [VAL]' you will get something like 'Amounts x 1000 EUR'.
	\|-		\|-
-	\| 5. Reference Category Position (As of V4.2)	+	\| 5. Reference Category Position (As of V4.2)
	\| Left/Right		\| Left/Right
	\| Mandatory		\| Mandatory
Line 42:		Line 42:
	*[[How can I configure my report to use quarters instead of months?]]		*[[How can I configure my report to use quarters instead of months?]]

-	[[Category:Report_Configuration~~]] [[Category:4.2_Functionality~~]]	+	[[Category:Report_Configuration]]

Central Top

Wouter born — Fri, 11 May 2012 13:07:40 GMT

← Older revision		Revision as of 13:07, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~	+	Central Top is a possible value of the [[Report Dimensions\|Report Dimension]] Initialization . It lets you choose a node to be the top node. When you navigate to this report, the view for this dimension is inherited from the previous view. (Unless the previous member isn't part of the selected tree)
-		+
-	~~=== (Upward of version 4.2) ===~~	+
-		+
-	Central Top is a possible value of the [[Report Dimensions\|Report Dimension]] Initialization . It lets you choose a node to be the top node. When you navigate to this report, the view for this dimension is inherited from the previous view. (Unless the previous member isn't part of the selected tree)	+

	Example:		Example:
Line 13:		Line 9:
	[[Image:CXO-Cockpit - Picture - Europe Hier.png\|200px]]		[[Image:CXO-Cockpit - Picture - Europe Hier.png\|200px]]

-	[[Category:Report_Configuration~~]] [[Category:4.2_Functionality~~]]	+	[[Category:Report_Configuration]]

SAP BPC

Wouter born — Fri, 11 May 2012 13:02:44 GMT

← Older revision		Revision as of 13:02, 11 May 2012
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

-	~~In case of a free OLAP source the SSAS OLAP~~ connector creates a direct connection to SSAS.The following architecture picture shows the system components:	+	The SAP BPC connector creates a direct connection to the SAP BPC SSAS cube.The following architecture picture shows the system components:

-	[[Image:~~Architectureimage001~~.png\|300px]]	+	[[Image:Architectureimage_SAPBPC.png\|300px]]

	<br>		<br>
Line 9:		Line 9:
	=== MDX ===		=== MDX ===

-	This connector generates inernally MDX queries to retrieve the data from ~~Essbase~~. Read more on MDX trouble shooting here: [[Turn on MDX Logging to investigate data or performance issues]]	+	This connector generates inernally MDX queries to retrieve the data from SAP BPC. Read more on MDX trouble shooting here: [[Turn on MDX Logging to investigate data or performance issues]]

	== Connectivity ==		== Connectivity ==

-	The connection to ~~SSAS~~ is managed in the [[System Settings]] specify the following fields:	+	The connection to SAP BPC is managed in the [[System Settings]] specify the following fields:

-	[[Image:~~OLAP Conenction~~ - ~~SSAS~~.png]]	+	[[Image:OLAP_Conenction_-_SAPBPC.png]]

	*Microsoft Analysis Server: the name or IP address of the SSAS server		*Microsoft Analysis Server: the name or IP address of the SSAS server
Line 24:		Line 24:
	Use the check button to check if the connection can be made.		Use the check button to check if the connection can be made.

-	== Configure CXO-Cockpit to run on ~~SSAS as a free model~~ ==	+	== Configure CXO-Cockpit to run on SAP BPC ==

	In order to succesfully run CXO-Cockpit on an SSAS application the following additional configuration is required.		In order to succesfully run CXO-Cockpit on an SSAS application the following additional configuration is required.

File:OLAP Conenction - SAPBPC.png

Wouter born — Fri, 11 May 2012 13:01:58 GMT

uploaded "[[File:OLAP Conenction - SAPBPC.png]]"

New page

SAP BPC

Wouter born — Fri, 11 May 2012 12:47:58 GMT

← Older revision		Revision as of 12:47, 11 May 2012
Line 1:		Line 1:
-	~~{{WIP}}~~	+	== Introduction ==
		+
		+	In case of a free OLAP source the SSAS OLAP connector creates a direct connection to SSAS.The following architecture picture shows the system components:
		+
		+	[[Image:Architectureimage001.png\|300px]]
		+
		+	<br>
		+
		+	=== MDX ===
		+
		+	This connector generates inernally MDX queries to retrieve the data from Essbase. Read more on MDX trouble shooting here: [[Turn on MDX Logging to investigate data or performance issues]]
		+
		+	== Connectivity ==
		+
		+	The connection to SSAS is managed in the [[System Settings]] specify the following fields:
		+
		+	[[Image:OLAP Conenction - SSAS.png]]
		+
		+	*Microsoft Analysis Server: the name or IP address of the SSAS server
		+	*Database: The name of the SSAS database
		+	*Cube: The name of the SSAS cube
		+	*Username & Password: SSAS can only be accessed using windows authentication. For the design studio the windows account of the current logged on user will be used. The website will use the account as specified in the application pool. The services will use the secvice acccount.<br>
		+
		+	Use the check button to check if the connection can be made.
		+
		+	== Configure CXO-Cockpit to run on SSAS as a free model ==
		+
		+	In order to succesfully run CXO-Cockpit on an SSAS application the following additional configuration is required.
		+
		+	*[[Dimension Mapping\|Dimension Mapping]]: all of the [[Dimension#CXO_Core_Dimensions\|CXO Core Dimensions]] need to be mapped
		+	*Sometimes it is required to use [[Dimension Split\|Dimension Splits]] in order to get all required dimensions. Specify dimension splits first then map the dimensions.
		+	*Set the [[Period Frequency\|Period Frequencies]] table
		+	*Correct any [[Dimension Variable\|Dimension Variable]] errors

	[[Category:CXO-Cockpit_Source_Systems]]		[[Category:CXO-Cockpit_Source_Systems]]