Understanding Cube Settings

Cube Settings is accessed by navigating to Maintenance > Reports > Cube Settings. There are 5 application pages that make up Cube Settings. Each of the application pages is discussed in detail below.

• Attribute Settings
• Report Settings
• Default Members
• Substitution Variables
• Custom Members

Attribute Settings

Attributes and attribute hierarchies are mapped to reporting cubes for reporting purposes. You can map attributes as either attribute hierarchies or properties, with up to ten attributes and hierarchies per Financial reporting cube and ten for the Sales reporting cube (twenty total). Attributes can be used just like dimensions (for example, sliced and diced across axes and drilled down upon).

You can add any remaining attributes (those in addition to the 10 per cube) created on dimensions as member properties. There is no limit to the number of properties that can be mapped. Attributes mapped as properties cannot be drilled upon. Properties show up as notes on a report. They can be included as mapped properties in the report setup for a Dynamic Report. When you run the report, they’re displayed.

Attribute Settings are processed in the cloud so that you can continue working while processing takes place. Once complete, you will be notified.

Attributes and Attribute Hierarchies are discussed in detail in the Hierarchy Management Admin Guide.

All default measures are enabled for selection on the Attribute Settings page so that you can map and unmap them to and from the reporting area. If you do not want to include annual salary or bonus, for example, in a Dynamic Report, you can hide them from the Measure dimension.

Report Settings

In Report settings, you can set the maximum number of Formula Exceptions (up to 999) that users can create while working on a Dynamic Report. When a Formula Exception is applied to a cell in a report, the cell value will depend on the applied exception. If the cell had any formula, the exception will even override the previous formula and use the exception created as part of the applied Formula Exception.

Based on the limit set, you can create your own number of exception formulas in Dynamic reports. This helps to perform custom calculations in each report. 

The Exceptions include invalid formulas.

See Dynamic Reports, for adding the Formula Exceptions.

Default Members

When you run a Dynamic Report, the system expects values for each dimension mapped to the cube, regardless of how users use the dimension in the report. For this reason, default values are automatically created for each dimension.

Substitution Variables

Substitution variables are used in the creation of Dynamic Reports and Report Sets. A substitution variable replaces a complex multi-dimensional expression (Rule) with a specified value. Substitution variables must be added to Report Sets as lines to be reflected in reports. Planful provides over 40 system-defined substitution variables.

The purpose of using a substitution variable is to:

• Improve report performance
• Improve Report Set maintainability
• Dynamically display report column/row headers

Description of Fields on the Substitution Variable Page

Grid Fields

Code - The name of the substitution variable as used in reporting formulas.

Reporting Area - The reporting area where the substitution variable is defined.

Dimension - The dimension where the substitution variable is defined.

Value - The value a substitution variable points to.

Derived Variables - The number of derivatives for the selected variable.

Substitution Variables Explained with Examples

A substitution variable contains a Name and Value pair. For example:

Substitution Variable Name: @CURMNTH@

Substitution Variable Value: Jan-2018

The Substitution Variable Name is replaced by its Value when the report is executed, thereby making reporting flexible. In the example above, you may create a report column using the @CURMNTH@ Substitution Variable. When the report is executed the Name is substituted by its Value (i.e. Jan-2018).

In Practice

Let's say you want to create a Rule for the following:

Prior Year Quarter 1

Prior Year Quarter 2

Prior Year Quarter 3

Prior Year Quarter 4

Q1 Prior year – Openingperiod(Ancestor(Parallelperiod(year,1,Time.CurrentMember),year))

Q2 Prior year - Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,Time.CurrentMember),year)).lead(1)

Q3 Prior year - Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,Time.CurrentMember),year)).lead(2)

Q4 Prior year - Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,Time.CurrentMember),year)).lead(3)

You can also create prior year quarters as derived variables on the @CURQTR@ substitution variable:

@PRYRQTR1@ - Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,@CURQTR@),year))

@PRYRQTR2@- Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,@CURQTR@),year)).lead(1)

@PRYRQTR3@- Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,@CURQTR@),year)).lead(2)

@PRYRQTR4@- Openingperiod(Quarter,Ancestor(Parallelperiod(year,1,@CURQTR@),year)).lead(3)

Substitution Variables can be used on any of the dimensions or attributes available and in any of the reporting areas. You cannot create a substitution variable that includes multiple dimensions, however, you can add multiple dimensions while defining static report sets. For example, if you want to define November MTD you can set the Rule to (@CURMTH@,[Measures].[MTD]) in your report set. If you want to set November for a selected department you might use the following (@CURMTH@,@CURDEPT@).

