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. The GLCMAIN cube rule provides automated sign logic, reduced manual errors, and improved 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 an account type through the GSCSIGNDEFINITION cube.

Formula logic

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

This rule is used for the GLCSIGNCACHE cube:

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

Calculated metrics rules

To define calculated metrics, use these metrics:

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

With this feature, cube rules are automatically published for each calculated metric within the KPIs rule group for the GLCMAIN cube. It ensures that calculations are consistently and accurately reflected in the cube, improving the KPI management efficiency and reliability.

Calculated metric rules offer these benefits:

All calculated metrics are automatically available as cube rules.
Effort and error risk are reduced when creating calculated metric rule.
Clear and consistent calculation logic applies to all calculated metrics.

A cube rule for each calculated metric 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 specified for the calculated metric, the cube rule target must be extended with 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, except for special cases.
For more information, see, Special cases.

Calculation adjustment by publishing from Business Modeling to OLAP

The calculated metric's calculation property is modified to replace all references, such as [xyz], with [GLDACCOUNT:'xyz'].

Examples:

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

For calculations with the N prefix, the prefix is removed and the rule is set to affect base cells only.

For calculations with the C prefix, the prefix is removed and the rule is set to affect consolidated cells only.

Note: In Business Modeling, you can customize rules or load a default package with predefined calculated metrics .

Objectives calculation

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

You must place cube rules in the dedicated KPI Objective Assignment folder within the GLCMAIN cube.

The cube rule structure contains these elements:

Affected cells: All
Target: [GLDACCOUNT: 'Objective 1_CALC_XXX']
Formula: [GLDACCOUNT: 'CALC_XXX']