Before redeploying, be sure the properties are correct and meet your needs. If applications are not set up correctly, deployment fails and error messages are displayed. After a Planning application is deployed, you cannot change these properties:
Whether the application uses a single currency or multiple currencies. For example, after you deploy with Multiple Currency selected, you cannot later clear Multiple Currency to use a single currency. Likewise, with a single-currency application, you cannot later select Multiple Currency.
The default application currency. For example, if you use USD, you cannot later change it to EUR.
The type of calendar. For example, if you set Base Time Period to 12 Months, you cannot later change it to Quarters.
The fiscal start month. After you set the Start Month, you cannot change it.
The start year. For example, if you set the Start Year to 2010, you cannot change it to 2009. You can, however, add years after the first year.
Any years added. After years are added, you cannot remove them. For example, if the deployed application includes FY09, you cannot remove this year.
The Weeks Distribution pattern. For example, if you set Weeks Distribution to 445, you cannot later change it to 544 or Even.
The plan types that are contained in the application. For example, if you deploy an application with plan types Plan1 and Plan2 selected, you cannot later add Plan3 or remove Plan2 from this application. You can change the Valid for Plan type for dimension members at any time. However, you cannot change the plan types contained in the application after deployment.
Dimensions added. You can add dimensions up to a total of twenty, including the predefined dimensions. You can rename dimensions, by changing the dimension alias, but you cannot delete them. See Setting the Dimension Alias.
Predefined dimensions. You cannot delete the predefined dimensions. Single-currency applications require these dimensions: Scenario, Version, Entity, Account, Period, and Year. Multiple-currency applications require these dimensions: Scenario, Version, Entity, Account, Period, Year, and Currency.
|
Caution! |
Each data value in Planning is identified by a set of dimension members and a plan type. Excluding dimension members from an application can translate to a delete action on deployment. For information, see Excluding and Deleting Planning Members. |
|
Note: |
For information on applications enabled 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 information on Public Sector Planning and Budgeting, see the Oracle Hyperion Public Sector Planning and Budgeting User's Guide. |
Before excluding members from an application or deploying to Planning, use the Show Usage feature within Planning to determine where members are used in the application and the implications of excluding dimension members from the application on deployment. For information about the Show Usage feature, see the Oracle Hyperion Planning Administrator's Guide.