Attributes and attribute hierarchies mapped on the Attribute Settings page are available in the Financial and Scorecard Reporting Area. Attributes mapped to properties are not available.

Types of Substitution Variables

1. Standard Substitution Variables: Standard Substitution Variables point to a value, which can be updated by a Reporting Administrator using the Substitution Variable page located under the Maintenance menu. Substitution Variables can be established for any of the dimensions or attributes available in any of the reporting areas. For example, variable @CURYR@ contains the year value 2018, which internally points to the appropriate Time dimension member such as [Time].&[5045]. The value is used on column headers and the dimension member is used in MDX expressions.

2. Derived Variables: Derived Variables contain a formula which references a Substitution Variable and derives an appropriate value by evaluating the formula.

   For example, A Derived Variable named ‘@CURMTH -1@’ can:

   Reference the following Substitution Variable: @CURMTH@.

   Contains a formula, such as: @CURMTH.Lag(1).

   Will result in the month preceding the Current Month based on setup.

   At run time @CURMTH.Lag(1) is evaluated based on the value of @CURMTH@.

   Generally, the value is used for column headers and the dimension member is used in MDX expressions.

How to Use Substitution Variables?

Substitution variables are used in the creation of Dynamic Reports. A substitution variable replaces a complex multi-dimensional expression (Rule) with a specified value. Substitution variables must be added to Report Sets as lines to be reflected in reports. Planful provides over 40 system-defined substitution variables.

Here is a list of places where you can use substitution variables:

• In Rules and on Row or Column Labels and Headers
• To Dynamically Display Report Set Lines
• As an Efficient Way to Replace Formula Exceptions
• In Combination with Static Text
• To Improve Report performance by Avoiding the Use of Calculated or Measured Dimensions when Building Column Sets
• To Improve Report Performance Instead of Reporting Scenario Functionality
• To Improve Efficiency in Building Report Sets
• To Overcome Rule Limitations

As an Efficient Way to Replace Formula Exceptions

Example: To display the current period in the column header of a report, replace the column set’s line name with a substitution variable, such as @CURMTH@. When the report is run, @CURMTH@ will be replaced with the actual month name Mar-10.

In Combination with Static Text

Examples:

YTD~ @CURMTH@ will display YTD~ Jan-18

@CURYR@Actual will display 2018 Actual

To Improve Report Performance by Avoiding the Use of Calculated or Measured Dimensions when Building Column Sets

The following Report Set is commonly used:

Setting up this Report Set requires the usage of complex Rules that typically require a column set on a Calculated or Measured dimension and utilizes the Reporting scenario for the Budget column. The following table displays commonly used formulas to deliver report columns.

While the rules above deliver the expected result, they are complex. This complexity adversely impacts report performance. The same report can be set up more efficiently using Substitution Variables. The table below displays how Substitution Variables compare to the formulas in the table above.

Performance for the Report Set depicted in the table above can be improved by moving the repeated member on the Page axis. The Report Set above uses [Measures].[MTD] and [Measures].[YTD] frequently. Move one of these members to the page level. For example, use the member [Measures].[YTD] on the Page axis rather than repeating [Measures].[YTD] on the first and second lines as shown in the table below.

To improve report performance instead of reporting scenario functionality

When using reporting scenario functionality to retrieve the budget and forecast for a selected year, you might use the following rule.

StrToMember ("Scenario.&["+Time.Currentmember.properties("Budget_Id")+"]"))

While the rule above delivers the expected result, it slows report performance. A performance improvement is to use Substitution Variables as described below.

To improve efficiency in building report sets

Substitution Variables aide in the setup and maintenance of time-based Report Sets, such as Trailing 12 months, along with Budget and Forecast columns. The following example displays a Trailing 12-month Report Set:

To overcome Rule Limitations

You cannot use the same dimension on two axes simultaneously. For example, a report that requires a Report Set on the Time dimension, will not allow selection of Time dimension members at the Page level. To set up a trailing 12-month report, define the column set on either the Calculated or Measure dimension. Time should be on the Page axis. This setup does not use substitution variables so performance will not be optimal. With Substitution Variables, the report column set can be set up on the Time dimension directly and the required selections can be made using Substitution Variables, which will result in improved performance.

How to Transition Existing Reports to Use Substitution Variables?

Transition an existing report to utilize Substitution Variables to take advantage of the following benefits:

• Improve Financial report performance.
• Improve the ease and maintenance of Report Sets.
• Display the report column/row headers dynamically.
• Provide you with additional flexibility in changing report parameters.

