Financial Management:

--------------------

FM provides eight system-defined dimensions and unlimited number of custom

dimensions that you can apply to accounts.

1. Scenario: It represents a set of data, such as Actual, Budge,or Forecast.

2. Year: It represents the fiscal or calendar year for data.

3. Period: It represents the time periods, such as quarters and months. FM supports
years, months and weeks for the period dimension.

4. Entity: It represents the organizational structure of the company. The entity

dimension is the consolidation dimension of the system. You define attributes for
Entity dimension members, such as default currency and security class and to
specify whether the entity allows adjustments and stores intercompany detail.

5. Value: It represents the types of values stored in the application and can
include the Input currency, Parent currency, adjustments and consolidation detail
such as proportion,elimination and contribution detail. For ex the entity currency
member stores the value for an entity in its local currency. The parent currency
member stores the value for an entity translated to the currency of the parent
entity.
The value dimension is useful for providing an audit trail of the transactions
applied to data.

6. Account: It represents a hierarchy of natural accounts.

Attributes for account dimension members - Account Type, whether account is
calculated, consolidated or intercompany partner account.

7. Intercompany: It represents all intercompany balances that exist for an account.

FM can track and eliminate intercompany transaction details across accounts and
entities.

8. View: It represents the various modes of calendar intelligence such as Periodic,

YTD, QTD frequencies.

Customer dimensions"

----------

HFM Metadata structures:

--------------------------
Application Settings
--------------------------
This section of a metadata file defines settings that apply to the entire Financial
Management application. For information on application settings attributes, see
Defining Application Settings.

This example specifies application settings attributes:

!APPLICATION_SETTINGS
DefaultCurrency=USD
DefaultRateForBalanceAccounts=Rate1
DefaultRateForFlowAccounts=Rate2
UsePVAForBalanceAccounts=Y
UsePVAForFlowAccounts=Y
ICPEntitiesAggregationWeight=1
DefaultValueForActive=1
ConsolidationRules=N
OrgByPeriodApplication=N
NodeSecurity=Entity
UseSecurityForAccounts=N
UseSecurityForEntities=Y
UseSecurityForScenarios=Y
UseSecurityForFlows=Y
UseSecurityForMarket=Y
UseSecurityForRegion=N
UseSecurityForCostCenter=N
UseSecurityForICP=N
EnableMetadataSecurityFiltering=N
SupportSubmissionPHaseForFlows=Y
SupportSubmissionPhaseForMarket=Y
SupportSubmissionPHaseForRegion=N
SupportSubmissionPhaseForCostCenter=N

-------------
Currencies
-------------
This section of a metadata file defines currencies. This syntax specifies a
currency:

Label; Scale; Descriptions

See Defining Currencies.

This example specifies currency attributes:

!CURRENCIES
EURO;0;English=European Euro
GBR;0;English=Great Britain Pounds
USD;0;English=United Stated Dollars

-------------
Members
-------------
This section of a metadata file defines the members of a dimension. You can use
delimiters to represent missing values as empty. Enter dimension members by using
this syntax:

!MEMBERS=Customers
'Label;IsCalculated;SwitchSignForFlow;SwitchTypeForFlow;
UserDefined1;UserDefined2;UserDefined3;SecurityClass;
DefaultParent;Descriptions
[None];N;N;N;;;;;DefaultParent=#root
AllCustomers;Y;N;N;;;;;DefaultParent=#root
Customer2;N;N;N;;;;;DefaultParent=AllCustomers
Customer3;N;N;N;;;;;DefaultParent=AllCustomers
Customer4;N;N;N;;;;;DefaultParent=AllCustomers
Customer5;N;N;N;;;;;DefaultParent=AllCustomers
Note:
For Custom dimensions, this section must use the Custom dimension alias name.

-------------
Account
-------------
Syntax for Account dimension members:
'Label, AccountType, IsCalculated, IsConsolidated, IsICP, PlugAcct, CustomTop,
NumDecimalPlaces, UsesLineItems, EnableCustomAggr, UserDefined1, UserDefined2,
UserDefined3, XBRLTags, SecurityClass, ICPTopMember, EnableDataAudit,
DefaultParent, Descriptions
See Defining Accounts.

The Custom_Order keyword is required for all new metadata files to define the
columns for Custom dimensions. This section must match the Custom Order of the
application profile (.per) file.

For example:

!Custom_Order=Product;Customers;Channel;UnitsFlows
The following example specifies attributes for two accounts, AdminExpenses and
CapitalStock:

!MEMBERS=Account
AdminExpenses;EXPENSE;N;Y;Y; ;AllCustom3;AllCustom1;AllMarket;AllFlows;2;N;Y;Y;Y;Y;
;
; ; ; ; ;N;DefaultParent=NetIncome
CapitalStock;LIABILITY;N;Y;N; AllCustom3;[None];AllMarket;AllFlows;6;N;Y;Y;Y;Y;
; ; ; ; ; ;N;DefaultParent=TotalEquity;English=Capital Stock
Account
Syntax for Account dimension members:

'Label, AccountType, IsCalculated, IsConsolidated, IsICP, PlugAcct, CustomTop,

NumDecimalPlaces, UsesLineItems, EnableCustomAggr, UserDefined1, UserDefined2,
UserDefined3, XBRLTags, SecurityClass, ICPTopMember, EnableDataAudit,
DefaultParent, Descriptions
See Defining Accounts.

The Custom_Order keyword is required for all new metadata files to define the
columns for Custom dimensions. This section must match the Custom Order of the
application profile (.per) file.

