This BR is a very flexible rule for performing a multitude of calculations in the multi-dimensional environment of this product.

  • Note that this business rule acts upon and stores data into the fact tables. You may need to take this into account in certain calculations to understand how they are performed.


  • Name - Enter the name you would like for this BR.
  • Description - Add a description of that this business rule to make it easy for your colleagues to understand.
  • Type - Displays the type of BR. Can not be edited.
  • Comment - Additional notes or comments can be added here.
  • DataClass - Dropdown to select which DataClass this rule will store results of calculations into. Note the rule can use source data from other data classes.
  • Main dimension - Dropdown to select the main dimension for calculation.
    • Example: If you would like to calculated the value of an account based on other accounts - select “Account” here.
  • Fixed dimension - Will force output of BR into dimensionality specified here.
    • Syntax is [Dimension]=[Leaf level Member of same dimension]
    • You may specify multiple such combinations separated by a “|”. Each dimension may only specified once.
    • The easiest way to specify this is to click on the button to the right which will give you a dimension dialogue. This can be repeated multiple times.
    • Example: BusinessProcess=BR_CF|BusinessRule=NONE will store all output with dimensionality set to BR_CF in the BusinessProcess dimension, and set to member NONE in the BusinessRule dimension.
  • Dimension filter - Will limit the execution of this BR to only act on data specified.
    • Recommended default setting is: BusinessProcess=Consolidated|BusinessRule=NONE
    • Allowed syntax is one of the following
      • Basic selection
        • [Dimension name]=[One or more MemberKey(s) of the default hierarchy of the same dimension, separated by comma]
          • The member keys selected can be Parents. If Parents are selected it is equivalent to selecting all leaf members under that parent in the default hierarchy.
          • Example: BusinessProcess=Consolidated
        • [Dimension name]:[Hierarchy name]=[One or more MemberKey(s) of the specified hierarchy of the same dimension, separated by comma]
          • The member keys selected can be Parents. If Parents are selected it is equivalent to selecting all leaf members under that parent in the specified hierarchy.
          • Example: Account:GAAP=AC_Expense,AC_Tax
        • [Dimension name].[Property name]=[One or more property values of leaf dimension members, separated by comma]
          • This will give all Leaf dimension members with matching property values.
          • Example: Employee.MedicalPlan=BQ47,BQ49
      • Not equal. In the above examples you may instead of “=” (equal) use “<>” (not equal).
      • You may specify multiple such selections separated by a “|”. Each dimension may only specified once.
        • Example: BusinessProcess=Consolidated|BusinessRule=NONE will limit the rule to only act on data that is in any BusinessProcess rolling up to the Consolidated parent, and only on data that has been currency converted.
    • The easiest way to specify this is to click on the button to the right which will give you a dimension dialogue. This can be repeated multiple times.


Left pane (and top of right pane) in picture below

  • Click on a destination to display its steps in right pane.
    • Member ID of destination shown in list.
    • Name, Dimension and DataClass of destination shown in top right pane when selected.
  • New destination button will create a new destination member in the list.
    • Only leaf level members are allowed as destinations.
    • You may multi-select destination to add more than one at once.
  • Right-click on a destination to Remove and delete it from the list.
  • Drag and drop a destination to alter the execution order of the list of destinations.
  • Multiply result with can be reset and changed. This will multiply the result with this constant value
    • After all step calculation have been performed.
    • Before storing the final value into the destination.
  • Press Save button to save any changes made.


Defining the steps and Basic step settings

Right pane in picture below


  • New Step button adds a new step.
    • All members are allowed as basis for steps.
    • You may multi-select steps to add more than one at once.
    • Important note on multi-step rules referencing output from earlier calculation steps
      • You may use the output of one step as the input for another step. The rules engine will determine the correct order of execution.
      • A reference to a previous step must be to a Leaf level (the exact output of the previous step).
      • A reference to a parent member containing leafs calculated in previous steps is not allowed and will give unpredictable results.
  • Drag and Drop steps to alter the order of them.
    • Order of steps are important - see Operator below.
  • Operator dropdown selects how this step will applied to the result of the previous steps.
    • The operator of the first step is always “=” and cannot be changed.
    • Note that steps are calculated in strict order.
      • Each step will use the intermediate result from earlier steps and be applied with selected operator.
      • Example (using fixed values to explain arithmetic logic)
        • Step 1: = 100
        • Step 2: / 20 –> Intermediate result of 5
        • Step 3: + 15 –> Intermediate result of 20
        • Step 4: / 5 –> Final result of result of 4
  • Multiply with multiplies the result with a constant value.
    • Most commonly used for -1 or 1 to reverse sign but can be used for any number scaling purpose.
  • Modifier with parameter set a modifier for the value. The following modifiers are available
