Entities Notes

· Given an exhibit, identify how to set up parent/child relationships and how they are affected when used in multiple organisations.

Organisations are created in the Organization window of the Entities module. Where the same sub organisation exists in more than one organisation and the sub organisation is changed in one organisation it will be changed in all organisations which contain the sub organisation. For example if Legal and Geographical organisations both contain a North America sub organisation and an entity for Canada is added to the North America sub organisation in the Legal organisation it will also be added to the Geographical organisation.

· Given an exhibit, identify the parent/child relationships of currencies and what currency will be used or derived when translating.

Local currency values are translated into the currency of the parent entity. The currency of the parent entity defaults to the application currency. When set the currency of the parent entity will generally be the application currency but can be different.

· Given an exhibit of entity attributes, identify attributes and their effect on the system when they are turned on and off.

· Describe the steps and effect of adding, copying, deleting, and purging entities.

An entity can be added by selecting Edit > Add. If the entity has been previously removed and is then subsequently added any children and data are also added.

An entity can be copied by:

1. Selecting the Entity.
2. Selecting Edit > Copy.
3. Selecting a sibling and selecting Edit > Paste or selecting the parent and selecting Edit > Paste Dependant.

When an entity is  copied its children and data are also copied.

Entities can be deleted by selecting Edit > Remove.  Deleting an entity does not delete its data.

Entities can be purge by selecting Edit > Purge Unowned Entities. This should remove unowned entities from an application and delete all data for unowned entities. This option does not work on some version of Hyperion Enterprise see the FAQ for more information.

· Describe where to do currency administration, and which modules are affected by it.

In the Entities module select Navigate > Currencies to display the Currencies window. Currency administration mainly affects the Application, Entities and Accounts modules and they affect all modules except for the Categories module in some way.

· Describe how to build entity lists.

In the Entities module select Navigate > Entity Lists to display the Entity List window.

· Describe how to create fixed and dynamic lists and where or how entity lists may be used.

Fixed lists are created by selecting the Fixed attributes when creating a list. Entities are added to a fixed list by selecting individual entities or groups of entities. Fixed lists are not automatically updated when new entities are added. Dynamic lists are created in the same way as fixed lists except that individual entities cannot be added. Dynamic lists are automatically updated when entities with the same attributes as a list are added. Entity lists can be used to select units in the database module.

· Describe how to build entity conversion tables.

1. Select Navigate > Entity Conversion Tables and create a new table by pressing New.
2. Enter a name and description for the table and whether it is a load and/or extract table and press OK.
3. Enter the mappings for the table

· Given an exhibit, determine if the exhibit represents an import or export conversion table.

Import tables can have one external id to one internal id relationships and many external ids to one internal id relationships. Export tables can have one Hyperion Enterprise id to one external id relationships and many Hyperion Enterprise ids to one external id relationships.

· Describe where or how entity conversion tables may be used in the system.

Conversion tables can be used to load and extract data from Hyperion Enterprise to external systems.

· Given a situation, describe why a substructure or the DSM would be more effective.

Using the DSM is generally preferable to using substructures to track currency translations and adjustments as it makes the organisation structures simpler. However, if you have complex requirements you may still need to use substructures. Situations where you might need to use substructures are:

• Where you need to consolidate local currency values.
• Where you need to adjust both local and parent currency values.

· Describe the results of consolidating data through a given substructure.

For the following substructure and input with a EUR/GBP rate of 1.5:

Entity                Currency    Value
--------------------  --------  -------
consol_post           GBP              
 |-consol_adj         GBP           100
 `-consol_pre         GBP              
    `-local_post      EUR              
       |-local_adj    EUR           100
       `-local_input  EUR         1,000

The result of consolidation will be:

Entity                Currency    Value
--------------------  --------  -------
consol_post           GBP           833
 |-consol_adj         GBP           100
 `-consol_pre         GBP           733
    `-local_post      EUR         1,100
       |-local_adj    EUR           100
       `-local_input  EUR         1,000

· Describe the attributes of the DSM.

See Hyperion Enterprise Consolidation Detail.

· Given an organization chart exhibit, define where the DSM and substructures may be used.

The DSM and substructures can only be applied to base entities.

· Describe where shares are loaded and extracted.

Shares can only be loaded and extracted if the Ownership by Period and Category option was selected when the application was created and the entity Inter-company attribute is true. Text files containing shares can be loaded and extracted using options on the Task menu.

· Describe the meaning of the 3 options available for calculating ownership's and what information will be used or updated when these options are selected.

Percent Ownership Attribute

This is the percentage of an entity's regular shares other entities own either directly or indirectly. In dynamic organizations, you can type this value directly in the Entity pane, or the system can calculate it from share values that you load or enter. In static organizations, you can only enter this percentage in the Entity pane. You use percent ownership in formulas for calculating eliminations based on partial ownership, or for determining your percent consolidation. Entering and using percent ownership is optional.

Percent Control Ownership Attribute

This is the percentage of an entity's voting shares other entities own either directly or indirectly. In dynamic organizations, you can type this value directly in the Entity pane, or the system can calculate it based on voting share values that you load or enter. In static organizations you can only enter this percentage in the Entity tab. You can use percent control for determining consolidation method assignments in dynamic organizations. Entering and using percentage control is optional.

Percent Consolidation Ownership Attribute

This is the percentage of an entity's values that consolidate to its parent. In dynamic organizations, you can type this value directly in the Entity pane, or you can allow the system to propose it based on the methods defined on the Consolidation tab of the Application window. In static organizations, you can only enter this percentage in the Entity tab.

· Given an exhibit of shares loaded into Hyperion Enterprise, describe what would appear in the Inter-company dependants table after calculating ownership.

If this file was loaded into Hyperion Enterprise:

actuals_current
1
1
OV,sub_1,,100
OS,sub_1,,100
OV,sub_2,,100
OS,sub_2,,100
V,holding,sub_1,50
S,holding,sub_1,50
V,sub_1,sub_2,50
S,sub_1,sub_2,50

After calculating ownership the Inter-company dependants table would show:

· Define where entity code by period information can be set.

Entity codes by period can be set on the Advanced Option tab of the Entity window.