NOTRANS is not working

[#1]

Hi

Wonder whether anybody can share their experience regarding this.

According to the documentation, NOTRANS is a reserved Ratetype that you enter under the "Ratetype" property of an ACCOUNT and the consolidation engine will leave this ACCOUNT so tagged alone when doing currency translation. I take this to mean that I can enter an amount both in local currency (which is, say, USD) and translated currency (say MYR) and the translated currency amount will not be translated. This is great for ACCOUNTS that need to be translated at historical rate, or so I thought.

So I created an ACCOUNT, say, Reserves, and entered "NOTRANS" in the Ratetype property. Next, I entered 1,000 under Local Currency, switched the dimension to "MYR" and entered 2,333. After running SPRunConso, I expect the local currency and translated currency amount to remain at 1,000 and 2,333 respectively. However, the translated currency amount got zeroised instead.

Is there something I ought to be doing to make NOTRANS work?

Thank you.

Regards.

[Former Member · Accepted solution]

I think the NOTRANS means that the conversion engine makes sure that when there is LC data, there is no data on the translated currencies. The difference between this and "doing nothing" is that the destination is still evaluated and if there is data it will be reversed to zero, to prevent that there is data on an account that for example used to have ratetype AVG which is switched to NOTRANS. In this case you would this have old data on the translated account which you don't want. So that's why the engine reverses the amount to zero. Only in your case this is a pity, because you loose your input data.

-Joost

[Former Member · Accepted solution]

Hi Joost,

Thank you for solving the mystery of the disappearing translated currency amounts!

Since NOTRANS is out, then what should I do if I need to fix the value of a local currency amount to a specified translated currency amount i.e. translate the ACCOUNT at historical (instead of AVG or END).

Can I put "HIST" as the Ratetype of the ACCOUNT that requires translation at historical rate and in the Currency Conversion Rules Table, create a new rule saying Account Ratetype = "HIST" and Formula = "AS_IS"?

Is this the correct way to go?

Thank you.

Regards.

[Former Member · Accepted solution]

I think that would be the right solution. I never used AS_IS but if I look at the help file it states that it will leave already existing values in the destination currency untouched. So I think this will enable input at the currency itself. With AS_IS in the formula you can name the new ratetype whatever you want and put it in the rate_type property of the accounts you don't want to convert.

-Joost