Modifier Parameter Comment
none No modifier applied. Original value will be used.
Multiply Factor Multiply with Factor. Same effect as using “Multiply with”
Divide Denominator Divide by Denominator
Month # months Shift value by # Months. Example: -1 would take value of previous month.
FFY # years Will give the Full Fiscal Year value. Can optionally be shifted # years with parameter.
FCY # years Will give the Full Calendar Year value. Can optionally be shifted # years with parameter.
Movement # months Calculates the Monthly movement of a Balance account. Can optionally be shifted # month with parameter.
FYTD # years Fiscal Year-to-Date value. Can optionally be shifted # years with parameter.
YTD # years Calendar Year-to-Date value. Can optionally be shifted # years with parameter.
R12 # months Sum of Rolling 12 months. Can optionally be shifted # months with parameter.
  • Dimension filter is shown here. To edit use Step Detail.
  • Comment is shown here. To edit use Step Detail.
  • DataClass is used to specify which Data Class to read data from.
    • none is default and means same DataClass as specified in Business Rule page.
    • Dropdown menu is used to select another DataClass.
    • When DataClass parameter is used in Step 1 (“=”) it is mandatory to specify all dimensions only existing in Destination DataClass explicitly in the Fixed Dimension BR setting (see example 2 below).
    • Data will automatically be summarized over dimensions that only exists in Source DC (in example 2 below, the Employee dimension).
    • Example 1: Multiply with Assumption.
      • Salary is stored on Account=6570 in Finance DC, Assumption of pension % is stored in Account=AS_PensionPct in Assumption DC.
      • Desired is to compute 6570*AS_PensionsPct.
      • The desired result can then by reached by
        • Main DataClass is set to Finance for BR
        • Step 1: Operator “=”; Account=6570
        • Step 2: Operator “*”; Account=AS_PensionPct with DataClass=Assumption.
        • Note: For Budgets and Forecasts you may want to set the type property of the destination account to Calculated which will give you flexibility on how to handle this in Input Sheets.
    • Example 2: Copy calculated data from HR DataClass to Finance DataClass in summarized format.
      • Monthly Salary is computed with HR DC and stored on Account=HR_C_Monthly in HR DC. This needs to be copied into the Finance DC, Account=6570.
      • Desired to be copied into the Finance DC, Account=6570 in summarized format.
      • Dimensionality (simplified example) of
        • Finance is Account, BusinessProcess, BusinessRule, Time, GL_Department, GL_ReferenceCode.
        • HR is Account, Employee, Time, GL_Department.
      • Conclusions on dimensionality differences:
        • Employee only exists in source DC (HR).
        • BusinessProcess, BusinessRule, GL_ReferenceCode only exists in destination DC (Finance)
      • The desired result can then by reached by
        • Main DataClass is set to Finance for BR
        • Fixed dimension setting example: BusinessProcess=BR_HR|BusinessRule=NONE|GL_ReferenceCode=NONE
          • It is mandatory to set these three dimensions not existing in Source DC explicitly in Fixed Dimension setting.
        • Step 1: Operator “=”; Account=HR_C_Monthly with DataClass=HR.
  • button is used to choose which of optional columns to display in step list.


Step detail settings


  • Click on a step to open the step detail settings.
  • Remove button will remove this step.
  • Duplicate button duplicates the selected step.
  • Move down button moves the step downwards in step/ execution order.
  • Move up button moves the step upwards in step/ execution order.
  • Apply button commits changes to this step detail.
  • Dimension filter - Will limit the execution of this BR to only act on data specified.
    • Allowed syntax is one of the following
      • Basic selection
        • [Dimension name]=[One or more MemberKey(s) of the default hierarchy of the same dimension, separated by comma]
          • The member keys selected can be Parents. If Parents are selected it is equivalent to selecting all leaf members under that parent in the default hierarchy.
          • Example: BusinessProcess=Consolidated
        • [Dimension name]:[Hierarchy name]=[One or more MemberKey(s) of the specified hierarchy of the same dimension, separated by comma]
          • The member keys selected can be Parents. If Parents are selected it is equivalent to selecting all leaf members under that parent in the specified hierarchy.
          • Example: Account:GAAP=AC_Expense,AC_Tax
        • [Dimension name].[Property name]=[One or more property values of leaf dimension members, separated by comma]
          • This will give all Leaf dimension members with matching property values.
          • Example: Employee.MedicalPlan=BQ47,BQ49
      • [Dimension Name]- signifies dimension detail exclusion.
        • This is only valid for Operators “*” (multiply) and “/” (divide).
        • It means that this dimension values will be summarized before calculation occurs.
        • This is similar to how dimensions are treated when copied from a DataClass that has dimensions not present in the destination DataClass.
        • Example 1: Revenue % split.
          • Revenue is stored on Account=4010, and on GL_Department=40,50.
          • Desired is to compute the percentage of revenue on each department.
          • The desired result can then by reached by dividing
            • Step 1: Operator “=”; Account=4010 with
            • Step 2: Operator “/”; Account=4010 with GL_Department- specified in Dimension filter.
        • Example 2: Units times Rates with currency..
          • Units is stored on Account=ST_Units with Currency=NONE, Cost per unit is stored on Account=ST_CPU in correct currency.
          • Desired is to ST_Units*ST_CPU and store in the currency of ST_CPU.
          • The desired result can then by reached by multiplying
            • Step 1: Operator “=”; Account=ST_CPU with
            • Step 2: Operator “*”; Account=ST_Units with Currency- specified in Dimension filter.
            • Note: Typically this calculation is performed limited to BusinessProcess=NONE, and any currency conversion is performed in following steps.
      • Not equal. In the above examples you may instead of “=” (equal) use “<>” (not equal).
      • You may specify multiple such selections separated by a “|”. Each dimension may only specified once.
        • Example: BusinessProcess=Consolidated|BusinessRule=NONE will limit the rule to only act on data that is in any BusinessProcess rolling up to the Consolidated parent, and only on data that has been currency converted.
    • The easiest way to specify this is to click on the button to the right which will give you a dimension dialogue. This can be repeated multiple times.
  • Comment - Additional notes or comments can be added here.
  • Apply button will commit the changes you have made to Step details.


  • v2/admin/br01-ref.txt
  • Last modified: 2021/03/16 17:43
  • by pcjamo