Integration of Detail-Planning Cubes (Cost Center Cube)
Return to Cost Center Model Overview
When running the Human Resources and Cost Center models on the same OLAP database, detailed data from the Personnel Costs cube can be automatically integrated into the Cost Center cube. The integration is implemented as rules in the Cost Center cube. These rules are defined as part of the KPI calculation.
The sample data package for the model contains some samples for the integration.
Example
The Cost Type element 311070 (Salaries & Wages) integrates values from the measure Wages and Salaries in the Personnel Costs cube.
- The
Employeedimension exists only in thePersonnel Costscube; the total value fromAll Employeesis integrated. - The
Currencydimension exists only in theCost Centercube. The value is integrated only into theLC(Local Currency) element, while other elements are set tonull. However, these other currency elements may be calculated by the currency conversion, which takes precedence over the KPI calculation. - All other dimensions are shared.
The rule expression for this is (Note: indentations and line breaks added for clarity):
PALO.DATA("", "Personnel Costs", !'Version', !'Month', !'Legal Entity', !'Cost Center', "All Employees", "Wages and Salaries")
The integration for planning versions (assigned to the P calculation schema) and for the actual version (assigned to the A calculation schema) are identical. The integration rule instances should be generated only if the source cube Personnel Costs exists.
The attributes for the Cost Type element 311070 (Salaries & Wages) are:
|
Attribute |
Value |
Remarks |
|
|
PALO.DATA("", "Personnel Costs", … |
The complete expression is shown above. |
|
|
Cube:Personnel Costs |
Create rule instance only if the source cube |
|
|
'Currency':'LC' |
Restrict calculations on the Currency dimensions to element LC. |
|
|
PALO.DATA("", "Personnel Costs", … |
Identical to the |
|
|
Cube:Personnel Costs |
Create rule instance only if the source cube |
|
|
'Currency':'LC' |
Identical to the PTargetRestriction attribute. |
Updated October 14, 2025
