L07 entities scenarios

Editor's Notes

• #4: When you run a consolidation, data rolls up from children to parents as defined in the Entity dimension hierarchy If a member is placed in more than one location in the hierarchy, be sure that the rollups it is part of have different top-level parents so that the data for the entity does not get counted twice. In the illustration, EastSales and WestSales are members of both a geographical rollup with Geographical as the top member and a rollup based on functional area with Activity as the top member.
• #5: Before Adding Entities Holding companies are used in statutory consolidations. In these consolidations the consolidation path does not always match the dimension hierarchy. The holding company identifies the owner of the member, which might not be its parent in the hierarchy. The default parent is used by functions in reports and rules that need refer to a member parent value. If there is more than on parent, the function will use the default parent.
• #6: Journals let you make adjustment to accounts after the account data has been loaded or entered. Unadjusted values are input to the <Entity Currency> member. Adjustments from journals are posted to the <Entity Curr Adj> member. The adjusted value in <Entity Curr Total> is aggregated to the parent during consolidation Use the AllowAdj propertu to enable or disable journal adjustments for each entity If you have entities that rollup to more than one parent, you can enable the the AllowAdjFromChildren option for the parent entities. This let you apply an adjustment for a child to a selected parent rather than to all parents.
• #7: ISICP Property The ISIcp property for entities specified whether they can be partners in intercompany transactions. Member for which the ISICP property is selected automatically displays as members in the ICP dimension. The ICP dimension is used to specify the intercompany partner in a transaction. Security as Pattern Property You might have users should not want to have edit rights to an entity, but should be able to eliminate intercompany transactions with that entity. You can specify a separate security class for an entity when it acting as an intercompany partner. An entity can only have intercompany transactions with partners that have a matching security class.
• #8: The ICP Dimension contains a system-generated list of the members from the entity dimension that have IsICP selected. You use the ICP dimension to specify the partner for an entity when entering intercompany transactions The only properties you can edit for members in the ICP dimension are the description and security class.
• #9: The currencies you define for your application are use to store translated values for entities. Each currency you add will be listed in the Value dimension. You can select a currency from the Value dimension to view data values translated to that currency. The currencies also display as system-generated members in the Custom1 and Custom2 dimensions. You use these members for entering currency exchange rates. The scale for a currency specifies the unit in which amounts are displayed and stored for the currency by identifying where the decimal point is placed. It also determines how the exchange rate must be entered. For example, if data is scaled to thousands, a value of 1 entered on a data entry form is stored as 1000 in the database. Specify one of the following values for Scale: § blank = No scaling§0 = Units§1 = Tens§2 = Hundreds§3 = Thousands§4 = Ten Thousands§5 = Hundred Thousands§6 = Millions§7 = Ten Millions§8 = Hundred Millions§9 = Billions
• #12: Hyperion Financial Management give you the flexibility to input and view either periodic or year to date data values. For example, if you input your data as year to date values, when you select Periodic as the data view, Hyperion Financial Management will automatically derives the periodic values from the year to date values.
• #13: Hyperion Financial Management interprets missing data as zeros for display on reports and for calculating summary time periods. For each scenario you can specify whether zeros for missing data are interpreted as zero for the current period or zero year to date. The example shows a periodic view of data, with data missing for August. The Budget scenario interprets missing data as zero for the current period, so the value for August displays as zero. The Forecast scenario interprets missing data as zero for the year to date value. Since July had a value of 75, the current period value for August is interpreted as -75, to result in a year to date value of 0 for August.
• #14: Process Management is the management of the review and approval process. Data is grouped into process units for review. A process unit is the combination of data for a specific Scenario, Year, Period, and Entity. Each process unit can have up to 10 levels of review. Process management is enabled or disabled by scenario. EnableProcessManagment: Select this option to make process management available for a scenario. MaximumReviewLevel: This option specified the maximum level of review for process units for this scenario. Enter a number from 1 to 10.