Return to Profit Center Model Overview.
The KPI calculation defines calculations for some elements of a dimension. The calculation is defined by an expression stored in an attribute of the calculated element. The KPI calculation for the Profit Center cube is defined in the PC Account dimension.
The KPI calculation for actual data is different from the calculation for planning data. Therefore, the Version elements are grouped into calculation schemas. The standard configuration defines the following two calculation schemas:
|
Calculation Schema |
Definition |
|
|
Calculation in the |
|
|
Calculation in planning versions |
This assignment is defined by the Calculation Schema attribute of the Version dimension.
If the Calculation Schema attribute is empty (like for Previous Year in the above example), no calculation applies to this version.
The calculations for elements in the PC Account dimension are defined in the attributes PCalculation (for versions assigned to the P calculation schema) and ACalculation (for versions assigned to the A calculation schema). More generally, speaking the calculation for a calculation schema is defined in the attribute starting with the first letter of the calculation schema followed by …Calculation.
The calculation can be defined as an expression in the Jedox rule syntax. This expression must not contain the target nor the equal sign. It may contain an optional cell-type restriction (B: or C:) followed by any valid rule expression.
Example:
For each element of the PC Account dimension in combination with the calculation schema having a calculation, a rule instance will be created. This is managed by a rule template.
The creation of rule instances can be restricted by additional dependencies. The dependencies for elements of the PC Account dimension are defined in the attribute PCalculationDependencies (for versions assigned to the P calculation schema) and ACalculationDependencies (for versions assigned to the A calculation schema). More generally speaking, the calculation for a calculation schema is defined in the attribute starting with the first letter of the calculation schema followed by …CalculationDependencies.
If the calculation dependency is the text Cube: followed by a cube name, the calculation will only be valid if the referred cube exists in the database. Otherwise, the rule instance will not be created by the rule template. If the calculation dependency is empty or the attribute is missing, the calculation is always valid.
The target area of the calculation is the element from the PC Account dimension, the list of versions for the calculation schema, and the Input measure of the Profit Center_measure dimension.
In addition to these coordinates, the target can be restricted further as defined in the attribute PTargetRestriction (for versions assigned to the P calculation schema) and ATargetRestriction (for versions assigned to the A calculation schema). More generally speaking, the calculation for a calculation schema is defined in the attribute starting with the first letter of the calculation schema followed by …TargetRestriction.
The target restriction consists a comma separated list of any number of dimension elements e.g. 'Partner Entity':'~','Profit Center':'~','Partner Profit Center':'~','Partner Cost Object':'~'. If the target restriction is empty or the attribute is missing, the target area is not restricted further.
Note: after changing the calculation schemas or the calculations, the rule templates handling the KPI calculations in the fact cubes need to be updated.
Updated July 8, 2024