Substitution Variables and their derivatives may be found by navigating to Maintenance > Report Administration > Cube Settings > Substitution Variables. This list displays system-defined variables, as well as any custom variables you create.

Complete the following steps to transition your existing reports to Substitution Variables:

1. Review the report and corresponding row and column set(s) in order to determine how you want to proceed. For example, if the column set is built on the measures dimension or calculated dimensions, consider how the report may be modified to use time or scenario on the column. Also, consider using Substitution Variables in column headers and row titles.

2. Make a copy of the existing report prior to beginning the transition. This copy will be modified during the transition, but you can compare the end result with the original report/report set(s) to validate data.

3. If you plan to change the dimension upon which the report set is built, you must create a new report set as it is not possible to change an existing report set to run on a different dimension. If you plan to use the same dimension for your new report set, you may copy the original report set. This copy will be modified during the transition and you can then compare the end result with the original report/report sets to validate data.

4. Modify the formulas on the Advanced Rule page from the current string to include the appropriate Substitution Variables. For example; In a rolling twelve month column set, you can remove the expression “Time.CurrentMember.lag(1)” and replace it with “@CURMTH-1@” for the column pulling the last month’s data.

5. Modify the column headers/row titles as necessary. A column previously titled using Formula Exceptions to display the appropriate month or hardcoded to fixed text can be replaced with a Substitution Variable in the column header within the column set. This header may include the Substitution Variable alone, or included with static text. For example; If the month is May, the column header within the column set may be “@CURMTH-2@” to display “March.” Or, it may be “YTD @CURMTH-2@” to display “YTD March.”

6. Save the copied and modified report set. Adjust the dimensions on the copied report if you created new report sets to accommodate the Substitution Variables. When you have the report highlighted within the Reports file cabinet, select “Setup” to view the Report Details and Report Settings. For example, you may need to move one dimension to the Page (such as Measures) and another to the Column (such as time) to use the new column set.

7. Run the newly transitioned report. Compare the results to the original report/report set(s) and make adjustments if necessary. You may change the values of the Substitution Variables at run time, however, these changes will not be saved with the report.

8. In addition, moving highly repeated members of Rules to the page level will improve report performance. If “*Measures+.*MTD+” is used in many of the Rule within a report set, you may move Measures to the page and include the measures dimension in the Rule only in fields where you do not want MTD.

9. Delete or rename the original report, which is no longer in use. Rename the transitioned report accordingly.

Use of Substitution Variables in Dynamic Reports

Substitution variables displayed are filtered based on Reporting Area. For example, @CURBDGT@ may be defined under the Financial Reporting Area and therefore can only be used if you select Financial as the Reporting Area while creating a Dynamic Report.

System-Defined Substitution Variables

There are 49 derived variables for the @CURYR@ substitution variable on the Time dimension. These derived variables are available for Financial and Workforce reporting areas.

You can access the derived variables by navigating to Maintenance > Report Administration > Cube Settings > Substitution Variables > @CURYR@ > Derived Variables.

The following Substitution Variables are available in your application by default.

Custom Members

The benefit of this feature is that formulas can be reused allowing for rapid chart production and more flexible and complex display of data.

Custom Members can be used on the horizontal or vertical axis within the chart. A few examples of the formulas that you can define and use in Dashboards follows.

To sort products in descending order and returns the top 5 products with the highest values:

TopCount({Order({{{Descendants({[Product].&[1]},,LEAVES)}}},([Time].&[5080],[Measures].[MTD]),desc)},5)

To calculate variance between budget and forecast for the given period using substitution variables:

((@CURBDGT@,@CURMTH@)-(@CURFCST@,@CURMTH@))/(@CURFCST@,@CURMTH@)

To get data for a specific combination of dimension members.

([Account].&[174],[Company].&[109],[Department].&[1])

To get the sum of values for accounts.

sum({[Account].&[197] , [Account].&[198] , [Account].&[199] , [Account].&[201] , [Account].&[202] , [Account].&[344] , [Account].&[203] , [Account].&[474] , [Account].&[204] , [Account].&[205] , [Account].&[206] , [Account].&[207] , [Account].&[208]})

For the descendants of a member in the hierarchy and to order them within a hierarchy.

Hierarchize({{Descendants({[Account].&[194]},,LEAVES)}})

To calculate variance between actual and budget using substitution variables.

@ACTUAL@-@CURBDGT@

To calculate variance between the previous month actual and current month budget using substitution variables.

([Scenario].&[1],@CURMTH-1@)-(@CURBDGT@,@CURMTH@)