Vous êtes sur la page 1sur 56

ORACLE HYPERION PLANNING

Release 11.1.2.3.000

Readme

CONTENTS IN BRIEF

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
New Features in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported Paths to this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Migration and Application Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Defects Fixed in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Accessibility Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Purpose
This document includes important, late-breaking information about this release of Oracle
Hyperion Planning. Review this Readme thoroughly before installing Oracle Enterprise
Performance Management System.

New Features in this Release


See the Oracle Hyperion Planning New Features. For new features relating to installation,
architecture, and deployment changes in this release, see New Features in this Release in the
Oracle Enterprise Performance Management System Readme.

Installation Information
Late-breaking information about the installation of EPM System products is provided in the
Oracle Enterprise Performance Management System Installation and Configuration Readme.
Review this information thoroughly before installing EPM System products.

Supported Platforms
Information about system requirements and supported platforms for EPM System products is
available in spreadsheet format in the Oracle Enterprise Performance Management System
Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System
Configurations page on Oracle Technology Network (OTN):
http://www.oracle.com/technetwork/middleware/ias/downloads/fusioncertification-100350.html

Supported Languages
Information about supported languages for EPM System products is available in a spreadsheet
format on the Translation Support tab in the Oracle Enterprise Performance Management System
Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System
Configurations page on OTN:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusioncertification-100350.html

Supported Paths to this Release


You can upgrade to EPM System Release 11.1.2.3 from the following releases:

Readme

Note: For upgrading instructions, see the Oracle Enterprise Performance Management System

Installation and Configuration Guide, Upgrading EPM System Products.


Table 1

Supported Paths to this Release

Release Upgrade Path

To Release 11.1.2.3

11.1.2.x

Apply the maintenance release to Release 11.1.2.3.


For Oracle Hyperion Financial Close Management, applying the maintenance
release is supported only from Release 11.1.2.1 and 11.1.2.2.

11.1.1.4.x

Upgrade to Release 11.1.2.3.

Release 11.1.1.0.x to 11.1.1.3.x

Apply the maintenance release to Release 11.1.1.4 and then upgrade to Release
11.1.2.3.

Release 9.3.3.x

Upgrade to Release 11.1.2.2 and then apply the maintenance release to Release
11.1.2.3.

An environment that includes multiple releases,


which can include an environment with one instance
of Oracle Hyperion Shared Services or an environment
with two instances of Shared Services

See "Upgrading from an Environment with Multiple Releases" in the "Upgrading


EPM System Products" chapter in the Oracle Enterprise Performance Management
System Installation and Configuration Guide.

Note: If you are starting from Release 9.2.0.3+, 9.3.0.x, 9.3.1.x (except Oracle Essbase 9.3.1.4.1,

9.3.1.5, 9.3.1.6, and 9.3.1.7), or 11.1.1.x, Oracle recommends that you first upgrade to
Release 11.1.1.3, apply the maintenance release to Release 11.1.1.4, and then upgrade to
Release 11.1.2.3. If you are starting from an earlier release, upgrade to the highest level
release that is directly supported.
Security Synchronization between Essbase and Shared Services was removed in Essbase Release
9.3, starting with Release 9.3.1.4.1. Essbase and Oracle Hyperion Shared Services Release 11.1.1.3,
however, still synchronize security information. For this reason, if you are using Essbase Release
9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, then
upgrade to Release 11.1.2.2, and then apply the maintenance release to Release 11.1.2.3.

Readme

Migration and Application Updates


Subtopics
l
l
l
l

Migrating Business Rules to Calculation Manager Rules


Upgrading Public Sector Planning and Budgeting 11.1.2.x Applications
Upgrading Project Financial Planning Release 11.1.2.2.30x Applications
Upgrading Predictive Planning Release 11.1.2.2.000 Applications

Migrating Business Rules to Calculation Manager Rules


Because Oracle Hyperion Business Rules is no longer available, if you are applying the
maintenance release or upgrading to Release 11.1.2.3, and if you have been using Business Rules
in an earlier release, you must migrate to Oracle Hyperion Calculation Manager rules in Release
11.1.2.3. See Business Rules Maintenance Release and Upgrade Installation Prerequisites in
the Oracle Enterprise Performance Management System Installation and Configuration Guide for
prerequisites you must complete before you install and configure in order to successfully migrate
business rules to Calculation Manager rules.

Upgrading Public Sector Planning and Budgeting 11.1.2.x


Applications
Subtopics
l
l

Before You Begin


Performing the Migration

Before You Begin


Subtopics
l
l
l

Requirements
About Migrating Artifacts and Data
Options and Considerations

To upgrade from 11.1.2.1, you must first upgrade to 11.1.2.2 as described in the Oracle Enterprise
Performance Management System Installation and Configuration Guide, and then perform the
business artifact update tasks provided in the Planning 11.1.2.2 Readme.
Before upgrading a 11.1.2.x (11.1.2.1 or 11.1.2.2.x) application to this release, perform these
steps:
l

Read the following sections to familiarize yourself with the process beforehand.

Create a test environment that is identical to your existing production environment.

Perform the upgrade steps on your test environment first. Once you confirm that everything
is working as expected on the test environment, then repeat the steps on your production
Readme

environment. Some steps may not be required based on the release of your existing
application.
l

If you customized your applications by modifying predefined rules, make a backup copy of
your changes to which you can revert if necessary.
New features such as decision packages and PeopleSoft commitment control integration
functionality are enabled only during application creation. If your application was created
earlier than release 11.1.2.2, these features will not be enabled during upgrade. You will need
to create a new application and import your existing content and modifications to take
advantage of the new features.

Requirements
Before running the Upgrade Wizard during installation, perform these tasks:
Note: Perform these steps on your test environment first. Once you confirm that everything is

working as expected on the test environment, then repeat the steps on your production
environment. Some steps may not be required based on the release of your existing
application.
1. Ensure that you can log on to the Oracle Hyperion Shared Services Console using an account
enabled for Oracle Hyperion Enterprise Performance Management System Lifecycle
Management tasks.
2. Ensure that you can log on to Oracle Hyperion Enterprise Performance Management
Workspace as a Oracle Hyperion Financial Reporting administrator.
3. Upgrade Planning to Release 11.1.2.3 as described in the Oracle Enterprise Performance
Management System Installation and Configuration Guide and Managing Upgrades in the
Oracle Hyperion Planning Administrator's Guide.
4. Update references to rehosted data sources (relational databases and Essbase servers). See
Managing Upgrades in the Oracle Hyperion Planning Administrator's Guide.
5. After installing the 11.1.2.3 release, create a 11.1.2.3 Oracle Hyperion Public Sector Planning
and Budgeting application as follows so that the application is identical to the 11.1.2.2. test
application:
Note: In the following steps, Application A refers to your existing 11.1.2.2 application and

Application B refers to the application you create after applying the 11.1.2.3 release.
When creating Application B, perform these steps so that Application B is identical
to Application A.

If you are migrating from 11.1.2.2 and your existing Application A is enabled for
Decision Package and Commitment Control, use the same option when creating
Application B.
Use the same configuration option.

Readme

Use the same currency options.


Use the same calendar definition (application start year and number of years, for
example).
Note: If your existing Application A uses Business Rules as the calculation module,

migrate all applications from Business Rules to Calculation Manager as described


in the Oracle Enterprise Performance Management System Installation and
Configuration Guide. You must perform this step before continuing with the
update.
6. Launch Planning11.1.2.3, open Application A, and then click Upgrade. This performs the
required schema upgrade.

About Migrating Artifacts and Data


The following is an overview of the tasks required to migrate data and artifacts from the test
Application B to Application A. Perform these tasks in the order listed here:
l

Meet the requirements. See Requirements on page 5.

Migrate your Smart List metadata. See Migrating Smart List Metadata on page 8

If necessary, modify the dimension metadata in the existing Application A using Planning
or Oracle Hyperion EPM Architect as described in Migrating Dimensional Metadata on
page 8.
Note: Performance Management Architect is not supported for decision packages.

Migrate your artifacts and data. See Performing the Migration on page 8
Migrate business rules using Calculation Manager. See Migrating Business Rules on page
9
Migrate substitution and user variables, forms, smart lists, menus, reports, and task lists
using Lifecycle Management in the Shared Services Console as described in the following
sections.
Perform the post migration tasks. See Post Migrating Tasks on page 10.
Verify the migrated data, and then use the same procedure to migrate the 11.1.2.2 production
environment.

Options and Considerations


Migrate your existing Public Sector Planning and Budgeting metadata and data based on your
situation.
Note: Support for decision packages and PeopleSoft Financials Commitment Control

introduced in 11.1.2.2 are available only for new applications; these features are not
supported for existing 11.1.2.1 applications.

Readme

If you want to acquire only the updated business logic in 11.1.2.3.000, do not want to update
forms, reports, or tasks in the application, and haven't customized your existing application,
perform the tasks in these sections in this order:
m

Migrating Smart List Metadata on page 8

Migrating Dimensional Metadata on page 8

Migrating Business Rules on page 9

If you did not customize your existing application, and you want to acquire all new
functionality, perform the tasks in these sections in this order:
m

Migrating Smart List Metadata on page 8

Migrating Dimensional Metadata on page 8

Migrating Business Rules on page 9

Migrating Forms, Menus, Reports, and Task Lists on page 10

If you modified the dimensionality and artifacts in your existing application, and want to
acquire all new functionality, perform the tasks in these sections in order:
m

Create a copy of the artifacts that you modified using the "Save As" functionality. This
ensures that you have a copy of all artifacts. If you saved modified artifacts using a new
name, they are not overwritten.

Migrating Smart List Metadata on page 8

Migrating Dimensional Metadata on page 8

Migrating Business Rules on page 9

Migrating Forms, Menus, Reports, and Task Lists on page 10

Reinstate the artifacts that you copied to restore your changes.


Caution!

If you want to keep the changes from the predefined application for artifacts
that were brought into the 11.1.2.2 test application, then skip this step for
those artifacts; alternately, you can merge your changes as you deem
necessary.

Readme

Performing the Migration


Subtopics
l
l
l
l
l

Migrating Smart List Metadata


Migrating Dimensional Metadata
Migrating Business Rules
Migrating Forms, Menus, Reports, and Task Lists
Post Migrating Tasks

Migrating Smart List Metadata


The following procedure applies to applications that use Planning application administration.
If you use Performance Management Architect to manage applications, refer to the Oracle
Enterprise Performance Management System Lifecycle Management Guide to migrate Smart Lists,
and then redeploy the application to Planning.
Note: Decision packages are not supported with Performance Management Architect.

To migrate smart list metadata


1. Log on to the Shared Services Console as an administrator.
2. Expand Application Groups, and then select Application B.
3. Select Application, then Global Artifacts, then Smart Lists.
4. Select Operation_Status and Allocation Options
5. Click Export, and then export the artifacts to the file system by specifying the appropriate
folder.
6. Import the Smart Lists data set to Application A.

Migrating Dimensional Metadata


If the application was not using Performance Management Architect, perform these tasks :
l

Run PSBAppUpgradeUtility.bat <arg1> <arg2> <arg3> <arg4> <arg5>


<arg6>, in which:
m

<arg1>Planning server

<arg2>Application

<arg3>Administrative user who created the Planning application

<arg4>Directory for the encrypted password file

<arg5>Directory and file in which to create the log file

<arg6>Directory in which to create the error file

Readme

Note: After running PSBAppUpgradeUtility.bat, ensure that Baseline Revision

Request and Current Service level are the immediate child members under the
Total Request member in the request dimension. If not, move these two members
so they are the first children under Total Request.
If the application was created using Performance Management Architect, perform these tasks
Note: Decision packages are not supported with Performance Management Architect.

1. In Performance Management Architect, open the Dimension Editor.


2. Create or copy Allocation Options and Operation Status.
3. In the Budget Item dimension, add a member called Percentage Allocation Assignments.
4. Move the existing members under Allocation Assignments (1st Allocation, 2nd Allocation
etc.) under Percentage Allocation Assignment
5. Create a member called Flat Allocation Assignments, and make it a sibling with Percentage
Allocation Assignments.
6. Add 25 members to support your flat allocations, below Flat Allocation Assignments.
7. In the Account dimension, add a Dynamic Calc Member called Union under Element
Properties.
8. Copy the formula used by the same dynamic calc member in Application B, and use it as
the formula for the new member you created. If you use the Position and Employee budget
detail or the Position Budget Detail, add a dynamic calc member called Job Code and make
the formula used by this member in Application B the member formula.
9. Add a Dynamic Calc Member called Location under Element Properties and copy the formula
used by this member in Application B.
10. Add these members to Allocation Information:
l

