Applies to:

Hyperion Planning - Version 11.1.1.3.00 and laterInformation in this document applies to any platform.

Symptoms

Scaling (a Planning feature) is used to change the way that currency values display, depending on which currency is associated with the current entity. For example, if the entity's base currency is Japanese Yen, the application designer could choose to apply 1000000 scaling, so that 4000000 will display as 4 in a web form. Similarly, if a user enters a value of 4 into this account-entity combination then it will actually be stored in Essbase as a value of 4000000.

The degree of scaling to apply is set as a property for the currency member concerned, in this case Japanese Yen, in the Currency dimension.

Scaling should only apply to currency type accounts. If an account is set to non-currency then there should be no scaling, irrespective of which entity (and which associated base currency) is in the point of view. The problem in this case is that scaling is being applied, despite the account member having the following properties:Data Storage: StoreDataTwo Pass Calc: NoSmart List: NoTime Balance: BalanceSkip Value: NoneExpense Reporting: NonExpenseAccount Type: SavedAssumptionExchangeRate Type: NoneData Type: NonCurrency

This kind of account should not be scaled.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms