SAP Knowledge Base Article - Public

2673706 - The exception aggregation field gets cleared when a shared dimension is updated in SAP Analytics Cloud (SAC)

Symptom

The exception aggregation field is cleared when a shared dimension is updated in SAP Analytics Cloud (SAC).

Environment

  • SAP Analytics Cloud 2018.12

Reproducing the Issue

Reproduction steps:

  1. Open a Planning enabled model that uses a public account dimension and modify a member in the account dimension (ex: by changing the decimals property value from 2 to 0)
  2. Now open another model that uses the same public account dimension and notice the Exception Aggregation is empty (It was previosuly SUM)
  3. Notice that the exception aggregation dimensions are still set even though the Exception Aggregation is empty
  4. If you try to modify a formula, the error "Exception Aggregation Type cannot be empty if an Exception Aggregation Dimension is selected"

Cause

  • This issue was due to the fact that the exception aggregation dimensions were not the same in both models.
  • A public account dimension needs to have the same Exception Aggregation Type and exception aggregation dimensions across all models.
  • Behaviour of a Global (public) Account Dimension:
  • The concept of a global account dimension is to ensure that the common accounts (base, calculated) behave the same across all the Models in which the account dimension is shared.
  • It does not make sense to have different exception aggregation types for the same account in different models.
  • Any change done to the system defined settings like "ID, Description, Account Type, Hierarchy, Unit & Currencies, Aggregation Type, Exception Aggregation Type, Scale, Decimal Places, Calculate On, Hide" will have impact across all the models. The same is applicable for User defined settings or columns) as well.
  • The only difference to this rule above is "Formulas" based on dimensions. You can define different formulas for the same account but be aware that you cannot choose to have different exception aggregation type for the same. Such configurations are not recommended.
  • If you want to have different settings for different account members then it's always advisable to use a local account dimension (or create a new global dimension specific only to that one model).

Resolution

This behaviour is as designed and there is no plan at the moment to enhance the current behaviour.

See Also

Your feedback is important to help us improve our knowledge base.
Please rate how useful you found this article by using the star rating feature at the beginning of this article.
Thank you.

Keywords

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, EPM-ODS, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics , KBA , LOD-ANA , SAP Analytics Cloud , LOD-ANA-BI , SAP Analytics Cloud - Business Intelligence (BOC) , LOD-ANA-PL , SAP Analytics Cloud – Planning (BOC) , LOD-ANA-BR , SAP Analytics Cloud - Digital Boardroom , LOD-ANA-PR , SAP Analytics Cloud – Predictive (BOC) , Problem

Product

SAP Analytics Cloud 1.0