Error when Locking a period in HFM 9.3.1

Question

Hi All,
When I try to lock September period in HFM I am getting the below error message:
“Cannot Lock Data because the validation account is not zero”
I have checked that my system validation account is Zero and the Process control for the entituy is at Published.
I have been able to lock all other entities except this entity and its parent.

Answer 1

Hi user9127887,
We came accross a similar issue. All the Base Entity data met the tolerance levels at the entry and publishing level; however, the sume of the etities fractionally caused the Parent Entity to be over the the tolerance level. We added HS.Round to these accounts and havn't seen the issue again.
Please see the following fix:
Aggregation of base members to a parent member produces a total value with a small decimal difference [ID 757443.1]
Modified 23-NOV-2010 Type PROBLEM Status PUBLISHED
Symptoms:
When entering data containing decimals the total value is not correctly summed up in the parent member due to a small differences (e.g. 0.0000000001234)
This is usually observed when the small remainder ends up in a Validation Account. You will sees 0 (zero) in the Process Control Grid or Web Grid, but when promote the Entity to next level receives an error: "The Validation Account is Not Zero".
Looking at the Full-Resolution Value or Stored Value for the cell, user can see the small remainder.
The Validation Status icon might actually be "green" in some HFM versions even though the stored value is not zero. @ this is because of unpublished Bug 7599539.
Cause
For default floating-point calculations, Hyperion Financial Management relies on Microsoft Foundation Classes. These libraries, which underpin Windows, have limitations.
You can verify this by entering the same data in Excel (with decimals) and then doing a SUM( ) of the values; the result will be exactly the same as the Full-Resolution Value of the parent member in HFM. This is because the underlying functions used for floating-point calculations are the same. The issue is also explained in this article on the Microsoft site.
Solution:
In your Rules, use HS.Round (documented in the HFM Administrator's Guide) to define the exact precision when needed. The function is financial-aware, so won't result in errors when dealing with decimals.
Do NOT use the standard VBScript "Round" function, as that one is not financial-aware and, with all probability, it will result in the same problem coming up again.
It is also possible to avoid encountering the issue by always loading data without decimals.
==================================================================================================
Please report your findings.
Drop me a note if you have any questions on this post.
P.S. Considering that you're on 9.3.1 suggests that the application is quit mature. Which suggest that you should have run into this error before now. Unless this Entity has suddenly changed the fractional amounts of data it is loading?
G'Luck.
-David
Edited by: David Debish on Jan 24, 2011 11:12 AM