3 Replies Latest reply: Aug 23, 2013 4:37 PM by 892733

# How to set up the number of decimal place in HFM calculation?

Dear All:

My HFM 11.1.2.2 does some strange thing in calculation.

I have some account/entity POV with

<Entity Currency> = 1000.00000000000000

<Entity Curr adjs> = - 1000.00000000000000

<Entity Curr Total> =0.00000000046566

It really distorted my calculation in the next step since some number will divide by <Entity Curr Total>

I wonder how to set up the number of decimals in HFM. May I just have 6 -8 digits after the decimal.

or

is there any way to have my

<Entity Curr Total> =0.00000000000000

Thank you so much for your feedback.

• ###### 1. Re: How to set up the number of decimal place in HFM calculation?

Here is a helpful link, which describes floating point calculates in HFM. Also, check to see what you have set as the maximum number of decimal places in your account.

• ###### 2. Re: How to set up the number of decimal place in HFM calculation?

Thank you very much for your reply. I click the link and to access the document and it ask me to provide Support Identifiers. I may have to ask the admin in my company for that.

I used HFM Metadata manager to check my account properties. The only related field I see is

NumDecimalPlaces = 2

It applies to all the members in my account dimension.

• ###### 3. Re: How to set up the number of decimal place in HFM calculation?

Here is the article:

 Accuracy of HFM in Floating Point Calculations (Doc ID 1437033.1)

HFM calculations are carried out with 15 significant decimal digits; this  includes the digits to the left and right of the the decimal point.  The round-off error noted is considered normal for floating point calculations.  In fact, the relative error is 1.29 x 10^-15.

There are multiple sources for round-off errors in floating point  calculations, including conversions between decimal and binary (used internally to store numbers), internal calculations such as aggregation, consolidation, etc, and storage and retrieval in the database.  The order of  calculations can also affect the visibility of round-off errors.

That is 15 significant decimal digits is the maximum accuracy can expect with the product.

1. HS.Round() functions can be used to narrow down numbers especially in dynamic account rules