|
Plan Name
|
Up to eight characters.
There are six plan types available in Planning (across various applications): Plan1, Plan2, Plan3, Workforce, Capital Asset, and HCP. However, the total number of plan types for a given application cannot exceed five.
Plan1, Plan2, and Plan3 are standard plan types that are available for all Planning applications.
Standard Planning applications can use these additional modules: Workforce and Capital Asset.
Public Sector Planning and Budgeting applications can use one additional module: HCP.
Note:
Public Sector Planning and Budgeting does not support Workforce Planning or Capital Asset Planning, so if you use those modules, set them up as separate applications.
For Workforce Planning and Capital Asset Planning, see the Oracle Hyperion Workforce Planning Administrator's Guide and Oracle Hyperion Capital Asset Planning Administrator's Guide. For Public Sector Planning and Budgeting, see the Oracle Hyperion Public Sector Planning and Budgeting User's Guide.
Default Value: Plan1: True, Plan2: True, Plan3: True, Wrkforce: False, Capital Asset: False, HCP: False
|
Plan1Name, Plan2Name, Plan3Name, PlanWrkforceName, PlanCapexName, PlanHCPName
|
|
Valid For Plan
|
The standard Planning application has up to three plan types.
For Workforce Planning and Capital Asset Planning, see the Oracle Hyperion Workforce Planning Administrator's Guide and Oracle Hyperion Capital Asset Planning Administrator's Guide.
An Essbase database is created for each plan type. As you create accounts, entities, and other dimensions, you associate them with plan types, so the database for each plan type contains only the dimensions, members, and data values relevant to that plan type. This allows for optimal application design, size, and performance. You must set up at least one plan type. (The number of plan types depends on the needs of your organization.) You cannot reduce the number of plan types or change the plan type names after you create the application.
Caution!
Deselecting a plan type for dimension members after data is entered into applications may result in loss of data when applications are refreshed. For Account members, data is lost if the deselected plan type is the source plan type.
Plan types are inherited from parents to child members. If you select a different plan type for a parent member, all descendant members in that hierarchy are also updated. To set a different plan type for certain members, select them individually and set a different property.
Note:
When you define the value for this property at the parent level, all descendants automatically inherit the value. If the value is overridden for a descendant member of the original parent, its own descendants inherit the new value.
This property value is a relationship value. If you make changes to this value, it is not automatically changed for the members in other hierarchies.
Default Value: Plan1: True, Plan2: True, Plan3: True, Wrkforce: False, Capital Asset: False
|
AppValidForPlan1, AppValidForPlan2, AppValidForPlan3, AppValidForWrkforce, AppValidForCapex
|
|
Date Format
|
Set the date format as MM-DD-YYYY or DD-MM-YYYY.
Default Value: MM-DD-YYYY
|
DateFormat |
|
Default Currency
|
This is the default currency for the application and application entities.
Default Value: N/A
|
DefaultCurrency |
|
Multiple Currencies
|
Indicates that the application supports multiple currencies. Once specified, this cannot be changed. A Currency dimension is required. Multiple currency support is available for level 0 members, regardless of base currency.
Performance Management Architect does not create Currency dimensions automatically. HSP_Rates is created during Planning application creation for multi-currency applications; it is not defined in Performance Management Architect. HSP_Rates is available in the Performance Settings dialog box to tune Planning application performance.
Default Value: True
|
MultiCurrency |
|
Base Time Period
|
Defines the bottom-level time period in the application to set how calendars roll up. Select the appropriate value for the Period dimension structure:
Default Value: 12 months
|
BaseTimePeriod |
|
Weeks
|
Pattern for fiscal weeks in a month: Even, 445, 454, or 544. Sets how data entered into a summary time period spreads among base time periods.
If you select a weekly pattern other than Even, Planning treats quarterly values as if they were divided into 13 weeks, and distributes the weeks according to the selected pattern.
Weekly patterns are available only after selecting the base time period option 12 Months.
Default Value: Even
|
WeeksDistribution, WeeksDistributionMember |
|
Fiscal Start Year
|
The fiscal start year for the application. Fiscal Start Year uses a four digit year format, such as 2008 or 2009. Do not change this setting after creating the application.
Default Value: N/A
|
AppStartYear |
|
Fiscal Year First Month
|
The fiscal year start month for an application that has a Base Time Period set to 12 Months. For other Base Time Period types, this field is not relevant. Do not change the Fiscal Year First Month for the application after it has been deployed.
Default Value: N/A
|
StartMonth |
|
Default Alias Table
|
Required for each application. If other alias tables are not created, aliases are stored in the Default table (which cannot be deleted). You can create up to nine additional alias tables.
To create alias tables in Performance Management Architect, create a dimension of type Alias, and create a child member named Default. This member is the default alias table required by Planning and Essbase. You can create additional alias tables by adding child members to the Alias dimension. Create dimension associations to associate the Alias dimension to the main or base dimension, such as Account, Entity, or a user-defined dimension. You can change the default alias table by selecting the Alias dimension and changing the Default Member property in the System category.
Default Value: default
|
DefaultAliasTable |