Knowledgebase: HFM
How to Determine Whether a Consolidation Issue is Caused by Non-Standard Consolidation Rules
Posted by Priya Doyle on 02 December 2010 08:24 AM

How to Determine Whether a Consolidation Issue is Caused by Non-Standard Consolidation Rules 

 Modified 05-MAY-2010  

Applies to:

Hyperion Financial Management - Version: 3.0.3.0.00 to 11.1.1.1.00 - Release: 3.0 to 11.1
Information in this document applies to any platform.

Goal

To help the HFM administrator determine whether an HFM consolidation issue is caused by a consolidation rule.

Solution

To determine whether the consolidation issue is due to a consolidation rule or some other cause, you need to:

1. Switch from a non-standard to a standard consolidation. Refer to the Note 779133.1 - How To Enable Consolidation Rules. In this case, you need to disable consolidation rules.
2. After loading the metadata, you can test the issue.

If you can reproduce the issue with standard consolidation, then the issue is either product related or related to rules outside the Sub Consolidate() subroutine. A Service Request should be opened with Support. Otherwise, the issue is related to consolidation rules. You should first contact the person who designed the consolidation rule. 

Note:
A standard consolidation is a type of consolidation driven by the application which uses the default consolidation and eliminations. A non-standard consolidation is driven by the Sub Consolidate() routine in the rule file. A non-standard consolidation is commonly used by statutory applications and is written by a qualified HFM person or HFM consultant.


(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: