Business logic represents a set of features that you can add to existing cubes. They are usually comprised of one or more rule templates, and may also add features to existing dimensions. To be fully operational, you may have to extend other database content.
To add business logic to cubes in either Jedox Web or Excel Add-in:
- Open the Modeler.
- In the Navigation pane, right-click on the relevant cube and select Add Business Logic… from the context menu, as shown below:
- A dialog is displayed, prompting you to select a template:
- Select the type of business logic you want to add. The options are described below.
Version blending business logic adds rules that blend values from the actual version into forecast versions.
Note: Version blending is only possible on cubes with both a
Version and a
The logic assumes that a
Version dimension exists in the database; if missing, this dimension will be created. The
Version dimension requires an
Actual Months attribute, which will also be created if it doesn’t already exist. Furthermore, it uses a
Month dimension (created, if missing) of type “Time”. Finally, the business logic adds a rule template to the cube. This rule will then fetch values from the actual version for the number of months in the Month dimension, as defined on the Actual Months attribute of the Version dimension.
KPI Calculation allows you to control the calculation of key performance indicators in a controlling dimension based on expressions from an attribute in that dimension.
When adding this business logic, you must specify the controlling dimension, which can be an existing dimension that contains KPIs, or a new dimension; in the latter case, that dimension will be created. Attributes called “Calculation” and “CalculationDependencies” will be added to this dimension. In the cube itself, a rule template for the KPI Calculation is added.
KPI Calculation (by Version)
KPI Calculation (by Version) operates in a similar way to KPI Calculation but calculates the KPI based on a selection from the
When adding this business logic, you must specify the controlling dimension, which can be an existing dimension that contains KPIs, or a new dimension; in the latter case, that dimension will be created. Four attributes (PCalculation, PCalculationDependencies, ACalculation, and ACalculationDependencies) will be created in the controlling dimension if missing. In the
Version dimension (created if missing), an attribute called “Calculation Schema” is created.
When defining values for the Calculation Schema attribute in the
Version dimension (e.g. “A” or “P”), the KPI calculation for that version will automatically use the matching definition from the control dimension’s attribute.
This logic adds rules for the Previous Year version to the cube. It shows ‘Version’:’Actual’ values of one year before on the ‘Version’:’Previous Year’ version.
Make sure that the dimensions Version and Month already exist in the cube before adding the business rule.