How to turn off Currency Conversion within the execution of Fox code

Question

Hi All:
We have a number of custom key figures defined in a Planning Layout.
We had wanted to define those fields as type CURR with 4 Decimals, however it appeared that 2 Decimals was the maximum we could specify.  We therefore wound up using Type FLOATING POINT with 16 Decimals.
In some Fox code that calculates these custom key figures we then use a ROUND statement to produce values such as 3.2735000000000000.
When this Fox code executes in debug mode, I see a generated ABAP program running which includes Include programs RUPFGENTOP and RUPFGEN00.   This program executes a Form F_00001, which is essentially the Fox code. Here I can see the ROUND statement producing the desired result.  Right after though a Form TCURX_CONVERSION executes, which often reintroduces all 16 decimals, and I might get values, such as 3.2735000000000001 or 3.2734999999999998.   These small fractions cause other issues later on in the process.
In our case we are not trying to convert an amount from one currency to another, so we don't understand why it even would try to do a currency conversion.
My question:  is there any way to "turn off" this currency conversion routine?
Please advise - any suggestions would be most welcome.
Many thanks in advance,
Robert van der Kam

Answer 1

Hi Robert,
the solution suggested by Anass only works for key figures of type number. For key figures of type amout or quantity it is not allowed to change the number of decimals. Especially for amounts the number on the DB can only be intepreted correctly knowing the currency. Depending on the currency the value 1 on DB may be 100. This is why the FOX does the TCURX_CONVERSION, a better word would be currency shift since currency values have to be scaled depending on the values maintained in table TCURX. Since FOX needs one common number type for calculations the shift is neccessary.
This is the reason why amounts have only 2 decimals on DB, the real number of decimals comes from TCURX; no entry there means 2 decimals, i.e. not scaling is neccessary. This is why changing the number of decimals via domains might corrupt all data.
It seems that you are using release 7.0x, in releases 7.3x internally uses DECFLOAT data type, thus the 'problems' coming from binary arithmetic in ABAP FLOAT will not occur any more.
Regards,
Gregor