Forum Discussion
5 Replies
- chul
OneStream Employee
Copy the data to the target scenario with a seeding rule.
On the target scenario, you can either use a different rate type or use a custom translation rule that uses the rates from an existing rate type.
On the cube, change the Translation Algorithm Type from Standard to Standard Using Business Rules for FX Rates.
Hope that helps!
- vasantharaiduNew Contributor III
Hi Chul,
Thanks for your reply. Yes we already tried your method.
1.copied data from source to destination
2. Created separate fxrate type and linked with destination scenario.
But I want to make using formula to take from seeding local value from source to destination
I used api. Data. Calculate (s#source) =(s#destination) .
But it's taking all the value and rates. Simply I am not able to get the variance of fx rate between the scenario. Same data with different rate.
Can you help me on this
- chul
OneStream Employee
The rates are stored in the FX rates table so you're not copying the rates when you run your calculate statement - unless you're doing some custom translation using cube rates vs OneStream's native functionality. If your destination scenario yields the same results as your source scenario in both local and translated data, my guess is that your FX rates in your source Rate Type are the same as the FX rates in your destination Rate Type. You need to copy prior year's rates from the source Rate Type into the current year of the destination Rate Type.
Related Content
- 6 months ago
- 2 years ago
- 2 years ago
- 2 years ago