Allocated Flat Amount,

Allocated Benefits

Allocated Taxes

Allocated Taxable Benefits

11. Change the smart list dimension associated to the Follow Salary Allocation member to the
Allocation Options member.
12. Add a UDA called HSP_NOLINK to the Revision Amount member.

Migrating Business Rules


To migrate business rules:
1. Make and maintain a copy of business rules that you may have modified, such as those used
in General Ledger allocations.

Readme

2. Log on to EPM Workspace, select Administer, and then select Calculation Manager.
3. Expand Planning, select the Application A test application, and then right-click.
4. Select Load Predefined Rules.
5. Right-click Application A again, and then select Deploy.

Migrating Forms, Menus, Reports, and Task Lists


1. Satisfy the requirements. See Requirements on page 5
2. Migrate composite forms, menus, task lists, forms, data load settings, and user variables
from Application B to Application A as follows:
l

Log on to the Shared Services Console Shared Services Console as an administrator.

Expand Application Groups, and then select Application B.

Expand Configuration, and then select Data Load Settings and User Variables.

Select Application, then Global Artifacts, then Substitution Variables

Expand Global Artifacts, and then select:


m

Composite forms

Custom menus

Task Lists

3. Expand Plan Type, expand HCP, and then select Data Forms.
4. Select Export, and then export the artifacts to the file system by specifying the appropriate
folder.
5. Import the exported application data set into the Application A.
6. Export the reports from Application B as follows:
l

Log on to EPM Workspace as a Financial Reporting administrator.

Click Explore and navigate to Application B.

Select Human Capital Planning, then select File, and then select Export.

Export all the reports into a .zip file, overwriting the existing reports.

7. After importing all reports, select Tools, then Change Database Connection, select the reports,
click OK, and then select the new database connection.

Post Migrating Tasks


After migration, perform these tasks:
1. Log on to the Public Sector Planning and Budgeting Application A to confirm that the
migrated task lists, forms, and custom menus display.
2. Select Administration, then Application, and then Refresh Database.
3. Select Database, select Update custom-defined functions, and then click Refresh.

10

Readme

4. Select Administration, then Manage, then Variables and then select Substitution Variables.
5. Set values as appropriate to your budget period in Compensation_Budget_Start_Year and
Compensation_Budget_End_Year.
6. To accommodate any data changes, perform these tasks:
l

To recalculate compensation budgets, for every combination of scenario and version


where you have data, recalculate compensation budgets for Total Entity.
For every combination of scenario and version where you have data, allocate modified
compensation expenses to General Ledger accounts for Total Entity, All Positions, and
Total Employees. Use the mapping reporting application functionality to push the newly
allocated data to the Line Budget cube.

7. Repeat this procedures to migrate metadata and data from the test environment to your
production environment.

Upgrading Project Financial Planning Release 11.1.2.2.30x


Applications
Subtopics
l
l
l

Before You Begin


Performing the Migration
Post Migration Tasks

Before You Begin


Before upgrading your existing 11.1.2.2.30x applications to this release:
l

Read the upgrade sections which enable you to familiarize the process beforehand.

Create a test environment that is identical to your existing production environment.

Perform all the upgrade steps on a test environment first.

Understand that some steps may not be required based on the release of your existing
application.
If you customized your applications by modifying predefined rules, member formula, and
so on, make a backup copy of your changes to which you can revert if necessary.

Readme

11

Performing the Migration


Subtopics
l
l
l
l
l
l

Migrating Data and Artifacts


Migrating Smart List Metadata
Migrating Dimensional Metadata
Migrating Business Rules
Migrating Forms, Menus, Reports, and Task Lists
Migrating Data

Migrating Data and Artifacts


Subtopics
l
l

Prerequisites
Options and Considerations

This section provides an overview of the tasks required to migrate the artifacts from an
11.1.2.3.000 New Application to a 11.1.2.2 Test Application.
l

Ensure you meet the requirements as described in Prerequisites on page 12.


Migrate Smart Lists using Lifecycle Management in Shared Services Console as described in
Migrating Smart List Metadata on page 14.
Migrate dimensional metadata using Dimension Editor and Lifecycle Management in
Shared Services Console as described in Migrating Dimensional Metadata on page 14.
Migrate business rules using Calculation Manager as described in Migrating Business
Rules on page 15.
Migrate forms, menus, reports, and task lists using Lifecycle Management in Shared Services
Console as described in Migrating Forms, Menus, Reports, and Task Lists on page 16.
Perform post migration tasks such as refreshing the application as described in Post
Migration Tasks on page 18.
Verify the migrated data, and then use the same procedure to migrate the 11.1.2.2 production
environment.

Prerequisites

Before running the Upgrade Wizard during installation, perform these tasks:
1

Create a Release 11.1.2.2 test environment that is identical to your 11.1.2.2.30x production
environment.
l

12

Ensure that you can log on to Shared Services Console using an account enabling
Lifecycle Management tasks.
Ensure that you can log on to EPM Workspace as an Financial Reporting administrator.

Readme

On the 11.1.2.2 test environment you created in step 1, upgrade Planning to Release 11.1.2.3 as
described in the Oracle Enterprise Performance Management System Installation and Configuration
Guide and in the Managing Upgrades section in the Oracle Hyperion Planning Administrator's
Guide.

Update references to rehosted data sources (relational databases and Essbase servers). See "Managing
Upgrades" in the Oracle Hyperion Planning Administrator's Guide.

On the upgraded environment, create a Release 11.1.2.3 Oracle Project Financial Planning application.
Copy the 11.1.2.3 artifacts from the newly created 11.1.2.3 application to the existing 11.1.2.2.30x
application. When creating the 11.1.2.3.000 New Application, perform these steps so that it is identical
to 11.1.2.2 Test Application, as follows:
l

Use the same currency options


Have the same calendar definition (application start year and number of years, for
example)

Launch Planning Release 11.1.2.3, open the 11.1.2.2 Test Application, and then click Upgrade. This
step performs the required schema upgrade to make the application valid for Release 11.1.2.3.

Options and Considerations


Migrate your existing release Project Financial Planning metadata and data based on your
situation:
l

Situation 1: Updating Only the Business Logic to an Uncustomized Application


If you want to update the business logic and do not want to update forms, reports, or tasks
in the application, and you have not customized your 11.1.2.2.30x application, perform
these tasks in the following order:
1. Migrating Smart List Metadata on page 14
2. Migrating Dimensional Metadata on page 14
3. Migrating Business Rules on page 15
4. Migrating Data on page 17

Situation 2: Updating All of the New Functionality to an Uncustomized Application


If you want all of the new functionality in Release 11.1.2.3, and you have not customized
your 11.1.2.2.30x application, perform these tasks in the following order:
1. Migrating Smart List Metadata on page 14
2. Migrating Dimensional Metadata on page 14
3. Migrating Business Rules on page 15
4. Migrating Forms, Menus, Reports, and Task Lists on page 16
5. Migrating Data on page 17

Situation 3: Updating All of the New Functionality to a Customized Application


You want all of the new functionality in Release 11.1.2.3. You have modified the 11.1.2.2.30x
application's dimensionality and artifacts for a custom implementation. If you have
modified any artifact (for example, forms, reports, and business rules) and if you did not

Readme

13

save them in the predefined Release 11.1.2.2 Test Application, then create a copy of the
artifacts that you previously modified (for example, using Save As functionality). This
ensures that you have a copy of all artifacts. If you changed artifacts that you copied, the
artifacts are not overwritten. Perform these tasks in the following order:
1. Migrating Smart List Metadata on page 14
2. Migrating Business Rules on page 15
3. Migrating Forms, Menus, Reports, and Task Lists on page 16
4. Migrating Data on page 17
5. Reinstate the artifacts that you copied to restore your changes.
Caution!

If you want to keep the changes from the predefined application for artifacts that
were brought into the 11.1.2.2 Test Application, then skip this step for those
artifacts; alternately, you can merge your changes as you deem necessary.

Migrating Smart List Metadata


To migrate Smart List metadata:
1

On the 11.1.2.3 test environment, log on to Shared Services Console as an administrator.

Expand Application Groups, and then select the new 11.1.2.3 application in the 11.1.2.3 test
environment.

Select Application, then Global Artifacts, then Smart Lists, and then select the following Smart Lists:
l

ApprovalCriteria

MethodSpread

SetTarget

ShiftProjectDates

TargetSpreadLogic

Click Export, and then export the artifacts to the file system by providing the folder name.

Import the exported 11.1.2.3 application's Smart Lists data set (that you exported in step 4) into the
11.1.2.2 Test Application.

Migrating Dimensional Metadata


This procedure applies only to applications that use Planning application administration
(formerly called Classic application administration).

To migrate dimensional metadata:


1

Log in to the 11.1.2.2 Test Application. Go to the Dimension Editor.

Perform the following changes within the Account dimension:


l

14

Rename Labor Expense - Non Billable to Labor Expense - Nonbillable

Readme

Rename Equipment Expense - Non Billable to Equipment Expense - Nonbillable

Rename Subcontracts - Non Billable to Subcontracts - Nonbillable

Rename Other Expenses - Non Billable to Other Expenses - Nonbillable

Rename Asset Expenses - Non Billable to Allocated Asset Expenses - Nonbillable

Rename Total Number of Employees to Total Labor Resources

Log on to Shared Services Console as an administrator.

Expand Application Groups, and then select a new 11.1.2.3 application.

Expand Configuration, and then select Data Load Settings and Substitution Variables.

Expand Global Artifacts, select Common Dimensions, and then select Standard Dimensions. Select
the following dimensions:
l

Account

Project

Version

Scenario

Expand Plan Type, select Project, then select Standard Dimensions, and then select Project
Element.

Click Export, and then export the artifacts to the file system by providing the folder name.

Import the exported 11.1.2.3 application data set (that you exported in step 8) into the 11.1.2.2 Test
Application.

10 In the Job dimension, add the member Unspecified Job directly under Total Jobs with the following
properties:
l

Data Storage: Store

Aggregation: Set this as Addition for Wrkforce plan type

Data Type: Unspecified

11 In the Employee dimension, move the member Unspecified Employee directly under Total Employees,
with the following properties:
l

Data Storage: Store

Aggregation: Set this as Addition for Wrkforce plan type

Data Type: Unspecified

12 In the Year dimension in the 11.1.2.2 Test Application, replace the member formula for the All Years
member from 11.1.2.3 Application.

13 Refresh the cube.

Migrating Business Rules


To migrate business rules:
1

Log on to EPM Workspace.

Readme

15

Select Administer, and then Calculation Manager.

Expand Planning.

From the list of applications, select the 11.1.2.2 Test Application.

Make and maintain a copy of business rules that you may have modified.

Right-click the 11.1.2.2 Test Application, and then click Load Predefined Rules.

Right-click the 11.1.2.2 Test Application again, and then click Deploy.

Migrating Forms, Menus, Reports, and Task Lists


To migrate forms, menus, reports, and task lists:
1

Satisfy the requirements.

Migrate composite forms, menus, task lists, forms, data load settings, and user variables from the
11.1.2.3 application to the 11.1.2.2 Test Application:

a. Log on to Oracle Hyperion Shared Services Console as an administrator.


b. Expand Application Groups, and then select the new 11.1.2.3 application.
c. Expand Configuration, and then select Data Load Settings and Substitution Variables.
d. Expand Global Artifacts, and then select:
l

Composite forms

Custom menus

Task lists

e. Expand Plan Type, then expand Project, and then select Data Forms; expand Capex and
select Data Forms; expand Workforce and select Data Forms.
f.

Click Export, and then export the artifacts to the file system by providing the folder name.

g. Import the exported 11.1.2.3 application data set (that you exported in the previous
step) into the 11.1.2.2 Test Application.

Export the reports from 11.1.2.3 application:

a. Log on to EPM Workspace as a Financial Reporting administrator.


b. Click Explore.
c. Navigate to the 11.1.2.3 application.
d. Select Project Planning.
e. Select File, and then select Export.
f.

Export all the reports into a .zip file.

Import the reports into the 11.1.2.2 Test Application:

a. Log on to EPM Workspace as a Financial Reporting administrator.


b. Under the 11.1.2.2 application folder, select the Project Planning folder.
c. To preserve reports you changed, rename the reports.
16

Readme

d. Select File, then Import, and then select Financial Reporting Documents.
e. Import the reports you exported to a .zip file, overwriting the existing reports.
f.

To map the imported reports to the 11.1.2.2 Test Application data source, select Tools,
then Change Database Connection, and then select the reports, then click OK, and then
select the new database connection name.

