1. Administrator's Guide
  2. Managing Metadata
  3. Defining Application Settings

Defining Application Settings

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

  • 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 the Application Settings Attributes table.

Table 4-7 Application Settings Attributes

Attribute Description

ConsolidationRules

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.

DefaultCurrency

Specifies the default currency for the application. This attribute is required.

DefaultRateForBalanceAccounts

The account that contains the translation rate to use for ASSET or LIABILITY accounts. This attribute is required.

DefaultRateForFlowAccounts

The account that contains the translation rate to use for REVENUE or EXPENSE accounts. This attribute is required.

DefaultValueForActive

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.

EnableMetadataSecurityFiltering

Specifies whether users can view all dimension members or only dimension members to which they have access. The system filters these dimension members:

  • Scenario

  • Entity

  • Intercompany Partner (ICP)

  • Account

  • Custom

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

FDMAppName

Name of the Oracle Hyperion Financial Data Quality Management application

ICPEntitiesAggregationWeight

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.

MaxCellTextSize

Specifies the maximum number of characters that can be used for cell text. Specify 1900 or greater up to 2,147,483,646. Values between 0 and 1899 are not valid. The default value is 8,000.

MaxNumDocAttachments

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.

MaxDocAttachmentSize

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.

NodeSecurity

Specifies the type of security access for nodes. This attribute is required. Select Entity to check node data based on the entity's security access, or select Parent to check node data based on the parent's security access.

OrgByPeriodApplication

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.

SupportSubmissionPhaseforAccounts

Specifies whether phased submissions in process management are supported for accounts in the application.

Valid values are Y or N. Default is N.

SupportSubmissionPhaseforCustom

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.

The number of attributes is based on the number of Custom dimensions defined for the application. The attribute name changes to reflect the Custom dimension alias. For example, Custom in the attribute name is replaced with the Custom dimension alias.

SupportSubmissionPhaseforICP

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 or N to use the value at exchange rate (VAL) translation method.

UsePVAForFlowAccounts

Specifies the default translation method for FLOW accounts. Specify Y to use the periodic value (PVA) translation method or N to use the value at exchange rate (VAL) translation method.

UseSecurityForAccounts

Specifies whether accounts in the application are protected by security. Specify Y for security on accounts or N for no security.

UseSecurityForCustom

Specifies whether Custom dimensions in the application are protected by security. Specify Y for security on Custom dimensions or N for no security on Custom dimensions.

The number of attributes is based on the number of Custom dimensions defined for the application. The attribute name changes to reflect the Custom dimension alias. For example, Custom in the attribute name is replaced with the Custom dimension alias.

UseSecurityForEntities

Specifies whether entities in the application are protected by security. Specify Y for security on entities or N for no security on entities.

UseSecurityForICP

Specifies whether ICP members in the application are protected by security. Specify Y for security on ICP members or N for no security on ICP members.

UseSecurityForScenarios

Specifies whether scenarios are protected by security. Specify Y for security on scenarios or N for no security on scenarios.

UseSubmissionPhase

Specifies whether phased submissions in process management are used in the application.

Valid values are Y or N. Default is N.

ValidationAccount

Specifies the account name to use for validation. The account used for validation must be an existing account.

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 1 is used for Submission Phase 1, and Validation Accounts 2 to 9 are used for Submission Phases 2 to 9.