Defining Application Settings

Application settings apply to an entire Financial Management application. Application settings determine the following information for the application:
l

Is the organization dynamic, using organization by period? Which dimensions are secured? What default translation rates and methods are used? What is the ICP weight? Are consolidation rules applied? What is the default currency?

You define application settings by using the attributes in Table 15.

Table 15

Application Settings Attributes Description Specifies whether consolidation rules are supported. Specify one of these values: Y to use the rules written in the Consolidate() routine in a user-defined rule. R to derive the proportional value in the Value dimension. Note that the proportional data is not stored. N to use the default consolidation and eliminations.

Attribute ConsolidationRules

DefaultCurrency DefaultRateForBalanceAccounts DefaultRateForFlowAccounts DefaultValueForActive

Specifies the default currency for the application. This attribute is required. The account that contains the translation rate to use for ASSET or LIABILITY accounts. This attribute is required. The account that contains the translation rate to use for REVENUE or EXPENSE accounts. This attribute is required. Specifies the default value for the Active account. This attribute is required. Specify 0 if the child is considered inactive and is not consolidated into the parent. Specify 1 if the child is considered active and is consolidated into the parent. Specifies whether users of an application see all dimension members or only the members to which they have access. The system filters these dimension members:
l l l l l

EnableMetadataSecurityFiltering

Scenario Entity Intercompany Partner (ICP) Account Custom1, Custom2, Custom3, Custom4

Specify Y to filter out the dimension members to which the user does not have access. The default for this attribute is N.

Defining Application Settings

89

Attribute FDMAppName ICPEntitiesAggregationWeight

Description Name of the Oracle Hyperion Financial Data Quality Management, Fusion Edition application Specifies the percentage of intercompany partner entity [ICP Entities] amounts that aggregate to the [ICP Top] member of the Value dimension. This attribute is required. The percentage is scaled to hundreds, with 1.0 equalling 100 percent. Specifies the maximum number of characters that can be used for cell text. Specify -1 for no limit or a positive number up to 2,147,483,646. The default value is 8000. Specifies the maximum number of bytes for the size of document attachments. Specify -1 for no limit or a positive number up to 2,147,483,646. The default value is -1. Specifies the maximum number of document attachments per user. Specify -1 for no limit or a positive number up to 2,147,483,647. The default value is -1. Specifies the type of security access for nodes. This attribute is required. Specify Entity to check node data based on security access for the entity and Parent to check node data based on security access for the parent. Specifies whether new consolidation structures can coexist with past consolidation structures in the application. Specify Y to allow new organizational structures or N to allow only current organizational structures. Specifies whether phased submissions in process management are supported for accounts in the application. Valid values are Y or N. Default is N.

MaxCellTextSize

MaxDocAttachmentSize

MaxNumDocAttachments

NodeSecurity

OrgByPeriodApplication

SupportSubmissionPhaseforAccounts

SupportSubmissionPhaseforCustom1, SupportSubmissionPhaseforCustom2, SupportSubmissionPhaseforCustom3, SupportSubmissionPhaseforCustom4 SupportSubmissionPhaseforICP

Specifies whether phased submissions in process management are supported for the Custom members in the application. Valid values are Y or N. Default is N. Specifies whether phased submissions in process management are supported for ICP members in the application. Valid values are Y or N. Default is N.

UsePVAForBalanceAccounts

Specifies the default translation method for BALANCE accounts. Specify Y to use the periodic value (PVA) translation method and N to use the value at exchange rate (VAL) translation method. Specifies the default translation method for FLOW accounts. Specify Y to use the periodic value (PVA) translation method and N to use the value at exchange rate (VAL) translation method. Specifies whether accounts in the application are protected by security. Specify Y for security on accounts and N for no security. Specifies whether custom dimensions in the application are protected by security. Specify Y for security on custom dimensions and N for no security on custom dimensions.

UsePVAForFlowAccounts

UseSecurityForAccounts UseSecurityForCustom1, UseSecurityForCustom2,

90

Managing Metadata

Attribute UseSecurityForCustom3, UseSecurityForCustom4 UseSecurityForEntities UseSecurityForICP

Description

Specifies whether entities in the application are protected by security. Specify Y for security on entities and N for no security on entities. Specifies whether ICP members in the application are protected by security. Specify Y for security on ICP members and N for no security on ICP members. Specifies whether scenarios are protected by security. Specify Y for security on scenarios and N for no security on scenarios. Specifies whether phased submissions in process management are used in the application. Valid values are Y or N. Default is N.

UseSecurityForScenarios UseSubmissionPhase

ValidationAccount

Specifies the account name to use for validation. The account used for validation must be an existing account and must have a valid intersection with [ICPTop] in the Custom dimensions. In process management, validation accounts are used to ensure that the value equals zero before a process unit can be promoted to the next review level. Validation account is used for Submission Phase 1, and Validation Accounts 2 to 9 are used for Submission Phases 2 to 9.

Organization by Period
The organization by period functionality enables the most recent consolidation structure to coexist with past structures in the same application. Organizational structures can change for many reasons, including acquisitions, disposals, mergers, and reorganizations. To support organizational changes, Financial Management uses a system account, Active, to reflect the active or inactive consolidation status of a child into its parent. The Active account acts as a filter of the entity hierarchy. The Active account is an intercompany account that stores data at the parent level and uses the ICP dimension to store information about children. For an ICP member that corresponds to a child of a parent, the Active account indicates to the system whether the child should be considered as an active consolidation member for the current year, scenario, and time period. Children that correspond to ICP members for which the Active account is equal to 0 are considered to be inactive children and are not consolidated. Children that correspond to ICP members for which the Active account is equal to 1 are considered to be active children and are consolidated. Active account values can be viewed or changed in data grids. Similarly, changes to active child data affect the parent, while changes to inactive child data does not affect the parent. The DefaultValueForActive attribute controls the status of children for which the Active account is blank. So, every parent-child intersection does not have to be flagged as active or inactive. By default, every child is active in relation to its parent unless otherwise specified.

Organization by Period

91