GLCMAIN

The Global Sign cube rule template manages sign logic for financial data that depends on account types and entity currencies.

The GLCMAIN cube rule ensures correct sign handling for financial data across account types and entity currencies. It automates sign logic, reduces manual errors, and improves consistency in Financial Reporting.

Template

  • Category: Global Sign
  • Name: Global Sign
  • Affected Cells: All cells in the GLCMAIN cube for each entity currency
  • Target: [GLDCURRENCY: '<param>']
  • Formula: Applies sign logic based on account type using the GSCSIGNDEFINITION cube

Formula logic

The formula multiplies the local currency value by a sign factor based on the account type for each account, using the GLCSIGNCACHE cube.

This is the rule for the GLCSIGNCACHE cube:

[GLDCURRENCY:'<param>_LC'] * DB('GLCSIGNCACHE', !GLDACCOUNT, 'SIGN')

Calculated Metrics rules

You can define calculated metrics by using these metrics for the calculation:

  • Base Metrics
  • Statistical Accounts
  • KPI Account Groups
  • Accounts from the Chart of Accounts

This feature automatically publishes cube rules for each calculated metric within the KPIs rule group for the GLCMAIN cube. It ensures calculations are consistently and accurately reflected in the cube, making the KPI management more efficient and reliable.

These calculated metric rules offer these benefits:

  • All calculated metrics are automatically available as cube rules
  • Reduction of effort and risk of errors in calculated metric rule creation
  • Clear and consistent calculation logic for all calculated metrics

For each calculated metric a cube rule is published under the KPIs rule group in the GLCMAIN cube.

Rule structure

Each published cube rule includes these elements:

  • Name: Name of the calculated metric
  • Description: Description of the calculated metric
  • Target: 
    [GLDACCOUNT:'<CalculatedMetric>', XPADUNITOFMEASURE:{'TOTAL', ‘<OLAPId of the BOR identified by UnitOfMeasureId>’}]

    If the UnitOfMeasureId property is filled in for the calculated metric, the cube rule target needs to be extended with the OLAPid.

    For more information, see XPADUNITOFMEASURE Unit of Measure.

  • Formula: The calculation logic for the Calculated Metric, with all references adjusted to the GLCMAIN cube format. The references in the formula receive [<ref>,XPADUNITOFMEASURE:'TOTAL'].
  • Affected cells: All cells, unless a special case applies. For more information, see, Special cases

Calculation adjustment by publishing from Business Modeling to OLAP

The value of the calculation property of the calculated metric is modified so that all references like [xyz] are replaced with [GLDACCOUNT:'xyz'].

Example:

  • Original calculated metric with the UnitofMeasureID Ratio property: 
    ['CALC_Cash_Ratio']=['MAP_0001'] / ['MAPG_2100']
  • Published formula including the Unit of Measure: 
    [GLDACCOUNT:'CALC_Cash_Ratio',XPADUNITOFMEASURE:{'TOTAL','Ratio'}]=
[GLDACCOUNT:'MAP_0001',XPADUNITOFMEASURE:'TOTAL'] / [GLDACCOUNT:'MAPG_2100',XPADUNITOFMEASURE:'TOTAL']

Special cases

  • If the calculation starts with N:, this prefix is removed, and the rule is set to affect base cells only.
  • If the calculation starts with C:, this prefix is removed, and the rule is set to affect consolidated cells only.
    Note: Rules can be customized in Business Modeling. A default package with predefined Calculated Metrics could be loaded into Business Modeling.

Objectives calculation

Cube rules are designed to forward the value of CALC_XXX to the corresponding mirror elements, such as 1_CALC_XXX objective.

These rules must be places in the dedicated folder KPI Objective Assignment within the GLCMAIN cube.

This is the cube rule structure:

Affected Cells: All

Target: [GLDACCOUNT: 'Objective 1_CALC_XXX']

Formula: [GLDACCOUNT: 'CALC_XXX']