For example:

!Custom_Order=Product;Customers;Channel;UnitsFlows
The following example specifies attributes for two accounts, AdminExpenses and
CapitalStock:

!MEMBERS=Account
AdminExpenses;EXPENSE;N;Y;Y; ;AllCustom3;AllCustom1;AllMarket;AllFlows;2;N;Y;Y;Y;Y;
;
; ; ; ; ;N;DefaultParent=NetIncome
CapitalStock;LIABILITY;N;Y;N; AllCustom3;[None];AllMarket;AllFlows;6;N;Y;Y;Y;Y;
; ; ; ; ; ;N;DefaultParent=TotalEquity;English=Capital Stock

Scenario
Syntax for Scenario dimension members:

'Label, DefaultFreq, DefaultView, ZeroViewForNonadj, ZeroViewForAdj,

ConsolidateYTD, UserDefined1, UserDefined2, UserDefined3,
SupportsProcessManagement, SecurityClass, MaximumReviewLevel, UsesLineItems,
EnableDataAudit, EnableJournalsAutoLabel, DefFreqForPostingFlowTrans,
DefaultParent, Descriptions
See Defining Scenario Members.

The following example specifies attributes for two scenarios, Actual and Budget:

!MEMBERS=Scenario
Actual;MTD;Periodic;Periodic;Periodic;N; ; ; ;N; ;10;Y;N;N;MTD ;DefaultParent=#root
Budget;MTD;Periodic;Periodic;Periodic;N; ; ; ;Y; ;10;Y;N;N;MTD ;DefaultParent=#root

Entity
Syntax for Entity dimension members:

'Label, DefCurrency, AllowAdjs, IsICP, AllowAdjFromChildren, SecurityClass,

UserDefined1, UserDefined2, UserDefined3, HoldingCompany, SecurityAsPartner,
DefaultParent, Descriptions
See Defining Entity Members.

The following example specifies attributes for three entities, California, Canada,
and Connecticut:

!MEMBERS=Entity
California;USD;Y;Y;Y;US;;;;;;DefaultParent=Imbler;English=State of
California;French=California

Canada;USD;Y;N;N;;;;;;;DefaultParent=Regional

Connecticut;USD;Y;Y;N;US;Northeast;;;;;DefaultParent=Imbler

Custom
Syntax for Custom dimension members:

'Label, IsCalculated, SwitchSignForFlow, SwitchTypeForFlow, UserDefined1,

UserDefined2, UserDefined3, SecurityClass, DefaultParent, Descriptions
See Defining Custom Members.

The following example specifies attributes for members of the Custom3 dimension:

!MEMBERS=Customers
[None];N;N;N;;;;;DefaultParent=#root
AllCustomers;Y;N;N;;;;;DefaultParent=#root
Customer2;N;N;N;;;;;DefaultParent=AllCustomers
Customer3;N;N;N;;;;;DefaultParent=AllCustomers
Customer4;N;N;N;;;;;DefaultParent=AllCustomers
Customer5;N;N;N;;;;;DefaultParent=AllCustomers

Value
You can use the members section to define descriptions for system-defined members
of the Value dimension. In addition, for Value dimension members that the system
creates for currencies, you can define descriptions that will be appended to the
currency descriptions.

Syntax for Value members:

Label;Descriptions
You can specify the label of a system-defined Value member. You also can use these
labels to create descriptions that are appended to the descriptions for the
corresponding Value members that the system creates for user-defined currencies:

<Currency Total>
<Currency Adjs>
<Currency>
For example, suppose that you define the currencies USD and EUR with descriptions
of �US Dollars� and �Euro,� respectively. In addition, suppose you define these
Value member descriptions in a loaded metadata file:

[None];English=ValueNone
<Currency Total>;English=Total
<Currency Adjs>;English=Adjs
<Currency>;English=Base
Table 17 describes the Value dimension member triplets that the system creates for
the USD and Euro currencies.

Table 17. Value Dimension Descriptions

Value Member | Description

USD Total | US Dollars Total

USD Adjs | US Dollars Adjs

USD | US Dollars Base

EUR Total | Euro Total

EUR Adjs | Euro Adjs

EUR | Euro Base

Note:
The metadata file must have a description specified for the Value member
<Currency>. If descriptions for currencies are not specified in the metadata file,
when you load metadata, the currency descriptions are not displayed.

Intercompany Partner
You can use the members section to define security classes and descriptions for
these system-defined members of the Intercompany Partner dimension:

[ICP Top]

[ICP None]

[ICP Entities]

Syntax for Intercompany Partner members:

Label;SecurityClass;Descriptions
This example shows how to define descriptions for [ICP Top], [ICP None], and [ICP
Entities] without specifying security classes:

[ICP Top];;English=Top ICP

[ICP None];;English=No ICP
[ICP Entities];;English=Entities ICP
Consolidation Methods
This section of a metadata file defines the consolidation methods.

Syntax for consolidation methods:

Label;UsedByCalcRoutine;IsHoldingMethod;ToPercentControlComp;
ToPercentControl;PercentConsol;Control;Descriptions
See Defining Consolidation Methods.

This example specifies attributes for consolidation methods:

!CONSOLIDATION_METHODS
M2;Y;N;<=;20;0;No
M3;Y;N;<;50;POWN;Limited
M4;Y;N;<=;50;50;Limited
M1;Y;Y;<=;100;100;Full
M5;Y;N;<=;100;100;Full