g. Ensure that the data source for the reports Project Labor Expense and Project
Capitalized Labor Expense point to the Workforce cube of the 11.1.2.2 Test
Application.
h. Ensure that the data source for the report Project Equipment Expense points to the
Capex cube of the 11.1.2.2 Test Application.
i.

Ensure that the data source for all other reports points to the Project cube.

Migrating Data
To migrate data:
1

Login to 11.1.2.2 Test Application.

Navigate to Administration, select Manage, and then select Copy Data.

In the Copy Data screen under the Static Dimensions grid, select the required parameters as specified
in the following table:
Table 2

Copy Data Static Dimensions Parameters

Dimension

Members

Entity

ILvl0Descendants(Entity)

Scenario

ILvl0Descendants(Scenario)

Version

ILvl0Descendants(Working)

Project

ILvl0Descendants(Project)

Year

ILvl0Descendants(Year)

Currency

Local

Period

ILvl0Descendants(Period)

Project Element

ILvl0Descendants(Project Element)

Under the Dimensions with Source and Destination grid, select the required parameters as specified
in the following table:
Table 3

Copy Data Dimensions with Source and Destination Parameters

Dimension

Source

Destination

Account

Percentage Completion

% Complete

Readme

17

Post Migration Tasks


After migrating data, perform these tasks:
1

Log on to the Project Financial Planning 11.1.2.2 Test Application to confirm that the migrated task
lists, forms, and custom menus display.

Select Administration, then Application, and then Refresh Database.

Select Database, then select Update custom-defined functions, and then click Refresh.

Select Administration, then Manage, then select Variables, and then select the Substitution
Variables tab. Set the substitution variable values as per your requirements.

Repeat the preceding procedures to migrate metadata and data from the test environment to production.

Upgrading Predictive Planning Release 11.1.2.2.000


Applications
Predictive Planning 11.1.2.3.000 form level preferences are not backward compatible with
preferences created in Predictive Planning version 11.1.2.2.000. This is due to a change in the
format used for storing the preferences. This issue only occurs for Planning forms that have been
set up for Predictive Planning on Planning 11.1.2.2. When the server is migrated to a later version
(11.1.2.3), any Predictive Planning stored preferences will not be readable in the new version
and all form preferences will need to be reentered. It is possible that Oracle Hyperion Smart
View for Office will issue error dialogs when a form that had Predictive Planning 11.2.2.2 data
is opened in 11.1.2.3. These errors can be ignored.
To work around this issue, you must reconfigure the Predictive Planning application default for
new forms as well as individual preferences for each form after a migration. This can be done
by first setting the application default preferences. All forms will have the factory defaults after
a migration so you can either set the application defaults to the factory settings or change some
settings and then apply Excel, then Predict, then Set Up Data Form, and then Set Default. Then
re-enter the preferences for each form that had non-default settings by opening the form and
running Excel, then Predict, and then Set Up Data Form.

Prerequisites
Planning 11.1.2.3 requires the following patch applied before running Planning: Oracle
Application Development Framework (ADF): 16709748.
You can find patch 16709748 on the My Oracle Support site at http://support.oracle.com (user
name and password required).

18

Readme

Defects Fixed in this Release


Subtopics
l
l
l
l
l

Planning
Project Financial Planning
Public Sector Planning and Budgeting
Smart View
Lifecycle Management

This section includes defects fixed in Release 11.1.2.3.000. To review the list of defects fixed
between earlier releases, use the Defects Fixed Finder. This tool enables you to identify the
products you own and your current implementation release. With a single click, the tool quickly
produces a customized report of fixed-defect descriptions with their associated platforms and
patch numbers. This tool is available here:
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1

Planning
l

