Default Multi Currency Applications and why Planning is not converting all the Accounts Members in 11.1.2.3
Multi-Currency Planning Applications provides an ability to plan, forecast and analyze in multiple currencies. We can do the same using default Multi-Currency planning application creation option or you can create your own Custom Currency Dimension. Later is generally a preferred choice as it provides more flexibility.
Today we will be concentrating on Planning's Default Multi Currency Applications. While creating an application, Application creation wizard gives us an option to create multi currency applications, when you choose this option Planning Creates two additional dimensions:
1. Currency
2. HSP_Rates (We can see the members of this dimension in Essbase Only, and the dimension name in the Performance Settings in Planning Web)
Both of these dimension are by default Sparse in nature. In Currency Dimension we can add the different Currency Members which we want to assign to our Entities as base currency.
HSP_Rates dimension contains Few default members ex: HSP_InputCurrency, HSP_InputValue and based on the number of Currencies you have enabled in Currency Dimension you will get members like: HSP_Rate_USD, HSP_Rate_AUD etc. These members are the place holders for exchange rates.
Once you will create a multi currency application, here are few steps you can do:
1. Add the currencies in which users will be entering data and enable them for Reporting too, if required,
2. Enter the Exchange Rates at following location:
Here is little more information on Exchange Rates.
3. Associate the exchange rate table to the scenario for which you want to perform conversion.
4. Once done, create currency conversion script, you have to mention below information:
5. After clicking on Save, you will get two Calcs generated in Essbase:
6. We have to refresh database before we try to execute these scripts as the exchange rates information is stored in Planning Application's Relational database, Here are few of the tables which comes into picture:
7. Above two scripts are executed in order to get the currency conversion done. Here is little more information on working with Multiple Currencies.
Note: We have to mark account dimension members as No Rate, Average, Ending or Historical.
We have to add Exchange Rates type as No Rate for those Account members for which you don't want the conversion to happen Ex: Units, Days and other Saved assumptions.
Now the issue, in 11.1.2.3, Planning converts the members to #MISSING even though you have marked Account Members as No Rate, it should keep the numbers same and use the exchange rate as 1.
Lets take one example: Here we are entering Units Sold and SP Per Unit and Getting Sales, we are entering data in Local Currency of Singapore and will convert into Reporting which is USD. We have set Exchange Rates Types(Assuming SGD is half of USD) as No Rate for Units Sold and for others its Average
Lets Run the Currency Conversion and Look at the results in USD
Its not showing values at Units Sold and hence in Sales as Sales is Dynamic Calc. Its just Converting Selling Price Per Unit.
This is because if you look at HspCRtB.csc its using:
@ISUDA("Account","NoRate")
We need to replace "NoRate" with "No Rate" (Space between No and Rate) and run the rule again. Here are the results:
Cheers..!!
Rahul S.
Comments
Post a Comment