|
| Home > Hyperion Enterprise > Certification > Consolidation |
Identify the meaning of the status flags (CHANGED, IMPACTED, CALC, OK, LOCKED, INACTIVE, and NO DATA).
| Status Flag | Meaning |
|---|---|
| IMPACTED | The data in this parent entity has been affected by changes to data in its child entities. |
| CALC | The manual says this status means the formulas in this entity have changed. However, in Hyperion Enterprise v5.1 when data has been changed the status is normally CALC even if the chart of account does not contain any formula. |
| CHANGED | The manual says this status means the data in this entity has changed. However, in Hyperion Enterprise v5.1 when data has been changed the status is normally CALC even if the chart of account does not contain any formula. This status does not seem to exist. |
| OK | The data in this entity has already been consolidated. |
| LOCKED | The data in this entity has been locked. Data in locked entities is not consolidated. |
| INACTIVE | This entity is not active. This status appears only in applications with organisations that vary by category and period. |
Given an exhibit, define what a particular status flag will be after executing a particular consolidation task.
After all consolidation tasks the only possible status flags are:
| Status Flag | Meaning |
|---|---|
| OK | The data in this entity has been consolidated. |
| LOCKED | The data in this entity has been locked. Data in locked entities is not consolidated. |
| INACTIVE | This entity is not active. This status appears only in applications with organisations that vary by category and period. |
Identify the effect on status flags when application elements are changed.
| Element | Action | Base Entity Status | Parent Entity Status |
|---|---|---|---|
| Account | Add | CALC | IMPACTED |
| Delete | CALC | IMPACTED | |
| Currencies | Add | CALC | IMPACTED |
| Delete | Not applicable | Not applicable | |
| Entities | Add | 0 | IMPACTED |
| Delete | Entity is deleted | IMPACTED | |
| Formulas | Add | CALC | IMPACTED |
| Delete | CALC | IMPACTED |
Currencies cannot be deleted when they are being used.
Identify the effect of status flags when data is changed (including GLOBAL exchange rate data.)
| Data | Base Entity Changed | Base Entity Other | Parent Entity |
|---|---|---|---|
| Global | CALC | CALC | IMPACTED |
| Normal | CALC | No effect | IMPACTED |
Given an exhibit of an intercompany matching report, identify where to look in the system to find the data displayed in the report.
1/27/03 10:21 AM
interco_single_curr - Intercompany single currency - USER
Matching Report: creditors_under_one - Creditors under one year
Category: ctd_current Period: Q1 02
Organization: Legal Entity: total Partner: Within Group
Scale: 0 Matching Currency: GBP Tolerance: 0
Entity Code: <None>
ENTITY MATCHING ENTITY interco_debtors (interco_creditors) DIFF (PAR-GBP) STATUS
headoffice
north 1000 -1000 0 MATCHED
south 1000 -990 10 DIFFERENT
east 1000 -990 10 DIFFERENT
west 1000 -1000 0 MATCHED
------------------------------------------------------------
SUBTOTAL 4000 -3980 20
------------------------------------------------------------
GRAND TOTAL 4000 -3980 20
Page: 1
|
In the above report the the intercompany balances in south and east are different from those at head office.
Identify the options that can be set when running an intercompany matching report.
| Intercompany Group Tab | Description |
|---|---|
| Intercompany Group | Selects the intercompany matching group(s) for which you want run reports. |
| Matching Options Tab | Description |
|---|---|
| Within Group | Selects intercompany transactions within the currently selects group of entities. |
| Outside Group within Organization | Selects intercompany transactions outside the currently selects group of entities but inside the current organization. |
| Outside Group within Application | Selects intercompany transactions outside the currently selects group of entities and inside any organization in the current application. |
| Select Partner | Selects intercompany transactions with a specified partner. |
| Entity Code | Filters entities included by entity code. |
| Entity Currency | Displays differences in entity currency on report. |
| Partner Currency | Displays differences in partner currency on report. |
| Parent Currency | Displays differences in parent currency on report. |
| Specified Currency | Displays differences in specified currency on report. |
| Reporting Options Tab | Description |
|---|---|
| Display Entity Description | Displays entity descriptions. |
| Display Account Detail | Displays account detail for multiple accounts in the intercompany matching group. |
| Display Account Totals | Displays account totals for multiple accounts in the intercompany matching group. |
| Display Accounts in Rows | Displays accounts in rows. |
| One Report per Entity | Creates a separate report for each entity. |
| Report Scale | Sets scale for values. |
| Decimal Places | Sets number of decimal places for values. |
| Suppress Status | Suppresses the Status column on the report. |
| Suppress Totals and Subtotals | Suppresses the Total and Subtotal rows on report. |
| Suppress Currency | Suppresses Currency columns on report. |
| Suppress Matching Values | Suppresses matched intercompany transactions and displays only unmatched transactions. |
| Matching Currency | Sets currency used by the system for matching tolerance. |
| Matching Tolerance | Sets values of differences which are not displayed on report. |
Describe minimum requirements to run the intercompany matching report.
| Requirement | Description |
|---|---|
| Intercompany entities | Created by setting entities Intercompany attributes to true. |
| Intercompany subaccount table | Intercompany entities are automatically added to this table. |
| Intercompany accounts | Created by attaching Intercompany subaccount tables to accounts. |
| Intercompany plug | A normal accounts |
| Intercompany matching group | Defines Intercompany accounts to match and plug account to post differences to. |
Describe where to setup intercompany matching and access the intercompany report.
To setup intercompany matching groups in the Accounts module select Navigate > Intercompany Matching.
To access intercompany reports in the Consolidation module select Task > Run Intercompany Matching Report.
Describe the effect of running a consolidation in the 3 modes/options available.
The result of all three modes should be the same. See notes below for more information.
| Mode | Effect |
|---|---|
| Consolidate All Impacted | Consolidates only entities that have been affected by data or method changes. The system consolidates entities with 0 if there is data in prior periods for that entity. |
| Consolidate All | Consolidates all entities. The manual say this can be used if changes have been made which are not reflected by the consolidation status indicators have been made and gives the example of exchange rates. However, if exchange rates are changed the status flags are updated. |
| Consolidate All with Data | Consolidates all entities with data. |
Describe the effect of running the 3 modes/options in 1 organization where the same part of the organization chart exists in multiple organizations.
The data in all the organisation is consolidated.
Identify the default methods found in Hyperion Enterprise.
The default methods are CHART, CHARTDSM, CONSOL, DYNVIEWACCTS and TRANS see the Methods page for more information.
Given several sequences of logic execution, identify which one is the correct execution order, both with and without DSM activated.
The consolidation sequence is:
Identify the use of the percent ownership field when converting an application from Standard Edition to Hyperion Enterprise 5.
Hyperion Enterprise 5 uses the percent consolidation value for consolidation while Hyperion Enterprise SE uses percent ownership value.
Identify the use of the percent consolidation field.
Percent consolidation is the percentage of an entity's values that are consolidate into its parent.
Identify the DSM node when using the percent consolidation field.
The percent consolidation field affects Proportion detail.
Identify where in the system parent adjustments are made.
Parent adjustments are made in the Journal module. Though they affect parent entities parent adjustments can only be made to base entities.
Identify characteristics of an application that indicate where ACE might be appropriate.
the Statutory Consolidation Engine (ACE) might be appropriate for applications where:
Describe how ACE handles an impacted consolidation (by dependent rather than by parent.)
ACE overrides the normal Hyperion Enterprise methods for calculating consolidation detail. It improves performance level of the Hyperion Enterprise consolidation by:
Identify where to look in the system if data is not being eliminated in an elimination entity or elimination DSM.
The following must be configured before data can be eliminated:
| Copyright © 1999-2008 Consolidation Consultancy Limited | Last updated: 25 Jan 2008 |