16037122 -- You cannot validate Planning scripts in Calculation Manager if the scripts refer
to the HSP_Rates dimension. If you use the Insert Member option in the script editor to try
to select HSP_Rates, you receive this error if you expand the dimension: "There is an
error processing the response.[object
com.hyperion.bpm.web.common.Response"

15942099 -- Business rules attached to composite forms that should run when the forms are
saved, do not save if the forms are associated (by menu) with the Data Collection form in
decision packages.
14832508 -- Because you can define row and column fetch parameters as part of user
preferences, you no longer wait for Planning to load dynamic form data.
14761766 -- When creating forms, dimensions that are applicable to your plan type, and
that should be displayed, do not display when you click Next on the Properties tab.
14745682, 14387053 -- Planning does not support forward slashes or backslashes in member
names.
14726855 -- Values that you enter in form cells do not display when you right-click to invoke
supporting details.
14723007 -- If you navigate between two forms that each have rules that run when the form
is saved, the rule associated for the first form you open runs when you open and then close
the second form.
14623875 -- You cannot use the Outline Load utility to load data if member names are
enclosed with parentheses ().
14589845 -- Custom members that you add to the HCP cube under Segment Information
are not used as expected by rules. When run the rules do not aggregate any data that exists
for these members.

Readme

19

20

14559126 -- When working with a member's attribute hierarchy, the right-hand panel may
not reflect the selections you make in the left hand panel.
14559099, 14615816 -- Account annotations that you enter on forms are saved to incorrect
intersections.
14552042 -- Even if supporting details are entered for a cell that is read-only, users can rightclick to view supporting details.
14473168, 13595884 -- When there are multiple segments on a row, you cannot Expand and
Collapse inner members.
14376244, 12422049 -- If it begins with zero, a member value that you enter in a form is not
saved correctly; the initial 0 does not display when you reopen the form.
14368144 -- Segments or chartfields that you manually add to allocations cannot be deleted.
The business rules that delete allocation information do not remove segments or chartfields
that you add.
14059986 -- In run time mode, only the first dimension displays on a row if Start
Expanded is disabled.
13889832 -- The current Planning ADF ODL log level NOTIFICATION:32 is impacting
Planning user interface performance and needs to be changed to WARNING:1. Also the
CSS/Registry ODL log levels need to be changed to WARNING:1 from NOTIFICATION:
32 to help overall Planning performance.
13879269 -- Ad hoc grids are not launched in a separate Analyze tab if they are created from
forms that were opened by selecting the Launch Tasklist Wizard icon.
13868533 -- If a Planner selects the Launch Tasklist Wizard icon before refreshing the screen,
an error occurs.
13868374 -- An ad hoc grid cannot be deleted or moved if using a different Web browser
than the browser in which it was created or invoked.
13867527 -- In Manage Approvals, clicking an action link for a planning unit node with a
secondary dimension causes an error.
13866265 -- Annotations added during decision package approvals are not being saved.
13857734 -- For accounts where Time Balance is set to Fill, if a child value changes, the
default aggregation logic is not applying up to its parent until the child value is changed
again.
13856610 -- When managing default compensation and there are multiple compensation
elements per category, only the default compensation that is last in the list for each category
is added to a new position.
13852525 -- You cannot modify cells in an ad hoc grid until the grid is refreshed by selecting
Refresh.
13848558 -- Non-owning (service provider) entities should not be allowed to reconcile a
project, however, Project Financial Planning allows them to do so.
13830589 -- The Drill Through command on a form's Edit menu does not work.

Readme

13830429 -- The Apply to all selected cells option does not work correctly when attaching
documents to a range of cells in a form. You will only see the attachment in the first cell
selected.
13722188 -- When entering a form cell that is in an editable mode, you must first click within
the cell before using Shift + End to clear it. You cannot double-click within a cell to fully
select it before clearing it nor can you move from one cell to another if cells have existing
values in them.
13644320 -- If you rename the Request dimension, when using Lifecycle Management, a
second Request dimension is created if you export a decision package-enabled application
and then try to import the application.
13615823 -- When selecting a non-English Planning application, an error occurs if you access
Planning Preferences using the File menu.
13500659, 14007131 -- Member names rather than aliases sometimes display on forms.
13491643 -- When you launch a business rule by right-clicking in a form, you must select
the budget request member by selecting a Dynamic User Variable. Instead, the budget
request member name should display.
13465212 -- To enter data in forms, you must click in cells twice (or press F2), which enables
data entry. Pressing Tab, Shift+Tab, Enter, or Shift+Enter puts the focus in the next or
previous cell or row, respectively. When focus is in a cell, data in the cell is selected, and if
you enter data directly, the earlier data is overwritten. To append data to an existing value,
press the End key, which puts the focus at the end of the field. Also, sometimes the page
selector icon is not visible.
13460103 -- When navigating away from a form by performing tasks such as selecting
another task list item or menu item, you are not prompted to save the form if you entered
or modified data.
13376907, 13262428 --The Web browser language setting overrides the EPM Workspace
locale setting. For example, if you set the Web browser to German, but set the EPM
Workspace locale to English, Planning incorrectly displays in German.
13371008 -- You cannot view all the dimensions to which you have access in ad hoc analysis.
13371002 -- If a user in a sequence is using rules with runtime prompts from another
application, upon sequence launch and invoking the member selector, the user might not
see the members. In other words, the member selector might be empty.
13256751 -- If you use Planning on a Russian locale and define the cell text limit using the
MAX_CELL_TEXT_SIZE parameter, the cell text limit is not correctly calculated and applied.
13099546 -- With Microsoft Internet Explorer 9, the Planning application wizard may
flicker.
13052075, 13446110 -- You cannot sort as expected in the Job Console. For example, you
cannot sort all jobs if the list spans multiple pages.
12997413 -- Selecting Tools, and then Export to Excel may generate an empty Microsoft Excel
workbook that contains only column headers.
12991887 -- Formatting you apply to cell text does not display after you save.

Readme

21

12981201 -- You cannot correctly sort by start time and end time on the Job Console page.
12866959 -- To enter data in the first cell on a form, you must double-click or press F2. To
enter data in the rest of the cells use the Tab key.
12833889 -- Approvals does not lock shared members, which enables users to enter data on
forms for which shared Scenario or Version dimension members are part of the form
definition.
12363328 -- Whenever Planning metadata changes, you must restart the Reporting server
to reflect the metadata change in Financial Reporting.
9497802 -- Resizing your Web browser display may cause problems with composite form
display.

Project Financial Planning


l

13732128 -- When viewing the 4.10 Review Construction in Progress (CIP) Assets form in
Project Financial Planning, you must make at least one dimension visible on the row header
or none of the data will display on the form.
13606962 -- Earned value analysis should be supported for projects.
12807571 -- If you import projects into Project Financial Planning and use Microsoft Excel
to edit the .CSV files used, dates are saved in mm/dd/yyyy format, which causes import
errors.
13582084 -- In Project Financial Planning, you cannot charge the costs from internal
Contract projects to Capital or Indirect projects. Intercompany functionality is supported
for Cost Plus Contract projects where the Revenue Cash Flow Incidence is set to Same
Month. For intercompany revenue calculations where the organization is a service provider,
the Cost Plus margin must be explicitly marked as 0% for cost-based settlements and greater
than 0% for cost plus-based settlements.
13626807 -- When adding an Other Contract project in Project Financial Planning, the
validation message you see if you select an option other than Monthly for revenue
recognition is in English only.
13869509 -- In the sample Project Financial Planning application, if you submit a plan for
approval while logged in as an asset manager, an error occurs. This error does not occur in
a basic Project Financial Planning application.

Public Sector Planning and Budgeting


l

22

16371049 -- The rollup definition is displaying incorrect dimensions if mapping is selected


in the Mapping tab.
16356358 -- After moving a budget request from decision package A to decision package
B, the Manage Decision Packages page is loaded causing you to lose the context.
16292266 -- It is required to have Unspecified Budget Item as the first member of the
Budget Item dimension. However, when loading position master data using Outline Load

Readme

utility, this member is moved to the bottom of the hierarchy. This can cause calculation
issues with FTE's.
l

14543467 -- Reverse transfers may not work correctly if adjustments are performed on the
same day as the reverse transfers are executed.
14538494 -- The Position Adjustment report does not display data for Unspecified Budget
Request.
14534927 -- You may lose assigned FTE values after you change the values for the
"Compensation_Budget_Start_Year' and 'Compensation_Budget_End_Year' substitution
variables and perform a Reset FTE and Status calculation.
14410245 -- When adding other compensation elements to positions by selecting Manage
compensation defaults, compensation elements are not added to a new position if the
element option start date occurs after the position start date.
14340834 -- You must double-click a decision package type twice to open it.
14070719 -- The run on save function may not work as expected for data forms attached to
budget requests.
13982781 -- For decision package-enabled budget requests, gross earnings and taxable
compensation may calculate incompletely on Edit Employee Details. To resolve this issue,
calculate compensation budgets from My Task Lists.
13903501 -- For Employee Only decision package-enabled budget requests, total taxes may
calculate incorrectly or not display.
13899540 -- For decision package- and business rule-enabled Public Sector Planning and
Budgeting applications, Annual Salary Spread Workdays or Paydays is not working as
expected.
13877081 -- Increment to Next Step does not increment the steps when incrementing is based
on the adjustment date in a decision package-enabled application.
13855699 -- On forms attached to budget requests in decision package-enabled Public Sector
Planning and Budgeting applications, when you save a value in any of the composite tabular
data forms, after save focus will come out of that form to first tab form. On forms attached
to budget requests in decision package-enabled Public Sector Planning and Budgeting
applications, when you save a value in edit mode in a data cell without tabbing away from
that cell, the value does not get saved even though the message says that the save was
successful.
13732681 -- Decision Package Types do not support composite forms.
13711165 -- For Decision Package Type Compensation Expenses, when you repeatedly
change the POV year in Manage Request Position-Employee Assignments, performance
issues occur and error messages are displayed.
13708903 -- In a decision package-enabled application, although the Terminate Employee
business rule launched from Employee Master Data completes successfully, neither the
Terminate Date is not displayed on the Employee Master Data form, nor is the employee
status set to Inactive. Terminate Employee should be launched only from Employee
Assignments forms with the Budget Request in which the Employee is assigned.

Readme

23

13708171 -- Although the budget request name should automatically display, it does not,
and you must select its corresponding member in the Request dimension when creating a
budget request in which you are adding new positions and defining their compensation.

Smart View
l

14461937 -- You may encounter errors launching rule sets in Smart View.

13360539 -- You cannot launch composite forms from Planning Web to Smart View.

13242100 -- In Smart View, data you enter in a Planning form and then try to submit
immediately after running a business rule fails, and you receive a The pages on the data form
have changed error.
13024793 -- You receive a Planning Provider Error when submitting forms in Smart View
after opening forms as .XLS files from your assigned task list.

Lifecycle Management
l

15986639 -- When using Lifecycle Management to migrate a Planning application from Dev
to Prod, the Display Option for the dimension (for example, Alias) is not retained.
13406410 -- After migrating using Lifecycle Management, the assignment of business rules,
attached to a form, to the correct plan type is lost and must be manually resolved. For
example, if business rules are assigned to a form associated with plan type 2, after migration
the business rules are drawn from plan type 1.
8597432 -- If you use Lifecycle Management to export forms on which a dimension row is
hidden, the hidden dimension is not visible in the generated XML file, but is visible in
Planning if you import the file.

Known Issues
Subtopics
l
l
l
l
l
l
l
l
l
l
l

Recommended Configuration for Optimizing Performance


Planning
Capital Asset Planning
Project Financial Planning
Public Sector Planning and Budgeting
Workforce Planning
EPM Workspace
Lifecycle Management
Performance Management Architect
Smart View
Web Browsers

The following are the noteworthy known issues of this release.

24

Readme

Recommended Configuration for Optimizing Performance


Subtopics
l
l
l
l

Internet Browsers
Server
Client
Client-to-Server Connectivity

This release includes a large number of user interface enhancements, as described in Oracle
Hyperion Planning New Features. To optimize performance with these new features, you must
implement the following recommended configuration.
The improved Planning user interface requires efficient browsers to handle interactivity
provided through Web 2.0 like functionality. In our testing, we found that Internet Explorer
(IE) 7, IE 8, and Firefox 3.x cannot typically handle such interactivity, and the responsiveness
and speed of these browser versions is not as good as with previous releases of Planning.
Consequently, Oracle strongly recommend that you upgrade your browser to IE 9 or Firefox 10
or later to achieve responsiveness similar to that in previous releases.
However, because response times in IE 7, IE 8, and Firefox 3.x are sometimes acceptable, Oracle
recommends that, if you wish to use these releases, you conduct an end user response test with
these browsers and that you are satisfied with browser performance before installing the new
user interface.
You can leverage the old user interface and features from Planning Release 11.1.2.1. For more
information, see Using the Planning Release 11.1.2.1 User Interface and Features in the Oracle
Hyperion Planning Administrator's Guide.

Internet Browsers
l

If you enabled ADF, you must use IE 9 in standard mode with this release of Planning.
Compatibility mode with IE 9 is not supported in this release if ADF is enabled.
This is the last release to support the Classic Planning 11.1.2.1 user interface if ADF is
disabled. Future releases will require that you enable ADF.
You cannot use IE 9 with release 11.1.2.1 of Classic Planning. Instead, use IE 9 with release
11.1.2.1.100 of Classic Planning.

Server
l

64-bit

16 GB physical RAM

Client
l

Optimized for IE 9 and Firefox 10 or later

Readme

25

Client-to-Server Connectivity
l

High-speed internet connection or VPN connection between client and server. Connectivity
provided via telephone modems is not supported.
Client-to-server Ping time should be less than 150 milliseconds

Planning
Subtopics
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l

Approvals and Planning Units


Business Rules
Data and Metadata Load
Data Validation
Dimensions
Exchange Rate Tables
Forms, Composite
Forms, General
Localization
Offline Planning
Planning Administration
Print and Print Preview
Reports
Searching, Sorting, and Filtering
Security
Selecting Members
Smart Lists
Task Lists

Approvals and Planning Units


l

16234326 -- In Scenario and Version Assignment, if you delete scenario and version
assignment and click Save, the change is not saved.
16233959 -- Users with only the View User role cannot use Approvals.
15939345 -- You cannot copy data if all the members of two very large dimensions (with
10,000+ members) are selected.
13894058 -- After starting and then editing a Planning Unit, its Enable Approval option is set
to Exclude, even though you did not set this option.

Business Rules
l

26

16616041 -- Some users may encounter an issue where Public Sector Planning and Budgeting
or Project Financial Planning application creation fails with errors while loading business
rules to the application. To work around this issue, add the following parameters to the

Readme

calcmgr property, in file, mod_wl_ohs.conf, located in Oracle/Middleware/


user_projects/epmsystem1/httpConfig/ohs/config/OHS/ohs_component:
m

WLIOTimeoutSecs 14400

Idempotent OFF

WLSocketTimeoutSecs 600

Example of the calcmgr property before updating the file:


<LocationMatch ^/calcmgr>
SetHandler weblogic-handler
WeblogicCluster servername
</LocationMatch>

Example of the calcmgr property after updating the file:


<LocationMatch ^/calcmgr>
SetHandler weblogic-handler
WeblogicCluster servername
WLIOTimeoutSecs 14400
Idempotent OFF
WLSocketTimeoutSecs 600
</LocationMatch>

After adding the parameters, restart OHS.


l

10150284 -- You cannot enter numbers with decimals at runtime.


9964318 -- If you create two business rules in Calculation Manager, and the names of the
rules use the same wording with different spacing, such as Rule 1 and Rule 1, the spacing is
not retained within Planning, and the rules are displayed with the same name. In the
database, the rule names are displayed correctly.
9438498 -- When a ruleset has a business rule from a target application that differs from the
current application, the member selector does not recognize the limits set on the runtime
prompt.
8628003 -- Business rules using the UDA function pass Performance Management Architect
validation but fail Planning validation. However, when the business rule is associated with
a form, it launches successfully.
8585767 -- If you create a composite form from an existing composite form using Save As
and move the new form to a different form folder, the business rules defined for the original
composite form may not be transferred to the new form.
7485452 -- When multiple business rules with one or more runtime prompts are assigned
to a form with Run on Save selected, an error may occur when the business rules are launched.
To avoid this problem, do not assign multiple rules with runtime prompts to forms with
Run on Save selected.

Data and Metadata Load


l

16575363 -- The Outline Load utility or Planning Outline Load is rejecting the YearTotal
record when importing Period metadata. All other Period members are importing correctly.

Readme

27

The work around is to ignore this error and modify the YearTotal record through the
Dimension Editor, if needed.
l

16104148 -- Planning supports only one data load process against an ASO cube at a time.
Concurrent data loads to ASO are not supported.
14775621 -- The Outline Load utility does not load data for members with embedded
parenthesis. For example:
Period, TestAccount, Point-of-View, Data Load Cube Name Jan, 111, Ent1,Current,Dept
Submission (Base Initial),FY14", Plan1

To work around this issue, remove the parentheses from Dept Submission (Base
Initial).
l

14651499 -- In some cases, Planning allows shared members to be added to the driver
dimension as well as the original member.
14284303 -- When using Oracle Data Integrator Adapter for Planning Release 11.1.1.1, you
see the following load errors while loading data to Planning:
m

Planning writer_0 : [ERROR] Error during initialization. Error


message is: Error unmarshaling return; nested exception is:
java.io.InvalidClassException:
com.hyperion.planning.HspRuntimeException; local class
incompatible: stream classdesc serialVersionUID =
5036872391602337965, local class serialVersionUID =
-1731297009856189748
Planning writer_0 : [ERROR] Error during initialization. Error
message @ is: java.lang.RuntimeException:
HyperionPlanningBean::beginLoad: Could not derive locale from
systemCfg format for data loading.

To work around this issue, check the DATE_FMT in the HSP_SYSTEMCFG table. If the
date format is MM/dd/yyyy, update it to MM-DD-YYYY. Before doing this, ensure you back
up the database. The date_format in the Hsp_SystemCfg table was set to MM/DD/YYYY in
version 9.3.x, but in later versions it is set to MM-DD-YYYY.
l

12318933 -- When using Outline Load utility to load dimensions containing spaces, the
dimension name parameter on the command line should be enclosed in quotation marks.
9787036 -- The Outline Load utility does not ignore line breaks in member formulas. Because
the utility interprets every line as a separate member, the outline load fails if the .CSV input
file contains member formulas with line breaks.
7435804 -- The application name must be in the correct case for the Outline Load utility to
function properly.

Data Validation
l

28

11667701 -- When you change a dynamic user variable, the updated variable may not display
in the POV and Page when viewed from the planning unit validate task list. To resolve this
issue, open the validation report to see the changed value.

Readme

Dimensions
l

14558468 -- You may encounter these issues when searching for dimensions or members:
m

When searching in the dimension editor, you receive this error if you do not first select
a member: An error occurred while processing this page.
The dimension in which you are searching is not highlighted or positioned at the top,
and you must scroll to find it in the search results that are returned.

14270412 -- If you have a dimension hierarchy with more than 25 members, members that
you add below the 25th member may not be displayed unless you access another dimension,
or log off, and then log back onto Planning.

Exchange Rate Tables


l

9194390 -- If an Exchange Rate Table contains only values for Beginning Balance (Beg Bal)
and Historical rates, those values are not refreshed to Essbase when Planning is refreshed.
To work around this issue, enter an Average or Ending rate and then save the table.
7441962 -- When entering information in the exchange rate table, you must enter only
numeric values, even if you set the separator options in the Currency dimension. The
Currency dimension properties do not apply to exchange rate table entries.

Forms, Composite
l

13694078 -- When you modify a composite form, for example, by splitting one of the sections
after you open the form, the modified section is not displayed. If you reload the form, it
displays as expected.
9047894, 8220537 -- When exporting a composite form to Microsoft Excel, only the first
simple form in the composite form is exported.
You cannot disable the pop-up messages that prompt you to save when you enter data on
composite forms comprised of a large number of tabs.

Forms, General
l

16551122, 16677644 -- Dimensions in rows are not displaying in the correct order if an
attribute is used in rows.
16444909 -- When working with ad hoc grids, the suppress options do not work with Release
9.3.3 Planning forms.
16228664 -- Form validation rules are incorrectly reading cells containing a dot (.)
character. As a result, incorrect cells are being highlighted.
16223220 -- The first line of cell comments does not display special characters correctly.
16169784, 16091672, 15992424, 15882408 -- After entering non-English text for comments
in cells, the cell comment displays unintelligible characters.
16091711, 15965430 -- When opening a Planning form in EPM Workspace, the POV dropdowns are a fixed width and, therefore, do not display the full member or alias names. To

Readme

29

work around this issue so you can view a very long member or alias name from the Page
axis, you must hover over the member or alias name.
l

16095820 -- Shared members are not displaying in Planning forms when there are two
dimensions in the rows. The label for the shared member does not appear as a row label,
however the data associated with the shared member is still displayed, but against the wrong
member. The same form displays correctly in Smart View. Also, if the form has just one
dimension in rows, then the shared member and it's data are correctly displayed and aligned.
16030548 -- The cell text in forms does not support formatting.
15973855 -- Microsoft Internet Explorer 9 users cannot change the currency code in forms
with multiple currencies. This issue does not occur for Microsoft Internet Explorer 8 and
Mozilla Firefox users.
15952183 -- A newly created form folder is not visible in the Edit menu immediately after
adding it. To view the new folder, you must close the Application tab in EPM Workspace
and then open it again.
15948220 -- If you enter data in a cell and then press Tab, the focus correctly moves to the
currency. However, if you press Tab again to move to the next cell, the focus incorrectly
exits the form and moves to the menu bar.
15834852 -- When editing a Planning form cell, the number value should retain the same
format as the format defined in Other Options and then Precision when the form was created.
14808741 -- Cells in Planning forms are not displaying all of the text.
14794898 -- With display preferences for Page members set to Indent based on hierarchy and
after selecting a member in the Member Selection dialog box, the member is incorrectly
displaying as indented in the drop-down box. A refresh resolves the issue.
14794516 -- If the screen resolution is set to 1024 x 768, and you run a business rule with a
runtime prompt, the launch button is not displayed in the prompt. To work around this
issue, you can set the screen to a different resolution.
14740305 -- Planning forms should sort dates in ascending or descending order. However,
the dates are sorting by the day of the month, not the actual date.
14680311 -- If ADF is enabled, edited cells (but not locked) and locked cells display the same
color.
14673046 -- If ADF is enabled, there is no support for a rich text editor in a pivot table cell.
14547509 -- Even though you define and enable them for members, aliases do not display
in cell attachments for Planning forms.
14492840 -- Although you specify particular forms on which to run grid diagnostics, they
are run on all forms.
14491094 -- Although they can navigate form tabs after closing the error, Internet 9 users
may receive this error when opening forms in Edit mode and using the form tabs:
Unable to get value of the property 'getClientId': object is null or
undefined Line: 686 Char: 481 Code: 0
URI: http://hostserver:19000/HyperionPlanning/afr/partition/ie/n/default/opt/core-11.
1.1.6.2-2198.js

30

Readme

14292651 -- After sorting ad hoc grid data by text fields, data that you enter and submit
loads to the intersection that you were at before you sorted.
14211460 -- When working with grids, performing a mass allocation either fails if the
Relational Spread option is selected for rows to which the Fill option was selected, or the
mass allocation incorrectly spreads data based on the Evenly Split option.
14192645 -- The grid spread functionality may perform incorrect calculations on locked
summary time periods.
14142871 -- The Page dimension shared member selections are not retained when you
navigate between two forms. This means that you must reselect the page shared members
each time you toggle between forms.
13899944 -- Text that you enter in text-type cells does not wrap to accommodate the text
you need to enter given the size of the cell. Also, multi-line text that you initially enter in
text data cells displays as one line of text if you edit the text in the cell.
13790557 -- Deleting All Years when it is used in a form moves All Years to Year Parent.
13788883 -- Member names that have a member range type variable and that contain spaces
must be enclosed in quotation marks (" ") when selecting the member from the member
selector.
13728452 -- If multiple business rules are set to launch when a form is saved, you must use
a ruleset to run the business rules one at a time or inconsistent data may result.
13709850 -- For forms that contain substitution variables with the Reuse existing substitution
variables selected in the Rolling Forecast Setup dialog box, if the period and year selected are
different from the year and period set in substitution variables, the values are set to the
original year and period. A message should be displayed to notify you that the existing year
and period values will be used.
13561653 -- If you launch a rule from a task list by right-clicking, the rule launches
successfully but the prompt is always displayed in a runtime prompt window.
13321947 -- If you have multiple members on row or column segments on the Layout tab,
and select the Place selection in separate rows option, you may notice the following:
m

The wrong members may be selected for the segments. For example, if mem1 and mem2
exist on a row segment, mem1 is not selected for segment1, and mem2 is not selected
for segment2.
The designer grid is not refreshed.

To resolve this issue, leave the Layout tab and refresh the grid designer to view the updated
segments.
l

13065602 -- After you export them, forms that are associated with multiple business rules
relating to two different databases only contain one business rule related to one of the
databases.
12907698 -- In applications with 53 weeks as their base time period, you receive, after
entering data on forms with asymmetric columns, a save error, and the underlying Essbase
applications may become unresponsive and restart.
12632935 -- Exported Microsoft Excel files do not suppress hierarchy.
Readme

31

32

12550717 -- Currency calculation scripts may not perform rollup calculations on forms
correctly if you open the forms in Smart View, enter data at a child level, and run the scripts
to calculate the form.
10324616 -- Formulas that reference a segment that is moved up, moved down, or deleted
may not get updated to reflect the updated segment positions, especially if the segment is
used as a part of a range (for example, sum([1:3])). You must manually update the formulas
to correctly reflect the changed segment positions or deletions.
10298120 -- The Round function results are incorrect if rounding to more than 9 decimals.
10226960 -- You cannot open a form that includes Dynamic Time Series (DTS) members
and has the Suppress Missing Blocks option selected.
9945942 -- Undesired behavior occurs when using the Lock/Unlock Cells option during data
spread. For example, read-only data for months before a Start Period is adjusted and Year
Total is locked.
9734723 -- Using the Suppress missing blocks setting with Dynamic Calc in forms is not
supported.
9654763 -- When printing a form to a PDF file, the columns are displaying as unformatted
- the column width is too small for the name of the member to get displayed. To work around
this issue, select File, then Spreadsheet Export and use the formatting options in Excel to
resize the fonts and columns. Or use Smart View from within Excel to open and then print
the form.
9328504 -- Click within a form cell and select the drill through icon to display source data.
Using the Drill Through option in the Edit menu can cause Web browser problems.
9284400 -- Using the ampersand character (&) in form names can cause issues.
9223718 -- When the Hide dimension property is set for two form dimensions, the form does
not open, and the Web browser stops responding.
9094156 -- If Dynamic Time Series (DTS) members are used in the Page or POV axis, when
the form is refreshed, selections on the Page or POV axis before the refresh do not persist.
8862285 -- Using Find from the browser Edit menu to locate a form member displays the
specified member. However, the member value displayed may be incorrect due to grid
display problems.
8636593 -- Problems with submitting data, refreshing data, or running business rules may
occur if users work with more than one form simultaneously.
8620404 -- Dynamic Calc members are not displayed correctly in forms when the Suppress
Missing Blocks property is set.
8579404 -- Hiding multiple dimensions on forms may cause Microsoft Internet Explorer to
stop responding.
8309383 -- In multicurrency application forms, you cannot copy a value from a cell
formatted for a thousands separator other than None to a cell with a thousands separator set
to None.
7626059 -- When data of type Text is deleted from forms, it is not deleted from the Essbase
database.

Readme

Localization
l

16319185 -- The following Planning error message is not localized:


Attributes cannot be associated with members enabled for dynamic children.

15866074 -- Although you configure Smart View and Microsoft Windows to display in
French (Canada), date formats in comment attachments and history records may not
displayed in French (Canada) format.
14536175 -- Because Smart View supports more locales than Planning, strings passed from
Planning to Smart View should display in English if Smart View is using a locale not
supported by Planning. This is not the case however, and strings passed to Smart View if
Smart View and Planning are not on the same locale, display in languages other than English.
14467288 -- Although you correctly define the locale in which to use Planning and
Calculation Manager, Calculation Manager rule prompts do not accept comma decimal
delimiters and dot thousand separators. For example, if you are on a Spanish locale, entering
2,5 to multiply by 2.5 is not accepted.
14464462 -- If you open a Planning ad hoc grid in Smart View, and are on a Chinese or
Japanese locale, you may receive an "Ad hoc grid cannot be opened as there
are no valid rows of data" error.
13958354 -- You cannot create databases for Project Financial Planning applications if the
application name is in Japanese.
13472940 -- The browser locale ZH-HK is not supported. To work around this issue, set the
browser locale to English instead of Traditional Chinese.
8970964 -- Planning does not support non-ASCII characters for passwords, such as Russian
characters.
7639511 -- Oracle recommends limiting planning unit annotations to 1200 characters or
fewer in Japanese due to sporadic issues with longer planning unit annotations.

Offline Planning
l

10410230 -- If a business rule is launched using the right-click menu on an offline form, the
business rule displays hidden runtime prompts to users.
13717851 -- Offline Planning only supports 32-bit Microsoft Office and Smart View
installations on a 64-bit operating system.
13424834 -- With Offline Planning, shortcut menus for running business rules or navigating
to other forms are not available from data cells. Select the row or column headers to access
shortcut menus in offline mode.
10383127 -- Forms with user-created substitution variables or dynamic substitution
members (dynamic POV) are not supported by Offline Planning.
9440181 -- In a form for which Suppress Missing is selected, taking the form offline can make
some read-only cells writable. Though the cells are displayed as writable in offline mode, on
sync back the data will not be saved to read-only cells.

Readme

33

8655540 -- If a function (for example, ILv10Descendants(No Accounts) is used to select


page members within a Planning data form and only shared members are selected due to
security, an error occurs if you take the data form offline in Smart View.
6562493 -- In Offline Planning, you cannot save supporting detail for cells with a Data Type
of Date.

Planning Administration
l

16447333 -- When creating a Oracle Hyperion Workforce Planning, Oracle Hyperion


Capital Asset Planning or Public Sector Planning and Budgeting application for use with an
ASO cube and the HCP plan, you must initialize the application before enabling dimensions
and members.
16383830 -- After creating or refreshing security filters for a user who has access to dynamic
members, the Essbase bucket name is displayed in the filter line for dynamic members
instead of the actual member name.
16072636 -- You cannot edit an existing menu for business rule menu types. This is because
business rule menu types do not have a plan type option and the Edit menu has an explicit
check for plan type.
15949368, 15871949 -- If you edit a user-defined attribute (UDA) and then save it while on
the Member Properties tab, the UDAs disappear. Changes to UDAs are only saved if they are
made on the UDA tab.
15923501 -- Usage statistics are incorrectly showing multiple sessions for a single user.
15880721 -- Creating and refreshing security filters is not supported for ASO databases. This
means you cannot retrieve data from ASO databases from a third party source. You can only
retrieve data through Planning either directly or, for Financial Reporting, through the
Planning ADM driver.
15841695 -- The Planning statistics Web page is displaying duplicate lines in the list, which
is confusing.
14699425 -- The navigation behavior for assigning user access is inconsistent. For example,
clicking Close on the Groups tab, incorrectly changes the focus to the Users tab.
13729396 -- Planning cannot validate values for the member range or cross-dimension
variables if two applications do not use the same dimensions.
13423598 -- If you provision a user in a Planning application through a group, select group
administration for audit reporting, and later the user is removed from the group, an entry
describing the removal is not logged in HSP_AUDIT_RECORDS.
9794656 -- You cannot copy applications between environments using anything other than
Lifecycle Management.
8603489 -- If you change user preferences in EPM Workspace and then select one of the
modified users as a user variable in a form, the following error displays:
An Error occurred while processing this page. Check the log for details.

34

7420574 -- When running Planning on a UNIX system, rename the output file from the
ExportSecurity utility to Secfile.txt before running the ImportSecurity utility.

Readme

7225626 -- If you add a driver member using Administration, then Data Load
Administration, you cannot subsequently delete that member. To work around this issue,
delete the driver member from the list of selected members in the Data Load
Administration window.
Planning forms that were customized using ValidateData.js and its helper JavaScripts
will not work with the Planning Release 11.1.2.2s ADF-based user interface. Customized
forms will continue to work, however, with the classic user interface in Planning releases
prior to Release 11.1.2.2.

Print and Print Preview


l

13064603 -- If you execute a report from a task list (using a URL and single sign on), you
cannot export the report to PDF format. To view reports in PDF format and print them,
run reports from EPM Workspace.

Reports
l

16099175 -- The position of task list columns that you manually reorder are not correctly
displayed in task list PDF and Microsoft Excel reports. Column position is determined by
the template provided and cannot be modified manually by reordering columns.
14699022 -- If you use Microsoft Excel 2003 PS3 and create a Microsoft Excel report to view
Task List data, you receive an error saying that the file is not in a recognizable format. If you
use Microsoft Excel 2007, you receive a message that the file is of different format than
specified by the file extension, and if you click OK, the report opens but not in Microsoft
Excel format.

Searching, Sorting, and Filtering


l

14394635 -- You receive this error when searching for dimension members in Planning: An
Error occurred while Processing this page. Check Log for details. To work around this issue,
select the parent dimension or member before performing the search.

Security
l

8633509 -- In forms that have a drill through icon, cells with Smart List drop-down lists
display the icon, but a user is prevented from clicking on this icon.
8553839 -- Sometimes the Performed On column in the Security Audit report displays
Unknown instead of the server name or address.

Selecting Members
l

13724899 -- When working with multiple dimensions in the member selector and switching
back and forth between dimensions, the expand and collapse states of individual member
nodes are not preserved.

Readme

35

13600650 -- When selecting members, there are issues with selecting multiple members at
one time.

Smart Lists
l

8714045 -- If you define custom values for Smart List IDs, do not use zero as an ID. Using
zero as an ID can result in missing data when the Smart List is saved to the Essbase database.

Task Lists
l

16263588 -- Users are unable to add or modify child elements with business rules to a task
list. To work around this issue, select Administration, then Manage, then Dimensions, and
then Versions. Select to edit a version and check whether the property Enabled for Process
Management is selected. If it is not selected, select it. At least one member of a version
dimension should have this property checked.
16207758 -- The scroll bar for task instructions is not displaying for tasks with long
instructions.
15881419 -- An error message occurs while editing task list items for an application that was
migrated using Lifecycle Management. But if you click OK, you can proceed without issue.
To work around this issue, go to Administration, then Manage, then Dimensions, and then
Versions. Edit any version member and check whether the property Enabled for Process
Management is selected. At least one member of a version dimension should have this
property selected.
14461892 -- You cannot specify a URL for a task list if the URL exceeds 256 characters.
13624086 -- When opening a report from a task list, you must enter a user name and
password in order to access the report. If the SSO token property is selected in the task
properties, the following error is displayed: An exception was thrown: HTTP request cannot
be accepted because of secure parameter passed in the URL. Parameter name: 'sso_token'.
8460666 -- Planning checks the format of a task due date, but does not restrict the date
specified. When administrators define task due dates, they must ensure that the dates
specified for dependant tasks occur in the appropriate order. For example, if Task1 must be
complete before Task2, set the due date for Task1 to a date earlier than the due date for
Task2.
8401031 -- URL entries for tasks are not converted to Web addresses.

Capital Asset Planning


Note: If you have a Release 11.1.2.1 or 11.1.2.2 Capital Asset Planning application, to take

advantage of the Release 11.1.2.3 new features for this module, create a new 11.1.2.3 shell
application for Capital Asset Planning, and then use Lifecycle Management to migrate
the new Release 11.1.2.3 application features into your upgraded native application.

36

Readme

16353951 -- When creating an application using Performance Management Architect, the


Asset Details dimension is not displaying in the Application Settings screen.
16328313 -- Capital Asset Planning applications that use Performance Management
Architect do not have the option to select an All Years parent member that includes all years.
13253184 -- Certain business rules do not execute unless, on the Performance tab, the Year
dimension comes before the Line Item dimension.

Project Financial Planning


Note: Performance Management Architect Project Financial Planning applications only use the

functionality provided in release 11.1.2.2.300. No new functionality introduced in release


11.1.2.3 is available to users creating a Project Financial Planning application through
Performance Management Architect.

16586760 -- For a revenue generating Capital project, when entering assumptions on the
Revenue Drivers Capital Project form, you must enter a value for each year in the Units (YOY
% Increase) and Price/Unit (YOY % Increase) cells. If a cell is left blank for any year, revenue
will not be calculated for subsequent years, even if values are specified for those years. To
work around this issue, enter a 0 (zero) value in any blank cell. Do not leave those cells blank.
16574256 -- The Calculate Imported Projects rule fails for existing projects when executed
for the scenario Actual and the version Final. The reason for failure is that the Calculate
Project Score rule, which is part of the Calculate Imported Projects ruleset, fails since
Calculate Project Score should not be executed on existing projects. Since we have a
common rule to calculate imported projects for both existing and new projects, executing
the rule for existing projects fails. To work around this issue, modify the rule
CalculateProjectScore, which is present under the Project cube, to add the condition IF
( @ISCHILD( "New Project")) ... ENDIF after the "Net Present Value
(NPV)" line as shown in the example below:
"Net Present Value (NPV)" (
/***** Add the below line *****/
IF ( @ISCHILD( "New Project"))
projectEndDate = "No Project Element"->"BegBalance"->"End
Date";
projectEndMonth = @TRUNCATE( @MOD( projectEndDate, 10000) /
100);

ENDIF
ENDIF
/****** Add the below line *****/
ENDIF
)

After modifying the rule, save it, and then deploy at the application level so that all of the
dependent rules are also deployed.

Readme

37

16512364 -- In Project Financial Planning, the default value for substitution variables is
English, even for translated applications. For non-English applications, change the English
values to the correct translated value.
16354519 -- When adding a new member using the member on the fly functionality in
Planning, the new member is not visible in Approvals unless the planning unit hierarchy is
synchronized by the administrator.
14548188 -- Project Financial Planning users may receive a "No planning unit
match the filter criteria" message and be unable to display and access planning
units using Manage Approvals as expected.
14547372 -- Project Financial Planning users may find that, in some situations, unit prices
display without their unit numbers on the Revenue Assumptions page.
13566568 -- When viewing the Review Project KPIs composite form for existing projects in
Project Financial Planning, do not select to view the KPIs at the No Project level.
13456856 -- When creating sample projects in Project Financial Planning, default user
preferences are not set during application creation.
13401335 -- In Project Financial Planning, intercompany expenses are not automatically
converted into the local currency of their owning entities.

Public Sector Planning and Budgeting


l

38

16677202 -- Allocation data is not populating for elements if Follows Salary Allocation is set
to No and if some employees/positions have overriding allocations specified at the employee/
position level while others do not. This issue only occurs while launching the Allocate
compensation to General Ledger accounts task for a specific employee/position. To work
around this issue, launch the Allocate compensation to General Ledger accounts task at the
employee/position level.
16580178 -- If commitment control and decision package features are enabled, then an error
occurs when running a budget check if a decision package contains multiple budget requests.
16560036 -- For a decision package-enabled Position Only application, calculations for
the source entity are incorrect when performing a single step position transfer mid-month.
16554257 -- For decision package-enabled applications, if the additional earning type
element Follows Salary Allocation is set to No, expenses are not allocating to GL accounts.
16527860 -- When HCP is not enabled and the decision package feature is enabled, then
executing the Copy Decision Package operation erases some of the revision properties.
16515538 -- When creating a second budget request and adjusting the salary for an
assignment made in the first budget request, the other percentage-based compensation
elements are not adjusting accordingly in the second budget request.
16412382 -- For a decision package-enabled Employee Only or Position and Employee
application, the revision employee details are assigned the same start year as the
compensation budget start year. If the employee has details prior to the compensation
budget start year, the start date will be the first day of compensation budget start year. During
budgeting, if an employee is active prior to the compensation budget start year and has

Readme

salary, FTE, status, non-salary, and allocation assignments, revision employee details will
start from the compensation budget start year.
l

16362193 -- While working with a Public Sector Planning and Budgeting application in
Smart View, you cannot retrieve Budget Request members in Rows/Columns.
16355521 -- Unable to create a Public Sector Planning and Budgeting application if the ASO
plan type is selected. To work around this issue, do not initialize the ASO cube until after
the Public Sector Planning and Budgeting module has been initialized. For example, Public
Sector Planning and Budgeting users who want to use the ASO plan type and the Human
Capital Planning plan type, during application creation, should enable Plan1, Plan2, Plan3,
HCP, and the ASO plan type and delete any plan types that they do not want enabled on the
Plan Types screen.
16354519 -- When adding a new member using the member on the fly functionality in
Planning, the new member is not visible in Approvals unless the planning unit hierarchy is
synchronized by the administrator.
16325324 -- Users cannot view the Smart List drop down inverted triangle to change the
selection for Allocate to Base Element to Yes or No. To work around this issue, resize or shrink
other columns and then stretch the Follows Salary Allocation to the right.
14371168 -- In decision package-enabled applications, right-click menu options for
positions may be unavailable for the Manage all positions task after you add new positions
using the Manage request positions task. To work around this issue, use the Tab button to
view the menus or, to alter the main content area in the browser window, move the splitters
for the masthead at the top of the browser.
13846249 -- Commitment control integration delivers real-time budget checking against
the rules defined in PeopleSoft Commitment Control through a web service call that is
initiated when the end user clicks the Budget Check button in the decision package detail
grid. If two users launch commitment control funds checking at the same time, a table
locking error occurs in the PeopleSoft budget checking process. Oracle Hyperion Financial
Data Quality Management ERP Integration Adapter for Oracle Applications currently
delivers one write-back rule, which is used by the commitment control validation process.
This conflict is caused by the two user processes being treated as one process instance through
ERP Integrator as though one user were launching multiple concurrent processes. To work
around this issue, define a separate Oracle Hyperion Financial Data Quality Management
ERP Integration Adapter for Oracle Applications write-back rule for each entity that will be
performing the commitment control validations through Public Sector Planning and
Budgeting.
11737150 -- In Public Sector Planning and Budgeting, in Employee Budget Detail you cannot
transfer an employee out using Maintain employee by job. To work around this issue, navigate
to Edit Job Details, select the job from Active Jobs, then View Job Details, navigate to the
employee tab and transfer out the employee.
10339351 -- In Public Sector Planning and Budgeting, in the predefined Financial Reporting
report, Position Adjustments, taxes and benefits are not displaying in the report.
10336709 -- In Public Sector Planning and Budgeting, sometimes the runtime prompt dialog
box displays even though its values are already determined from the context.

Readme

39

8851138 -- The Fill Salary Grade operation fills any gaps, for example, if there are no salary
grades defined for a position and employee combination, then it will create the new salary
grade. If a salary grade exists, then it will not do anything.

Workforce Planning
Note: If you have a Release 11.1.2.1 or 11.1.2.2 Workforce Planning application, to take

advantage of the Release 11.1.2.3 new features for this module, create a new 11.1.2.3 shell
application for Workforce Planning, and then use Lifecycle Management to migrate the
new Release 11.1.2.3 application features into your upgraded native application.

16353951 -- When creating an application using Performance Management Architect, the


Job dimension is not displaying in the Application Settings screen.
16328313 -- Workforce Planning applications that use Performance Management Architect
do not have the option to select an All Years parent member that includes all years.

EPM Workspace
l

9886144 -- Forms and folders are not consistently displaying in the left pane after logging
into Planning using EPM Workspace.
8629620 -- If you use an SSL Accelerator and access Planning from Oracle Hyperion
Enterprise Performance Management Workspace, an HTTP call, instead of an HTTPS call
is made.

Lifecycle Management
l

16374203 -- Using Lifecycle Management to export forms fails if the form has trailing spaces.
16312605 -- While exploring Planning applications where Planning related artifacts are
created, the Modified Date and Modified By properties are not available for several artifacts.
16198496 -- Business Rules functions are not translated to equivalent Calculation Manager
functions during a Lifecycle Management migration, thus causing validation of the rule to
fail.
15861796 -- When logged in as an LCM Administrator and while exploring Planning
applications, an error message displays indicating that the service is currently not available.
14534842 -- After migrating using Lifecycle Management, form folder security is not applied
as expected to all subfolder, and some subfolders may not be migrated.
14525863 -- The following error is occurring during the import of a planning unit if the
planning unit owners are deleted from the source application.
ID OF PLANNING UNIT CREATOR IS UNKNOWN

40

14483057 -- If you encounter defect 14398885 (see the issue listed after this one), create the
substitution variables described in 14398885, and then get the following error message after
Readme

creating or refreshing the database in Planning, create or refresh the database using the
Update custom defined functions option:
Verify Outline failed with the following errors: Error [1200472] detected in member
formula for member "IRR". Error [1200472] detected in member formula for member
"ROI".
l

14398885 -- After using Lifecycle Management to import a Project Financial Planning


application created in Performance Management Architect, you may get a deployment
completed due to error message caused by missing substitution variables. To work around
this issue, manually recreate these variables as shown below, and then redeploy:
m

CurYrThe current year. For example, if the current year is 2013, set this variable to
FY13.

LastYrThe previous year. Ensure that the previous year exists in the year dimension.

NextYear The next upcoming year, such as FY14

Yr3The year after NextYear, such as FY15

Yr4The year after Yr3, such as FY16

ThisMonthThe current month

CurScenarioThe current scenario

CurVersionWorking

ActVersionFinal

ForVersionWorking

PlanVersionFinal

ThisyearThe current year

13805402 -- After migration, the directory structure and order of forms in the destination
application differs from that in the source application.
10402229 -- The shell creation utility does not support migration of security related artifacts.
The security related artifacts must be imported after application creation.
10373894 -- After a Lifecycle Management migration, the Planning artifacts (for example,
Business Rules, Custom Menus, and so on) are displaying in a different order on the
destination environment than the order in which they were displayed on the source
environment.
10336614 -- After a Lifecycle Management migration, the task list order on the destination
environment differs from that of the task list order on the source environment.
10140764 -- After a Lifecycle Management migration, the directory order on the destination
application differs from that of the directory order on the source application.
10029734 -- After you import artifacts using Lifecycle Management, the sequence order of
some artifacts may change from the source application.
9363364, 9354048 -- Form and menu imports are failing due to long artifact path names.
Because of a Windows limitation, Lifecycle Management cannot migrate artifacts if the
artifact path exceeds 256 characters. The work around is to zip the source artifacts using 7Zip (not WinZip) and copy the 7z file to the target location. Then unzip the artifacts. 7-Zip

Readme

41

is available at http://www.7-zip.org/download.html. You can use any program to copy the


artifacts from the source location to the target location, since programmatic languages like
Java (1.5.11+) do not have this limitation and can handle folders and artifacts with paths
exceeding 256 characters.
l

7454233 -- After migrating Calculation Manager rules artifacts, there might be differences
between the XML on the source and on the destination environments. These differences
occur because of the order in which sequences or applications get added to the destination
environment. The differences could also be due to the number of sequences or applications
at the destination. For example, if a source application has five sequences with IDs starting
from 1 to 5 and the destination already has three sequences, at import, the sequences will
be renumbered to start at 4 on the destination environment. As a result, there would be
value differences between the source and destination XMLs.
7454182 -- If an application has only Workforce and/or Capex-enabled plan types, the
Consolidation property for dimension members is not getting set during a Oracle Hyperion
Enterprise Performance Management System Lifecycle Management import.
7011878 -- ACLs that were removed in the source application are not being updated on the
target environment.

Performance Management Architect


l

16374929 -- An error occurs while initializing Workforce Planning on a Capital Asset


Planning deployed application or while initializing Capital Asset Planning on a Workforce
Planning deployed application. To work around this issue, administrators can modify the
properties of the members whose formulas do not compile to be enabled only for the
Workforce plan type. You can review and update the Valid for Plan Types property for existing
dimensions under Administration, then Manage, and then Dimensions.
12402565 -- The Performance Management Architect Data Synchronizer does not report
an error when a member in the source file is invalid.
9720515 -- You cannot deploy two different Performance Management Architect
applications at the same time.
Even though you redeploy from Performance Management Architect to Essbase using In
Sync With Deployment, new attribute members that you add or existing attribute members
that you move in the Dimension Library are not successfully redeployed to Essbase.
Data synchronization fails between Oracle Hyperion EPM Architect and Planning
applications if you use a substitution variable as a filter.

Smart View
l

16566257 -- When adding members in Smart View, after selecting Submit Data, the new
member is not being added under the Parent Member. Instead it is added under the root
member.
For example, in the following hierarchy:

42

Readme

Entity
1000
2000
3000
3100
3200
......
6000
......

If member 6100 is added under the parent 6000 and then Submit Data is selected, the new
member is added as a child of Entity, not member 6000.
To work around this issue, select the Submit without Refresh mode. To select the Submit
without Refresh mode:
1. Logon to Planning Web.
2. Open the Planning application.
3. Select Administration, then Application, and then Properties.
4. Add the following property and set the value to True:
SMART_VIEW_DIMENSION_EDITOR_PARITY_MODE

5. Add the following optional property to override the Submit with Refresh (overrides the
* after adding and refreshing a new member):
SMART_VIEW_DIMENSION_EDITOR_NEW_MEMBER_SUFFIX

6. Disconnect from the Planning application in Smart View and then reconnect.
Note: It is not necessary to restart the Planning server in order for the changes to take effect.
l

16566075 -- When using Planning extensions to add and edit metadata (dimensions,
members), if a new member for an entity or other dimension is added and then you click
Refresh to apply the modification, Smart View displays a message 'Invalid double
Value' after 'Refresh' and the new member is not added. To work around this issue,
select the Submit without Refresh mode. To select the Submit without Refresh mode, follow
the steps that are documented in the previous defect (defect 16566257).
16189511 -- Although the Planning Smart View extension (described in Appendix D of the
Oracle Hyperion Planning Administrator's Guide) is localized in this release, the Planning
Smart View extension installer is not localized in this release. It will be localized in the next
Planning release.
16031150 -- The Shared Data storage option is not available for members of the Currency
dimension.
15917027, 15911382 -- While using ad hoc analysis in Smart View using the Planning
connection, if you copy and paste values containing blank rows from one sheet to another
and then submit the data, it displays an error message stating, You are in free form mode,
press refresh before submit. If there are no blank rows in the values being copied and pasted,
then you can submit them.
14799772 -- In Smart View, Planning composite forms with business rules attached to them
are displaying run time prompts even when the Hide Prompt option is selected.

Readme

43

14473004 -- Attribute values that you define in Planning and use on a form are not displayed
if you open the same form in Smart View.
14461937 -- Runtime prompts that you add to rulesets created in Calculation Manager and
that you associate with new task lists do not display when you open the task lists in Smart
View and try to launch the ruleset.
14258058 -- You may experience these problems when building reports using ad hoc
analysis, and then viewing and running them in Microsoft Excel. These problems occur if
you connect to Essbase via Shared Connections in Smart View:
m

44

After adding the IMPLIED_SHARE FALSE setting to Essbase.cfg, loading data to


Essbase, refreshing the Planning database, and restarting Essbase, data is missing when
you access your application in Smart View.

14175891 -- Given your browser, you may be unable to open Planning forms in Smart View,
or open forms as expected. Note the following:
m

After defining a report, applying a query, saving it as a Microsoft Excel file, and then
trying to run the report in Microsoft Excel you get a Response is missing
expected tag attributeerror.

Internet Explorer (IE) 8.0 and 9.0Clicking the Open toolbar button does not enable
you to open forms.
IE 7.0Microsoft Excel launches and you are prompted to log on but forms do not open
Firefox 3.0.19 and 10 or laterYou receive a security alert but continuing does not open
the form

13737802 -- There are some behavioral differences between Planning Web and Smart View
for runtime prompts. For example, if on a form a shortcut menu business rule is set to hide
runtime prompts in Planning Web, but in Smart View, it will still show runtime prompts
to users when launching the rules.
9690538 -- If a form name contains an ampersand character (&), the form cannot be opened
in Smart View using the File menu's Open in Smart View menu option.
9458442 -- If the Suppress missing data option is set for a form and shortcut menus do not
display, edit the form and clear this option on the form Layout tab.
9395874 -- Forms created from other forms using Save As are displayed as empty Microsoft
Excel spreadsheets when you select Open in Smart View.
9357803 -- Smart List data type values show aggregate cells as NA though the aggregation
type is defined as 'Ignore' in Planning. On the Web, these display as blanks. To work around
this issue, remove the #missing label from within the Smart List definition on the Web.
9299556 -- In Smart View, if you launch a business rule that has a runtime prompt for a
Smart List, if the Use Last Value option is not selected, the runtime prompt displays blank
values, whereas in Planning Web, the runtime prompt displays the first value in the Smart
List drop-down list.
9032377 -- When using ad hoc analysis in Planning through Smart View, audit information
is not saved.
8872764 -- Substitution variables and user variables are not supported in Smart View.

Readme

8246706 -- When using ad hoc analysis in Planning through Smart View, Planning does not
support ad hoc analysis for multi-currency (entity currency overrides) forms.
6779540 -- When selecting members for runtime prompts in Smart View, shared members
are not included in the list displayed.
6769707 -- If users attempt to start Smart View from Microsoft Excel on a machine where
Smart View is not installed, an error message should be displayed stating that Smart View
is not installed.
If you use the @RETURN function in rules and calculation scripts to enable users to define
custom error messages, you may notice that in Smart View only the underlying Oracle
Essbase error message is displayed and the custom user-defined message is not.

Web Browsers
l

16030432 -- With Firefox, double-clicking on a POV down arrow may cause a Planning
application to become unresponsive. Also, you may get a Null Pointer error when you
double-click on a POV member name.
15992688 -- With Microsoft Internet Explorer 9, Planning displays an error message if you
perform a search for a specific dimension member under Manage Dimensions.
9265794 -- Sometimes selecting form cells with a mouse causes an error, and the following
message is displayed.
Warning: Unresponsive script
A script on this page may be busy, or it may have stopped
responding. You can stop the script now, or you can continue to see
if the script will complete.

Documentation Updates
Subtopics
l
l
l
l
l
l
l

Accessing EPM System Product Documentation


Copying and Pasting Code Snippets from PDFs
Planning Administrator's Guide
Planning User's Guide
Project Financial Planning User's Guide
Public Sector Planning and Budgeting User Guide
Workforce Planning Administrator's Guide, Chapter 4, Adding New Hires

Accessing EPM System Product Documentation


The most recent version of each EPM System product guide is available for downloading or
viewing from the EPM System Documentation area of the OTN Web site (http://
www.oracle.com/technology/documentation/epm.html). You can also use the EPM System
Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-

Readme

45

information-147174.html), which also links to EPM Supported Platform Matrices, My Oracle


Support, and other information resources.
Deployment-related documentation is also available from the Oracle Software Delivery Cloud
Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form).
Individual product guides are available for download on the Oracle Technology Network Web
site only.

Copying and Pasting Code Snippets from PDFs


When you cut and paste code snippets from a PDF file, some characters can be lost during the
paste operation, making the code snippet invalid. To resolve this issue, copy and paste from the
HTML version of the document.

Planning Administrator's Guide


Subtopics
l
l
l
l
l
l
l
l
l

Chapter 2, Getting Started with Planning, Working with Planning Utilities


Chapter 3, Setting Up Access Permissions
Chapter 5, Loading Data and Metadata
Chapter 6 Managing Forms
Chapter 7, Using the Member Selector, Working with Substitution Variables
Chapter 9, Managing the Budgeting Process
Chapter 12, Working with Planning Application Administration
Appendix C, Form Formula Functions, Formula Functions
Appendix D, Using Smart View to Import and Edit Planning Metadata, Designating Shared Members in Smart
View

Chapter 2, Getting Started with Planning, Working with Planning


Utilities
Debug messages for Planning utilities (for example, ProvisionUsers, ImportSecurity,
ExportSecurity) are logged to a log file called PlanningCLU.log that is generated under C:
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\planning.
The debug level can be modified in the loggingCLU.xml file located under C:\Oracle
\Middleware\user_projects\epmsystem1\Planning\planning1.

46

Readme

Chapter 3, Setting Up Access Permissions


Managing Security Filters
Oracle recommends that you perform a cube refresh with the Security Filters option selected
each time a change is made to the outline, including when dynamic child members are added
or members are renamed and security is assigned to the new members.

Migrating Business Rule Security


Because Oracle Hyperion Business Rules is no longer supported in Planning and Oracle
Hyperion Calculation Manager is the only option, the Calculation Module setting was removed
from the System Settings page.

Chapter 5, Loading Data and Metadata


Generating Load Files
Note: If saving or modifying metadata or data .csv files generated by the Outline Load utility

export/import in Microsoft Excel, be aware that Excel does not properly handle some
formatting features in the .csv file. For example, Outline Load utility places the POV
member information in double quotes and treats it as one column, while Excel treats the
POV members as separate columns. Saving the file in Excel will place an additional set of
quotes around the POV members and will add commas to the top header row. Outline
Load utility will not recognize this as a valid format when the file is imported back. We
recommend editing and saving .csv export files in Notepad, Wordpad, or another text
editor.

Exporting Metadata from a Planning Application to a Relational Data Source


The example for Properties File for Exporting with an Alias from an Outline to a Relational
Data Source needs to be updated as shown below:
/A:expe
/U:admin
/ERA
/D:Entity
/REQ:ENTITY_EXPORT_QUERY1
/C2A:AliasLabel
AliasLabel:(AliasTableName, Alias: reallyLongAliasTableName30Char)
ENTITY_EXPORT_QUERY1=Insert into Test(Member, Parent, AliasTableName) values (Member,
Parent, Alias: reallyLongAliasTableName30Char)

Assume the following with regards to the previous example:


l

The 'Test' table has three columns, Member, Parent, AliasTableName and the table is empty.

Readme

47

The Entity dimension has one member, e1, under the root (Entity).

After running the previous query, the 'Test' table will have one entry:
Table 4

'Test' Table Output

Member

Parent

AliasTableName

E1

Entity

E1 Alias From reallyLongAliasTableName30Char

Note: The /C2A and/or Label switches may be used to work around the thirty character column

name limit restriction in Oracle relational tables; for example, Alias:


reallyLongAliasTableName30Char is longer than thirty characters and not allowed as a
column name in Oracle relational tables.

Command Line Parameters for the Outline Load Utility


Parameter: /S:server
New Description: If specified, the server into which you are currently logged in. If not specified,
localhost is used.

Importing from a File


l

To import data, the load dimension must be selected in the Dimension drop down.
For Dimension, user defined dimensions (for example, Product) are listed in the drop down
along with the base dimensions. If there is a user defined dimension in the application and
you want to load its metadata, then select the user defined dimension from the drop down.
If your file contains metadata for a user defined dimension called, for example, NewProduct
which does not yet exist in the application, then select New Dimension, then User Defined,
and then NewProduct. Planning Outline Load will create the NewProduct dimension and
load it's metadata.
The Command Properties File import option was removed from the Import from File screen
in Planning Outline Load.
For Driver Member Specification, note the following example:
Entity,Children(Account_Total), Plan1

Clear Essbase Data is optional. If a data value exists in a cell and the imported data does not
have value for that cell, the existing data will not be overwritten. To overwrite existing data
with a #missing value, the data block must be cleared first (all cells will be #missing) and
then data should be imported into these cells. For example:
e2,IDescendants(Account_Total),"FY13,Current, BU Version_1,Jan,Local",Plan1

Exporting Data to a File


l

48

For Planning Outline Load, when entering member names with a comma character in the
Export Data to File window, use double quotation marks to enclose the member names. Each
Readme

member in a list of multiple members must be placed in its own set of quotation marks. For
example:
"e2,""e,2"""
"Jan,""Feb,2"",Mar"
"FY13,Current,""a,1A"",Local, BU Version_1"
l

For Row Members, note the following example:


Idescendants(Ent_Total)

For Column Members, note the following example:


Idescendants(YearTotal)

For POV Members, note the following example:


FY13,Current, BU Version_1,account1,Local

Chapter 6 Managing Forms


Numerous sections in this chapter incorrectly describe the formula bar as displaying above forms
on the Layout tab. You can no longer invoke the formula bar and define formulas from this
location. To define form formulas, perform these steps
1. Open the form, select Layout, and then select the formula row or column.
2. Expand Segment Properties to the right, and then click Edit by Formula.
3. In Formula, select the function (Count(), Max(), and IfThen() for example) to use and build
the formula as described in the documentation.

Chapter 7, Using the Member Selector, Working with Substitution


Variables
In Chapter 7, the Oracle Hyperion Planning Administrator's Guide states that you create and
assign values to substitution variables using Oracle Essbase Administration Services Console or
ESSCMD. These substitution variables are then available in Planning when you select members
for a form.
You can also create and assign values to substitution variables within Planning.

To create and assign values to substitution variables using Planning:


1

Select Administration, then Manage, then Variables.

Select the Substitution Variables tab.

Click Actions, then select Add.

On the Add Substitution Variable page, select the Plan Type.

For Name, enter the name of the substitution variable.

For Value, enter a value for the substitution variable.

Click OK.

Readme

49

To delete substitution variables using Planning:


1

Select Administration, then Manage, then Variables.

Select the Substitution Variables tab.

Select the substitution variable to delete.

Click Actions, then select Delete.

Click OK.

Chapter 9, Managing the Budgeting Process


Exporting Planning Unit Hierarchies
After export, click Export or Done. Export performs the action, and Done dismisses the dialog.

Importing Planning Unit Hierarchies


After import, click Import or Done. Import performs the action, and Done dismisses the dialog.

Adding Tasks to Task Lists


For the Form type of task, you can only select the form associated with the task you are adding.
You cannot select the form folder.

Chapter 12, Working with Planning Application Administration


Working with Dimensions
The example for the Time Balance Property called Fill is incorrect in Table 69 of the Oracle
Hyperion Planning Administrator's Guide. The documentation incorrectly shows the parent value
as equaling the child values when it should show the parent value consolidating. The following
is the corrected example:
Jan: 10; Feb: 10; Mar: 10; Q1: 30

Specifying Plan Types


You can specify up to three generic plan types for an application. If you select one BSO plan type
during application creation, then you are allowed to add two more from the plan type editor for
a total of three. Oracle Hyperion Public Sector Planning and Budgeting and Oracle Project
Financial Planning users will need to use Oracle Hyperion Workforce Planning and/or Oracle
Hyperion Capital Asset Planning plan types and should ensure those plan types are tagged as
such so they will not count towards the three generic total. Planning allows up to three generic
plan types total and one ASO database for each BSO database plus one additional ASO database
for consolidation purposes.

50

Readme

Aggregate Storage Outline Limitations for Planning


l

Use of the aggregate storage outline (ASO) feature within Planning requires the customer
to have the appropriate license for its use.
Creating and refreshing security filters is not supported for ASO databases. This means you
cannot retrieve data from ASO databases from a third party source. You can only retrieve
data through Planning either directly or, for Financial Reporting, through the Oracle
Hyperion Planning ADM driver.

Appendix C, Form Formula Functions, Formula Functions


When a formula row includes @IDESC, the sum includes all of the parents and their descendants.
For example, a form is created with the following rows (and each member has children):
IDESC("Mem1"), IDESC("Mem2"), IDESC("Mem3"), IDESC("Mem4")
If a formula row is added with the following formula:
SUM(ROW[1],ROW[2],ROW[3],ROW[4])
When the form is opened for data entry, the formula row will return the sum of all the parents
and their children.

Appendix D, Using Smart View to Import and Edit Planning Metadata,


Designating Shared Members in Smart View
The Shared data storage option is not available for members of the Currency dimension in Oracle
Hyperion Smart View for Office.

Planning User's Guide


Subtopics
l
l

Chapter 10, Managing Planning Units, Planning Unit Details Screen Uses a New Tabbed Layout
Chapter 11, Setting User Preferences, Remembering the Most Recent Page Visited

Chapter 10, Managing Planning Units, Planning Unit Details Screen Uses
a New Tabbed Layout
When viewing details for a planning unit on the Manage Approvals screen, there is a new tabbed
layout that displays tabs for History and Annotations. The History tab displays the planning unit
approvals status, owner, last action, and the date the status changed. The Promotional Path button
was moved to the History tab and a Refresh button was added. The Annotations tab enables you
to view the title, author, date, and text for existing annotations and to add new annotations.

Readme

51

Chapter 11, Setting User Preferences, Remembering the Most Recent


Page Visited
The Remember most recent page visited option is no longer a valid option in the Display Options
Preferences.

Project Financial Planning User's Guide


Subtopics
Chapter 7, Planning Workforce
Chapter 12, Performing Financial Analysis, Setting the Target for Entities
Appendix C, Importing Data and Metadata

l
l
l

Chapter 7, Planning Workforce


The user interface label for To-Be-Hired (TBH) has changed. The old and new labels are as
follows:
Table 5

Old and New Labels for TBH

Old

New

Add To-Be-Hired

Add Hiring Requisition

Remove To-Be-Hired

Remove Hiring Requisition

The documentation will reflect the name change in a future documentation update.

Chapter 12, Performing Financial Analysis, Setting the Target for


Entities
You can set the target value for each entity by referring to the Actual data for last year, or you
could manually enter the target values. If you have the Actual data for last year, then you can set
the target at a very high level or at summary level for each entity.
To set the target values at a high level, you can directly import data into the following relational
tables:
l

To load the Headcount value at the Entity level, use the


HSP_I_PFP_ENTITY_LEVEL_ACTUALS table and enter the Headcount value for the
required entity, year, period, and currency.
See Import Entity Level Actuals Table Description, for details about the
HSP_I_PFP_ENTITY_LEVEL_ACTUALS table.

52

To load the Cost of Sales value at the Entity level, use the HSP_I_PFP_PROJECT_EXPENSES
table and enter the Cost of Sales value for the required entity, year, period, and currency at
the Actual, Final, and Unspecified Project intersection.
Readme

See Project Expense Table, for details about the HSP_I_PFP_PROJECT_EXPENSES table.
l

To load the Sales Revenue value at the Entity level, use the
HSP_I_PFP_PROJECT_REVENUE table and enter the Sales Revenue value for the required
entity, year, period, and currency at the Actual, Final, and Unspecified Project intersection.
See Project Revenue Table for details about the HSP_I_PFP_PROJECT_REVENUE table.

Appendix C, Importing Data and Metadata


Load Requirements and Recommendations
The following point must be corrected:
l

Incorrect: All percentage values must be entered after dividing it by 100. For example, if you
want to add a percentage value of 30%, then you must enter a value of 0.3 in the .csv file.
Correct: All percentage values should be entered without dividing by 100. For example, if
you want to add a percentage value of '30%', then you enter the value '30' in the required
table column.

Import Entity Level Actuals Table Description


The following point must be updated:
Correct: Use the HSP_I_PFP_ENTITY_LEVEL_ACTUALS table to load entity level actuals data
such as Headcount. We support only headcount to be loaded within the
HSP_I_PFP_ENTITY_LEVEL_ACTUALS table.

Public Sector Planning and Budgeting User Guide


Subtopics
l
l

Chapter 11, Working With Decision Packages and Budget Requests


Chapter 12, Using Reports and Budget Books

Chapter 11, Working With Decision Packages and Budget Requests


How Budget Request Type Impacts Compensation Budgeting
The guide provides incorrect or contradictory information about the actions permitted for
positions in both types of budget requests.
l

If created in recurring budget requests, positions later used in non-recurring budget requests
cannot be transferred or terminated.
Positions created in non-recurring budget requests cannot be transferred or terminated in
recurring budget requests.

Readme

53

Positions created in non-recurring requests can be transferred or terminated if used in


another non-recurring budget if both budget requests have the same end date.

Submitting Decision Packages for Approval and Viewing Promotional Paths


When viewing details for a planning unit used to submit and promote a decision package on the
Manage Approvals screen, you can view history and annotations using the tabs provided. The
History tab enables you to:
l

View the status of each planning unit associated with a decision package, its owner, and the
last action taken. The Promotional Path button was also moved to the History tab and a
Refresh button was added
Access and refresh the promotional path using the corresponding buttons

The Annotations tab enables you to view the title, author, date, and text for existing annotations
and to add new annotations.

Chapter 12, Using Reports and Budget Books


Replace the descriptions for these predefined Oracle Hyperion Financial Reporting reports with
the following descriptions:
l

Vacant Positions: Displays all vacant positions, their numbers, and compensation details
and expenses by year. Positions without compensation expenses are not displayed.
Position-Employee Associations: Summarizes all employee position assignments, including
the job, position, and total FTE.

Workforce Planning Administrator's Guide, Chapter 4,


Adding New Hires
Use this procedure that requires you to create an alias table for salaries, to add new hires:

To add new hires:


1

Create an alias table, define aliases in the format of (Grade -n) for Average Salary by Grade members
in the Account dimension, and then refresh the database.

This enables you to assign a salary to new hires. See Working With Alias Tables in the
Oracle Hyperion Planning Administrator's Guide.

From the Workforce Planning task list, select Add New Hires.

Complete the 3.00 New Hire Request master details form.

From the New Hire - Request tab, use the shortcut menus to add hiring requisitions, calculate
compensation, and change requisition status.

54

Readme

Documentation Feedback
Send feedback on product documentation to the following email address:
EPMdoc_ww@oracle.com
Follow EPM Information Development on these social media sites:
l

YouTube: http://www.youtube.com/user/OracleEPMWebcasts

Google+: https://plus.google.com/106915048672979407731

Twitter: https://twitter.com/HyperionEPMInfo

Facebook: https://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

LinkedIn: http://www.linkedin.com/groups?home=&gid=3127051&trk=anet_ug_hm

Accessibility Considerations
It is our goal to make Oracle products, services, and supporting documentation accessible to the
disabled community. EPM System products support accessibility features, which are described
in the product's Accessibility Guide. The most up-to-date version of this guide can be found in
the Oracle Enterprise Performance Management System Documentation Library on the Oracle
Technology Network (http://www.oracle.com/technology/documentation/epm.html).
In addition, this Readme file is accessible in HTML format.

Readme

55

COPYRIGHT NOTICE
Planning Readme, 11.1.2.3.000
Copyright 2013, Oracle and/or its affiliates. All rights reserved.
Updated: June 2013
Authors: EPM Information Development Team
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure
and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you
may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display
any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required
by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any
errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS:
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are
"commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject
to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms
of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License
(December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed
or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe,
backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for
any damages caused by use of this software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products, and services from
third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with
respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss,
costs, or damages incurred due to your access to or use of third-party content, products, or services.

Vous aimerez peut-être aussi