Business Logic represent a set of features that can be added 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, the user may have to extend other database content.
The 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 Month dimension.
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, the user 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 as KPI Calculation, but calculates the KPI based on a selection from the Version dimension.
When adding this business logic, the user 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.