PPS Planning – How to run a Currency Translation Job

PPS Planning allows the user to create a Currency Translation Job in order to facilitate a model’s data to be converted to any currency.

In order to accomplish this there are certain criteria that a model must adhere to.

  1. The model must be a Financial type of model.  Either a Financial Model with Shares or a Financial Model without Shares
  2. You need to add the Currency dimension to the model
  3. The Exchange Rate Model must be linked in as an assumption model
  4. The Time granularity of the Exchange Rate model must be the same as the granularity of the model that you want to convert
  5. The model property Default Currency can optionally be set to one of the currency members in your model.  If it is, then this currency will be used to triangulate an exchange rate if a direct rate is not specified in your Exchange rate model for the period(s) that need to be translated.
  6. Enter your exchange rate data in the Exchange Rate Model for the exchange rate members AVE (this rate is used to convert the Income Statement) and CLO (Used to convert the Balance Sheet).  You can also fill in the other rate type members if you want to customize your currency rules or if you are using the Flow dimension in your model.


This report shows the data in the Exchange Rate model that will be used to convert the fact data in our model for

  • Scenario = Actual
  • Time = Q2 2004
  • Destination Currency = USD
  • Source Currencies = {EUR, GBP, CAD}
  • Exchange Rate Types = {AVE, CLO, OPE, HIST}





Now I can run a currency conversion job to convert my data.



Using the above job properties will have the net result of converting all of fact data for my Budget model using the following job properties

  • Target Model = Budget
  • Entity = Resorts (The job will convert all of the fact data for entity Resorts and all of its descendants)
  • Scenario = Budget
  • Reporting Currency = USD (Convert all applicable entities data to USD.  If the default currency of the desired entities is already USD then it will do nothing for those entities)
  • Start Period = Q 2 2004
  • End Period = (Since this is blank, then it will only convert the data for the one period Q 2 2004)
  • Exchange Rate Start Period = Q 2 2004 (If this had been left blank it would use the Start Period which in our case is also Q 2 2004.  We could have used the Exchange rates from another period)
  • Exchange Rate End Period = (Since this is blank it will be the same as the Exchange Rate Start Period – Q 2 2004)
  • Exchange Rate Scenario = Actual (If this had been left blank, it would use the same scenario for the Exchange Rates as the parameter Scenario.  In this case it would have used Budget, but for this example we wanted to convert the Budget data using the Actual Exchange rates)

Comments (3)

  1. rodonnell says:

    It appears PPS Planning cannot maintain proper currency conversion for Income Statement for 2 quarters (or months) at the same time. To get Q2 end values, I would want to use Q2 end Rate for all Income Statement data from first day of Q1 through last day of Q2. To get Q3 end values, I would want to use Q3 end rate for all Income Datement data from first day of Q1 through the last day of Q2. I then normally display this data in a side by side fashion with Income Statement accounts/summaries as rows and then Q1, Q2, and Q3 YTD values as columns. I would want Q1 to use rate from end of Q1. Q2 to use rate from end of Q2 and Q3 to use rate from end of Q3. How can this be done?

  2. Parveen says:

    Nice information on Currency Translation Job. Thank you for post.