Table of Contents:
If your application used Oracle Hyperion Business Rules, the Upgrade Wizard automatically converts Business Rules business rules to Oracle Hyperion Calculation Manager business rules. Release 220.127.116.11 supports onlyBusiness Rules business rules as the calculation module.
Classic application administration is now called Oracle Hyperion Planning application administration (versus Oracle Hyperion EPM Architect application administration).
The Upgrade Wizard automatically upgrades applications having Oracle Hyperion Business Rules business rules, converting them to Calculation Manager business rules. However, the Upgrade Wizard does not automatically convert Release 18.104.22.168 applications having Oracle Hyperion Calculation Manager business rules. For those upgrade instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
Online Help content for Oracle Enterprise Performance Management System products is served from a central Oracle download location, which reduces the download and installation time for EPM System. You can also install and configure online Help to run locally. For more information, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
A new diagnostic tool enables administrators to view the time it takes to open forms and ad hoc grids, and to select whether they view the load times in chart form or tabular form. The tool enables administrators to select on which forms and grids to run the diagnostics and to identify forms with poor performance so they can address their design issues.
A new tab enables administrators to manage substitution variables for all Planning applications. You can select which plan types the substitution variables apply to, their name, and their value. You can also edit and delete existing ones.
Administrators can now set up forms to include a rolling forecast window. In a traditional forecast, the forecast cycle is always tied to the fiscal year end, and the months in the forecast period keep reducing as the months in the fiscal year progress. Rolling forecasts differ from traditional forecasts in that they are continuous without regard to the annual fiscal year end period. The periods in a rolling forecast roll along based on the predefined window for the rolling forecast, as set by the administrator when defining the form.
Rolling forecasts can also include substitution variables, which act as global placeholders for information that changes regularly. When you select substitution variables as members on the form, their values are based on dynamically generated information. For example, you could set the current month member to the substitution variable CurMnth so that when the month changes, you need not update the month value manually in the form or the report script.
When Predictive Planning is installed and a valid form (not an ad hoc grid) is loaded into Oracle Hyperion Smart View for Office, planners can use the Predict item on the Planning menu or ribbon to predict performance based on historical data. To use this feature, administrators must design forms as described in the “Oracle Hyperion Planning Predictive Planning User's Guide”. (For installation instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.)
To provide greater flexibility in managing a budget's review process, Approvals workflow now supports groups of users. When assigning planning unit owners, you can assign individual users, or you can assign a group. Within a group, any user can become the owner, but only one user can be the owner at a time. Only the user assigned as an owner can perform actions. Other group members can take ownership away from the current owner. If no one is assigned as the owner, then anyone in the group can perform actions on behalf of the group without having to first claim ownership.
When assigning planning unit reviewers, you can assign individual users, a group, or multiple groups. If you select individual users as reviewers, all users must approve, and the approvals must follow the order in which the users are entered. If you select a group (or groups) as a reviewer, any user within the group can be the reviewer and can promote to the next level.
You can now create an All Years parent member that includes all years. The All Years parent member enables users to view the accumulated data across multiple years, for example, a project's total cost up to its end date. The parent member does not include the No Year member, if one is defined for the application.
If your administrator selects the Enable Cell-Level Document property for a form, from form cells, planners can add, delete, and view multiple EPM Workspace documents, even in a single cell. These documents can be a website or any file type (for example, an .XLS or .PDF file). For example, you could associate a cell with several documents with updated assumptions behind the cell's sales data.
A small red square in the cell's upper-right corner indicates that it contains cell-level documents; hovering over the red square displays the cell's intersecting members.
Planners with write access permissions to cells can add comments to cells, for example, explanations of variances or rolling forecasts. Now various planners can add multiple comments, and can subsequently view, edit, or delete comments. Cell notes also now support rich text formatting.
A small red square in the cell's upper-right corner indicates that it contains comments; hovering over the red square displays the cell's intersecting members.
If an administrator has turned on auditing for Data, planners can view the data history of any numeric, date, or text cell to which they have at least Read access. After right-clicking in a cell and then selecting Show Change History, planners view a read-only screen that displays which users changed the cell's value, when, its previous value, and its new value. The list can be sorted by ascending or descending order.
Runtime prompts now support Approvals security. You can filter runtime prompt members based on access permissions and Approvals. If you correctly set up the runtime prompt order (scenario, version, then entity, secondary member), then Approvals security can be determined and used for filtering members.
An accordian-style expandable left pane now reflects functionality appropriate to the type of user who logged in. For example, administrators view and can manage forms, task lists, dimensions, business rule security, and preferences, whereas planner user types view content that is relevant to them (for example, My Task Lists and Preferences).
When they log on to an application, planners see the My Task Lists panel and a graphical or tabular depiction of the current status of their tasks. The former Advanced and Basic views are no longer in Planning.
Planning's new user interface uses Oracle Fusion Middleware technology components, so now conforms to Oracle's Fusion standards, providing users with a familiar look and feel and consistent user experience across products. The new user interface and underlying architecture also support text that is read from right to left, such as Arabic text. The Regional Locale selection sets the language preference.
To help planners see the relevant context when working with multiple forms, administrators can now create a new form type called master composite form, which has one master form and can have multiple simple forms. In a master composite form, the selection of members in the master form automatically filters to the members in the simple forms, and the simple forms display only the details that are relevant to the members highlighted in the master form.
Administrators can set up forms so that planners can invoke them from shortcut menus. Invoking such forms using right-click (shortcut) menus, you can navigate among them by:
Clicking the hyperlinked form names at the top of the page. The links reflect your navigation flow (also called “breadcrumbs”).
Clicking the tab named for the form.
Right-clicking and then selecting the form to move to.
To help users graphically view data, administrators can design composite forms to display the data in sections as charts.
Display a form as a chart in the top section and as a grid in the bottom section so planners can see the effect of data they enter in the bottom grid (when saved) as a chart on the top.
Include the same ad hoc grid twice, one to display as a grid and the other to display as a chart. Users can then perform ad hoc operations (such as Zoom In, Pivot To, and Keep Only) on the grid and view the changes in the chart.
Create a dashboard by displaying multiple related forms as charts.
Planners can also drill down to the next level by clicking the underlined links or chart areas.
When defining a shortcut menu for business rules, administrators can specify a launch confirmation message that displays when the business rule is invoked, but before it is launched. This option enables you to provide meaningful messages to planners about the consequences of launching business rules.
Selecting from Smart Lists is more convenient now that Smart List options reflect type-ahead and filtering.
Forms that users do not have access to are automatically hidden in a composite form.
A global setting is available to set precision for currencies across all forms.
Oracle Project Financial Planning bridges the gap between the detailed projects an organization undertakes and the overall corporate impact/resources. It gives organizations a high-level snapshot of how their assets and resources are allocated, and then it monitors performance and provides information about return on investment.
Project Financial Planning addresses planning for the various tasks and resources for any project initiative with an underlying multidimensional database. Specific functionality was built to handle various scenarios and calculations that are typically used in Project Financial Planning.
The Oracle Project Financial Planning User's Guide is available on Oracle Technical Network (OTN).
The Project Financial Planning application unifies the decision making process between corporate financial planning, and project financial planning processes within a single application construct.
In many instances, there tends to be a process disconnect between decisions made around projects and decisions made as part of the annual financial planning cycle within an enterprise. Project sponsors and stakeholders may have different goals from the corporate financial targets and long range plans that drive bottom up annual plans and forecasts.
The application construct and functionality within the Project Financial Planning application ensures that the what-if impact analysis and feedback loop from financial considerations for projects is instantaneous. Since the approval processes for projects are closely tied to the approvals for financial plans and forecasts, the application’s process controls implicitly ensure agreement between project sponsors, key stakeholders, and financial decision makers. This helps ensure alignment of project plans and financial plans to financial targets and corporate long range financial plans.
Oracle Project Financial Planning enables you to accomplish these tasks:
Perform planning for Indirect, Capital, and Contract projects
Use the provided template files for importing metadata and data
Perform expense planning at a detail level or account level (labor, material, equipment)
Allocate workforce resources and capital assets to projects
Calculate driver-based overhead expenses for projects
Perform different types of revenue planning/revenue recognition based on the type of Contract projects (Time and Material, Fixed Price, or Cost Plus)
Ability to view the impact on financial statements from a project level or an entity level (Profit and Loss, Cash Flow, key performance indicators [KPIs])
Rank and approve projects based on a project score using financial measures and subjective measures (net present value [NPV], return on investment [ROI], payback, lifetime investment, risk assessment, strategic assessment, business assessment, organization missions)
Perform planning for intercompany projects and reconcile them
Track the project approval flow
Use out-of-box reports
Provides sample projects for information technology
To acquire the new decision package and PeopleSoft commitment control functionality, you must install Release 22.214.171.124. These new features are not supported for upgrades of existing applications.
Decision packages provide a mechanism for department heads or financial support staff to submit incremental requests for funding, rather than submitting an entire budget with amounts that include the new funding amount. Decision packages collectively present requests for funding along with narrative justification and supporting information that may be submitted through the review and approval process.
Decision packages contain budget requests that include the detailed budget amounts necessary to implement a decision package. Budget requests could include funding for positions and employees, personnel costs, and non-personnel related, operational costs such as equipment or property leases. Decision packages are generally, but not always, prepared by entity (department, office, bureau, branch, and so on) level budget management personnel. For example, the line item for a department's personnel budget consists of $250,000 for two full-time positions. A manager needs to request another full-time position, which requires an additional $125,000. Ordinarily, the manager would do this by submitting a personnel budget amount for $375,000 with an explanation (I require $375,000 for personnel salaries, which includes an additional $125,000 for a new position) for the amount that is an increase from his baseline budget. Decision packages and budget requests enable the manager to submit a request for the $125,000, and the approver to see the baseline and the additional funds being requested:
|Baseline decision package||Personnel Expenses||$250,000.00|
|Decision package to create a position||Personnel Expenses||$125,000.00|
Because a decision package represents a proposal that may be for a new service or a strategic outcome, the full cost for all resources necessary to meet the objective may involve multiple entities or departments. In this case, you can share a decision package with other participating entities. Preparers in each entity must enter line item expenses in the budget request. Shared entities prepare their budget requests concurrently, then promote them for review and promotion. For example, a decision package to extend a municipal emergency response system could necessitate budgets from both the Fire Department and the Police Department; in which preparers in both departments would enter expense values.
See Chapter 11 of the Oracle Hyperion Public Sector Planning and Budgeting User's Guide, available on Oracle Technical Network (OTN).
Integrating with PeopleSoft Financials and using Commitment Control budgets enable you to:
Extract actuals, budgets, encumbrances, financial references, and supporting data such as the following from the PeopleSoft Financials Commitment Control tables for use in Oracle Hyperion Public Sector Planning and Budgeting applications:
Line item budgets
Perform large scale changes to many or all budgets, and send revisions as journals back to the source system for posting while maintaining distinctions in Public Sector Planning and Budgeting budgets between original proposals, adjustments, revisions, and adjusted budgets.
Validate budgets in Public Sector Planning and Budgeting against rules in PeopleSoft Commitment Control.
Seed data back to PeopleSoft Commitment Control
Use the following to transfer data between PeopleSoft and Public Sector Planning and Budgeting budgets:
Control rules—Consist of rules for budget definitions and combinations of segments or chartfield values, both of which are used to validate line item budgets.
Line item budgets that have final approval and are posted back to budget ledgers in PeopleSoft. Line item budgets are validated against the budget definition and combination edit rules defined in PeopleSoft.
See Chapter 5 of the Oracle Hyperion Public Sector Planning and Budgeting User's Guide and the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide.
Synchronize salary properties to apply changes to basic salary data such as grade type and grade salary basis Input (how often the salary is paid) to all positions or employees, possibly in different entities and departments, to whom the salary grade is assigned. Changes to grade steps, sequences, and values are not synchronized.
Synchronize employee properties to update employee master data (pay type, for example) that you modify to:
The same employee if they are associated with another position in another entity or department
Another individual employee
All related forms, such as employee details
Synchronize compensation properties to apply changes to basic data such as the following to all existing positions or employees, possibly in different entities and departments, to whom the compensation element is assigned:
If the element is options based
If the element is taxable
If it is added to gross pay
Synchronize position properties to apply changes to this master position data to any employee who is, or will be, assigned to a position:
See Chapter 7 of the Oracle Hyperion Public Sector Planning and Budgeting User's Guide.
Increments remove the need for you to manually modify and run adjustments to salary grades and other compensation elements that change over time. Increments enable your budgets to include automatic changes such as progressions to the next salary step or to an increased benefit option value. For example, a budget for the years 2013 through 2017 could include automatic increments of 3% to value-based salary grades every second year, and annual increases in the dollar amount defined for dental benefit options.
Numbers of increment cycles run from one of the following Increment Cycle Start Dates that you select to the business rule start date that you specify. This date determines the compound factor that calculates the salary or other compensation increment value for the first cycle. The first cycle is always the time between one of these dates and the business rule start date:
Position Start Date
Employee Hire Date
Job Code Start Date
For example, if the Increment Cycle Start Date is a position start date of 2010, the increment period is yearly, the increment frequency is 1, and the business rule start date is 2012, two cycles fit in the first cycle, so the increment value is compounded twice. The business rule that applies increments runs from the business rule start date to the business rule end date.
The Start From First Cycle option enables you to include or exclude the first cycle with its compounded value in increments. Selecting Yes begins increments from the first cycle onward until the business rule end date. Selecting No begins increments after the first cycle completes and stops increments on the business rule end date.
For example, assume these increment settings for an employee hired on January 1 2009:
Increment Cycle Start Date—Hire date (January 1, 2009)
Business rule start date—January 1, 2012
Business rule end date—December 31, 2014
In this case, a cycle completes after running from the hire date January 1, 2009 to the business rule start date January 1, 2012, a total of 3 years. Increments begin on the business rule start date January 1, 2012 with an increment value compounded three times, because three cycles exist between the effective date and the business rule start date. Afterward, from second cycle onwards, increments are made in each cycle until the business rule end date.
See Chapter 8 of the Oracle Hyperion Public Sector Planning and Budgeting User's Guide.
To more quickly define and update position and employee compensation, you can now assign to them the compensation and allocation defaults specified for an entity such as a department. To apply the defaults defined for an entity such as salary grades, benefits, or allocations, use the new context menus when specifying general position and employee data:
Apply Default Compensation Elements—Apply predefined compensation defaults, such as employer-paid taxes, salary grades, and additional earnings.
If multiple changes to salary grades and steps exist, data is applied according to position start date or the employee hire date.
Apply Default Allocations—Apply the General Ledger segments (Account, Entity, Program, and so on) defined as the Salary Allocation defaults.
See Maintaining General Position Data and Managing and Specifying General Employee Data in the Oracle Hyperion Public Sector Planning and Budgeting User's Guide.
The tasks various users perform to administer and define budgets and decision packages are now listed in the My Task Lists pane. If you use decision packages and budget requests, there are some differences in the task lists displayed in this pane:
In Budget Administration, there is not a task for Mass Update Position and Employee.
In Budget Preparation, there are no subtasks for Manage Position and Employee Data. Selecting this high-level task launches your decision packages and budget requests, in which you perform position and employee data tasks such as fill to-be-hired vacancies, edit position details, edit employee details, manage pending transfers, and manage position-employee assignments.
In Budget Preparation, there are no tasks for:
Mass adjust compensation and benefits
Review and approve positions
Manage revision requests
Consequently, any task in About Performing Budgeting Tasks Not Displayed in My Tasks List in the Oracle Hyperion Public Sector Planning and Budgeting User's Guide is not invoked from the My Task Lists pane, but is performed in the appropriate decision package and its budget requests.
This release includes a large number of user interface enhancements, as described in this document. To optimize performance with these new features, you must implement the following recommended configuration.
The new, improved Planning user interface requires efficient browsers to handle interactivity provided through Web 2.0 like functionality. In our testing, Internet Explorer 7, Internet Explorer 8, and Firefox 3.x are not sufficient to handle such interactivity, and the responsiveness in these versions of browsers is not as fast as the user interface in the previous releases of Planning. For this reason, we strongly recommend that you upgrade your browser to Internet Explorer 9 or Firefox 10 to get responsiveness similar to what you experienced in previous releases. In some instances, the response times in Internet Explorer 7, Internet Explorer 8 and Firefox 3.x could be acceptable. Hence, we suggest that you uptake the new user interface only after you conduct an end user response test and you are satisfied with the results of these tests for these versions of browsers. Please note that it is still possible to leverage the old user interface and features from Planning Release 126.96.36.199. For more information, see “Using the Planning Release 188.8.131.52 User Interface and Features” in the Oracle Hyperion Planning Administrator's Guide.
The new Planning Upgrade Wizard enables you to:
Upgrade both Classic and Performance Management Architect Planning applications.
Simultaneously update multiple data source references for rehosted relational databases and Oracle Essbase servers.
Update references to rehosted Essbase servers that have reporting applications.
Former process management functionality is renamed Approvals and includes key new features:
Dynamic owner assignment
Leverage UDAs to dynamically assign owners, reviewers, and users to be notified in data validation rules. This enables administrators to set the user name in the UDA associated to the dimension member that participates in the approval process, instead of specifying the user name in the validation rule. For example, create a UDA that includes a prefix––a generic user description (for example, ProdMgr:). Then in a validation rule, instead of entering specific user names, you select the UDA method, which dynamically returns the user name stored in the UDA of the current member.
When an error occurs during planning unit validation or promotion, a report is generated that lists the data form and validation rule name that caused the error. More information is written to the server log.
View how planning units are used
A new Usage tab enables you to view planning unit hierarchy dependencies and links you to the data forms or scenario and version associations so you can remove the dependencies, if needed. Dependent objects such as data validation rules or scenario and version associations must be disassociated before you can delete a planning unit hierarchy.
Using the Classic Application Wizard in Planning or the application wizard in Performance Management Architect, you can set the first fiscal year and month and specify whether the fiscal year starts from the same calendar year or the previous calendar year. You can later set up calculations based on the calendar year, for example, using formula expressions.
Data form design enhancements:
Validation rules based on Attribute dimensions support operators such as Greater Than and Less Than, which are required for attributes of type Numeric and Date. Additionally, attribute values are supported in validation rules for If conditions.
The Not In operator is now supported in data validation rules.
In the data form list, icons now distinguish whether data forms are simple, composite, or ad hoc grids.
When designing data forms, you can set row height (with the options Medium, Size-to-Fit, and Custom). Users can also drag row headings to adjust row height while viewing a data form, regardless of the row height setting in the data form properties.
A new Use Context checkbox enables user variables to be used in the POV. With this option selected, the value of the user variable changes dynamically, based on the context of the data form.
The new PushData utility enables administrators to schedule pushing data to a reporting application during non-peak hours.
Smart List labels in Planning dimensions can be mapped to reporting application member names or aliases.
Use the Essbase @RETURN function to customize displayed messages when a business rule calculation is terminated.
The OutlineLoad utility now supports an /8 parameter for specifying that input, output, log, and exception files use UTF-8 encoding, and that UTF-8 BOM markers be written to output, log, and exception files.
Set the maximum length for cell text and notes with the MAX_CELL_NOTE_SIZE and MAX_CELL_TEXT_SIZE properties.
To configure a data source to support Essbase failover in active-passive clustering mode, you can replace the Essbase Server name value with the APS URL followed by the Essbase cluster name (for example, http://:13090/aps/Essbase?clusterName=EssbaseCluster-1). For more information, see the “Documentation Updates” section of the Oracle Hyperion Planning Readme.
The online help systems for PlanningPublic Sector Planning and Budgeting modules , Oracle Hyperion Workforce Planning, and Oracle Hyperion Capital Asset Planning are now available in EPM System dynamic help, enabling access to them from an integrated help environment.
The following new roles are available in Oracle Hyperion Shared Services:
Approvals Administrator: Typically responsible for controlling the approval process for their region, but does not need the overall Planning administrator role. The Approvals Administrator comprises these roles:
Approvals Ownership Assigner: Performs Planner role tasks, and for members of the planning unit hierarchy to which they have write access, can assign owners, reviewers, and users to be notified.
Approvals Process Designer: Performs Planner role tasks and Approvals Ownership Assigner tasks, plus, for any member of the planning unit hierarchy to which they have write access, they can change the secondary dimensions and members for the Entities to which they have write access, change the scenario and version assignment for a planning unit hierarchy, and edit data validation rules for data forms to which they have access.
Approvals Supervisor: For members of the planning unit hierarchy to which they have write access, they can start, stop, and take action on a planning unit. Approvals Supervisors can perform the preceding actions even if they do not own the planning unit. However, they cannot change data in a planning unit unless they own it.
Ad Hoc Grid Creator: Performs Ad Hoc User tasks, plus creates and saves ad hoc grids.
Ad Hoc User: Analyzes data forms using ad hoc features.
For role descriptions, see the Oracle Enterprise Performance Management System User and Role Security Guide.
With ad hoc grids, users having the appropriate access permissions and assigned role (see New Roles) can create, personalize, and dynamically change focused data slices that they frequently access. Users are not confined by the data form definition and can change the data intersection and layout of ad hoc grids (assuming that they have access to the members). For example, they can save a set of products that they work with during spring promotions so they can easily access their data. Ad hoc grids can be created and accessed in a similar ways from Planning and Smart View.
New ad hoc grid functionality:
Select which alias table the ad hoc grid uses.
Control, at a global level, how ad hoc actions are performed or how the ad hoc grids are displayed. Examples:
Set which members are selected when Zoom In, Zoom Out, Keep Only, and Remove Only operations are performed.
Display member names, aliases, or both.
Set the member level (next, all, or bottom-level) when zooming in.
Set indentation (no indentation, indent totals only, or indent all subitems with totals one level down).
During Zoom In operations that are inclusive, set whether to display the parent members at the top or the bottom of the hierarchy.
Set whether to refresh data when performing ad hoc actions such as Pivot To, Move, Zoom In, and so on.
To streamline the grid, suppress rows or columns that contain unneeded data (for example, #MISSING data, zeros, repeated members, and missing blocks on rows).
Set the number of decimal positions to display for numerical data.
Specify the text to display in cells having missing or no data or to which the user does not have access permissions.
End users can now drag row headings to adjust row height while viewing a data form, regardless of the row height setting in the data form design. After adjusting the row, they can add a new line of text to the row.
For information about new features in Oracle Hyperion EPM Architect, see and the Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide.
If you are using Oracle Hyperion Enterprise Performance Management System Lifecycle Management to migrate from a test to a production environment, and Planning does not exist in the target environment, you can use Oracle Hyperion Enterprise Performance Management System Lifecycle Management to create an application shell. See “Creating a Planning Application Shell” in the Oracle Enterprise Performance Management System Lifecycle Management Guide.
You can build budget applications using fiscal years that do not start on January 1, or that start in the previous calendar year. For example, you can define budgets in which the fiscal year for 2012 starts July 1, 2011.
Compensation budget expenses such as benefit schedules, salary, employer-paid taxes, and additional earnings are generated in the HCP plan type. Budgets for operating expenses (leases and utility expenses, for example) or revenues are maintained in the plan type 1, 2, or 3. Product implementors or administrators transfer compensation expenses, enabling General Ledger allocations and creating the line item budget, by:
Preparing applications by defining and configuring the required and custom dimensions, Smart Lists, and possibly configuring business rules to support their General Ledger allocation implementation.
Defining mappings to link compensation expenses in the HCP plan type with the appropriate dimensions in Plan 1, 2, or 3.
Pushing data whenever compensation budgets are updated or new budget cycles begin, from the HCP plan type to Plan 1, 2, or 3 and the reporting application.
After modifying or updating employee, position, and compensation expenses, you can allocate expenses to General Ledger account segments or chart fields as follows:
For all or individual entities, enabling you to simultaneously allocate the expenses for all positions, employees, or jobs in an HRMS organization
For all or individual jobs or positions in an entity
For all or individual employees in an entity
These options ensure that you can select and quickly allocate expenses for a range of personnel–for entire departments and bureaus–to specific employees or positions.
Use the Process loaded human resources data task to adapt these effective dates loaded from HRMS to calculate the period-level status and FTEs of positions and employees:
Position start and end dates
Employee hire dates
FTE start and end dates
This new task enables you to ensure that positions and employees are between these dates, and the respective period's status is updated accordingly.
Planners can activate jobs for their entities by selecting the Maintain job details task, and reviewing the jobs displayed on the All Jobs and Active Job tabs. Jobs to be activated display on the All Jobs tab. Right-click these jobs to activate them.
You can now more easily load a wide range of HRMS source system data to Public Sector Planning and Budgeting applications using the sample code and further instructions provided in Appendix A of the Oracle Hyperion Public Sector Planning and Budgeting User's Guide.
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Planning supports accessibility features, described in the Oracle Hyperion Planning Accessibility Addendum available on Oracle Technical Network (OTN).
End users can use Planning with a Web browser, or through a Microsoft Office interface using Smart View.
Promote planning units based on entity and secondary dimensions. For example, the owner of a department that includes HR and revenue accounts can promote the HR accounts first, and continue working with revenue accounts until they are ready to promote. Planning unit ownership now drives the read or write access in data forms at a more granular level.
Select and promote multiple planning units at one time.
Manage planning unit status by filtering, sorting, and setting display options for planning units to which you have access:
Filter by planning unit, process status, sub-status, current owner, location name, and location generation. For example, filter by location to view planning units that have reached a certain level of approval in the promotional path.
Sort in ascending or descending order, or use a default sort order.
See a graphical view of the promotional path.
When you are not available, use an Out of Office wizard to set an automatic action such as Delegate, Promote, or Reject. This ensures that the process continues even when reviewers are away.
Use the new actions available for the new budgeting modes.
With the new budgeting modes, end users do not have to select the next owner. Owners are determined by the system, based on the planning unit hierarchy and validation rules. New budgeting modes:
Bottom-up Budgeting: Data is input at the leaf member level (for example, children of Budget Group) and consolidated by rolling data up the organizational hierarchy. When the budget is started, data is populated for each scenario and user independently. The ownership follows the hierarchy of approval in bottom-up mode. Users can view or edit data based on access permissions defined for the planning unit. The topmost Budget Group owner consolidates individually approved budgets into a final consolidated budget.
New actions and status for this mode:
Delegate: Pass ownership to a user not on the promotional path
Take Ownership: Become the owner of the planning unit and any level 0 planning units under the selected parent planning unit
Originate: Pass ownership to the first owner in the planning unit hierarchy
Reopen: Reopen an approved planning unit
Freeze, Unfreeze: Lock or unlock related data in descendant planning units
Frozen: All related data is locked in descendant planning units
Distributed Budgeting: Budget data is entered at the leaf level of the organization, and ownership starts at the top level of the organization. Ownership is then distributed down the organization hierarchy. After ownership reaches the lower levels, budgets are submitted back to the top through the approval process. The top budget group owner reviews, approves, and loads the budgets for budgetary control, transaction control, and reporting.
New actions and status for this mode:
Distribute, Distribute Children, Distribute Owner: Assign ownership to members at the current level of the planning unit hierarchy, to children of the current owner, or to the level 0 owner defined during planning unit hierarchy creation
Submit, Submit to Top: Give ownership to the next level or to the top user defined in the hierarchy
Reopen: Reopen an approved planning unit
Distributed: Multiple users are reviewing the budget
You can still use the free-form budgeting mode, in which planners select the next owner from a drop-down list.
Validation rules can prevent the planning unit from being promoted, or they can change the promotional path. For example, an HR reviewer can be included if expense boundaries are exceeded for budget items such as salaries or new hires.
Validation rules can be used for matrix-based organizations, and can be implemented by department and by product. For example, after department managers promote a plan, users in charge of the budgets of their products across all departments automatically become the owner of all data related to their products for all departments.
Validate planning units by running data validation rules associated with the planning unit. Conditions in data validation rules must be met before the planning unit is promoted.
The validation process returns the status of the planning unit. When planning unit validation indicates a problem, such as invalid data or additional approval required, review a validation report to correct data errors and take any necessary actions.
Use data validation rules to maintain data integrity, for example, to ensure that entered values are between minimum and maximum values. Errors or warning messages are generated if entered data violates validation rules.
Data forms can display data validation messages, tooltips, and cell colors when data validation errors occur. For example, a tooltip can instruct you to enter data that meets certain criteria or that fits within a specific range.
If data forms contain data validation messages, a Data Validation Messages pane displays on the right side of the data form. View messages specified by the administrator, and click links to set the focus on the cell associated with the message.
Sort rows and columns within the hierarchy or across data to view data in ascending or descending order.
Filter rows and columns to customize the display in the data form; keep or exclude members using simple functions that compare against a specified value.
Use right-click context menus in data cells for regular planning actions: Cut, Copy, Paste, Clear, Delete, Edit, Adjust Data, Grid Spread, Mass Allocate, Insert Comment, Supporting Detail, Add/Edit Document, and Lock/Unlock Cells.
Use context menus that are displayed in the POV, page, row, column, members, and cells; for example, a menu may be available when you right-click Account members or when you right-click a data cell.
New menu item to return to the previous data form.
Use ad-hoc analysis features in data forms to analyze data and save personalized views of data. For example:
Pivot to move a dimension to another area, such as moving a row to the POV, page, or column.
Move to the left or right from a row, page, or POV. Move up or down in a column.
Zoom in to a hierarchy and show descendants that are not displayed by default in the data form definition. For example, if the data form displays Year Total, click the Year Total member, and open the Year Total hierarchy to view a dimension. View a member's children and add them to the data form.
Zoom out a level, based on your access permissions. For example, click a member and zoom out to the member's parents to add them to the data form.
Remove only the selected member from the data form definition.
Keep only the selected member, and remove all other members from the dimension.
Select members using a member selector, based on your access permissions; selections can go beyond the current form definition.
After making ad-hoc changes, save and rename a personal version of the data form to access it again later.
Ability to show the consolidation operator associated with a member with the member name, such as Sales (+); set preferences to control the display of consolidation operators in data forms
Separate notifications for task lists and process management
New user settings for process management display
Improved navigation with restructured menus
Improved look and feel with new colors and icon-based indicators for data forms and task lists
With this release, end users can perform their planning activities completely in a Microsoft Office environment without having to go to the Web. All of the new end user features mentioned previously are available through Smart View. Key features added to Smart View in this release to support a fully functional end-user experience:
Planning task lists are now integrated into Outlook, so planners can integrate their tasks into Outlook tasks, and can perform these tasks from within Outlook. Planning data form tasks are seamlessly launched from Outlook into the familiar Excel interface
Planning task lists are available in Office, including task status and task reports; users can perform tasks in Excel, and have them automatically synchronized with the Web
All process management end-user functionality can be accessed from Outlook and Excel
Data validation, including validation indicators and messages
The ability to monitor the status of Planning jobs in the Job Console
Composite data forms in Microsoft Office with shared dimensions that are automatically synchronized across multiple data forms
Mass Allocate and Grid Spread for spreading values
Copy data across versions for scenario-entity combinations
Dynamic user variables that allow end users to select and change user variable values directly in data forms
Custom right-click menus for data and metadata
Member formula display
Setting Planning user preferences within Smart View
Data forms enabled for ad hoc allow users to slice data and save a slice to create reports or share with other users
Improved look and feel, including a Smart View home page
For information about Smart View, see the Oracle Hyperion Smart View for Office New Features and Oracle Hyperion Smart View for Office User's Guide.
Following are the key features for Planning users when using Smart View for Outlook.
Smart View task panel:
Task status, task reports, import, and removal of tasks
The ability to refresh task lists
Planning tasks displayed as Outlook categories:
Task due dates and other task fields
Customizable task fields
Auto synchronization of task completion status changes
Outlook reminders driven by tasks alter dates and due dates in Planning
Planning task-based launch actions are enabled from within Outlook:
Business rule tasks
Launch a URL from a task
Execute process management actions
Launch data form-based task actions into Excel:
Users are taken to specific tasks that need to be acted on
Single sign-on support
Can be used with native Outlook task capabilities:
Display of tasks in Outlook Calendar with synchronization to mobile device
Display of tasks in Outlook task/status bar
Following are the key features for Planning users when using Smart View for Excel.
Planning task lists in Excel:
Task status, reports, instructions, alerts, due dates, and other information
Refresh task lists and update task completion status
Visual color-coded display of completed and overdue tasks
Support for granular, matrix-based, and data-driven planning unit definition
Status changes and all planning unit actions
Promotional path display
Flexible actions, including take ownership and the ability to select multiple actions
Out Of Office setting
Planning unit status display
Annotations with URL links to attachments
Validation reports displayed as tasks for corrective actions
Composite data forms:
Color-coded display and navigation of shared global and section dimensions
Display instructions for multiple data forms
Data validation and messaging:
Color-coded display of shared global and section dimensions
Validation message display
Color-coded validation indicators
Mass Allocate and Grid Spread
Support for dynamic user variables
Member formula display on row, column, page, and POV
Planning Job Console
Option to suppress Excel right-click menus and use Planning right-click menu actions, for data cells and metadata
Smart View options:
Planning user preference settings
Planning-specific Smart View Options
New default cell styles for Planning with an Office look and feel
Planning Ad Hoc:
Launch a data form into Ad Hoc mode on the fly
Save an Ad Hoc slice as a Smart Slice definition
Cascade an Ad Hoc slice across a selected dimension
Smart View connection manager:
Easy entry point for connections, icon-based recently used items
Unified display of connections
Products filtered for display, servers and applications in tree view
Separate sub-trees for data forms and tasks
Icons to easily identify tasks and all types of data forms (single, composite, and Ad Hoc)
Oracle Hyperion Shared Services connections (based on common registry)
APS Connections (Ad Hoc for Planning)
Named connection to Planning provider
On-the-fly URL connections
Easy navigation across connections
One-click disconnect from all connections
Action pane for context-based actions
Newly designed Office ribbons, including ribbons for Planning and Planning Ad Hoc
Data cell level context menus for drill through, document attachment, and cell comments
Application level right-click access to application level actions:
Offline wizard, copy version
Process management, business rules, user preferences
To implement business policies and practices, administrators can build data validation rules that are checked when conditions are met in data forms. Rules can generate validation messages, enforce limits on submitted planning unit data, and designate a specific reviewer or owner to review data that meets some condition. For example, data validation rules can ensure that a department’s capital expenses fall within designated guidelines.
Set up the planning unit promotional path based on the review process for owners and reviewers in the planning unit hierarchy. The review process follows the promotional path unless an event triggers a change in the path, for example, exceeding expense boundaries for budget items. The path can also change if the current owner returns the budget to the previous owner for additional information, or requests help from an authorized user who is not necessarily on the promotional path. In addition, administrators can set up the hierarchy so that some users receive notifications for changes in planning unit status.
Use planning unit hierarchies to adapt the budgeting process to all types of organizational requirements.
Planning units are now a combination of the entity and other dimensions. For example, if an application includes all of a company's products, the planning unit hierarchy for North America can include dimensions and members appropriate to products sold in North America. Similarly, the planning unit hierarchy for the European division can include dimensions and members for products sold in Europe. Within the same process management hierarchy, Latin America entities can be enhanced using the Account dimension, creating planning units such as Entities by HR, Entities by Capital Expenditures, and Entities by Revenue.
Use preset budgeting mode templates to create hierarchies that are bottom up, distributed, or free form.
Include dynamic links to dimensions based on generation numbers for the entity dimension and the secondary dimension that is used. For example, automatically add generations 0 to 3 in the entity or segment dimension to the planning unit hierarchy. If a change occurs in the dimension, the planning unit hierarchy can be easily updated.
Import and export planning unit hierarchies.
Create planning unit hierarchies that differ by scenario and version. For example, the Budget scenario can have a large planning unit hierarchy consisting of departments, accounts, and products, while the Forecast has a simpler process organization with fewer levels of approval.
Drag and drop dimensions with many ease-of-use enhancements for selecting data form properties
Use live preview to view dimensions assigned to the POV, columns, rows, and page axes
Add data validation rules to provide color coding or special messages to be displayed to end users in data forms; multiple validation rules can be added at the cell level, at the row or column level, and at the grid level of a data form
Add formula rows and columns, including blank rows and columns; many Oracle Hyperion Financial Reporting formula functions are supported
Easily create data forms by dragging and dropping within the Layout manager
Share dimensions across all data forms within the composite, or only for data forms in a section
Divide the layout into multiple tabs so that data forms in each section of the composite are displayed as tabs
Customize section labels
Customize data form display names
Most of the functionality described here is available for both administrators and end users:
Search by member, alias, description, or UDA
Find an exact match for a single word or multiple words
Use wildcard characters, including characters within lists or ranges
Collapse and expand members
Narrow down the display using ad hoc functions, attributes, levels, or generations
Set multiple display options for member name and alias, description, and count
Select user variables, substitution variables, and attributes in a separate tab
Select members across multiple dimensions, where applicable, through a single member selector
Place selections in separate rows or columns, which is useful for easy data form creation
After a task list is completed, clear the completion status, due dates, and alerts for all tasks in a task list; this allows tasks to be reused for a future planning period
Select default page members for data form type tasks
With reporting application integration, you can map dimensions between Planning applications and reporting applications to enable:
Easily reporting on Planning data in a reporting application
Aggregations and queries on Smart Lists, which are converted to regular dimensions in the reporting application
Linking Planning data to multiple reporting applications for various consolidations
After setting up application mappings, you can push data to reporting applications. Planning validates the selected application mappings, and then pushes the mapped Oracle Hyperion Planning dimension data to the reporting application dimensions. Reporting applications can be either Oracle Essbase block storage or aggregate storage databases.
Load incremental dimension members based on unique driver identifiers. For example, when loading employee data, load new budget line item detail for Salary Grades, or update existing line item detail. Use Advanced Settings to load and update data for dimension hierarchies based on unique identifiers for the driver dimension.
New Outline Load utility features:
Load Smart Lists and Smart List dimension members using DX:HSP_SMARTLISTS.
Export planning unit hierarchies, including owners, reviewers, and users to be notified, to a file using /E:outputFileName. The hierarchy can include sub-hierarchies.
Public Sector Planning and Budgeting is a Web-based integrated budgeting and planning solution in the EPM System suite. It helps public sector and higher education organizations manage existing and projected budgets that are based on reliable information from Human Resource Management Systems and General Ledgers.
Human capital planning features provide out-of-the-box configurable and expandable position and employee expense budgets. Combined with sophisticated process management functionality, these features help you project and evaluate the impact of employee compensation and benefits on overall budgets. The application enables you to forecast the impact of new positions, workforce reductions, contract proposals, as well as compensation and benefit changes as they occur throughout the year. Using a Microsoft Excel-like interface, you can plan for human capital expenses using the budget detail that is most appropriate for your organization's needs:
Both positions and employees
Budgeting activities can be distributed across an organization with planners having different views to make the process easy, resulting in greater accuracy, efficiency, and transparency. Notifications can be issued when budget issues need attention or the budget is completed. Users can distribute, consolidate, monitor, and manage budgets, including revisions, through an approval process. Public Sector Planning and Budgeting optimizes the allocation of scarce public resources and provides consistency and control throughout the budget process.
Oracle Hyperion Public Sector Planning and Budgeting features include:
Manage position data such as department or organization, job code, position type (for example, shared or pooled), status, and other compensation details.
Manage employee-related data such as department, salary (annual or hourly), salary grade, benefits, FTE, location, status, employer-paid taxes, and union information.
Enable allocating budget amounts to different programs, projects, or other chart of account dimensions.
Integrate with Human Resource Management Systems and General Ledgers for tightly integrated budget preparation and execution processes through the use of Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications.
Enable detailed and highly formatted budget books and reports through the use of Oracle Hyperion Financial Reporting.
Help build budgets from prior years or prior versions.
Support multiple scenarios.
Distribute work and merge data into an overall process.
Enable organizations to define approval processes that fit their unique requirements.
Set constraints and validate the data against them.
Handle overrides with comprehensive audit trails to ensure accuracy.
Enable integrating and aggregating position budgets into operating expense budgets.
Enable budget managers to prepare, distribute, review, and approve budgets that use organizationally defined time frames, account codes, and data field combinations.
Include date-driven calculation logic for the entire organization.
Enable spreading and allocating values by organization or by using attributes as drivers.
Support mass updates and defaults based on changes to HRMS salary and other structures.
Support working with data forms using Oracle Hyperion Smart View for Office.
The latest product documentation is available from Oracle Technical Network.
Oracle Configuration Manager (OCM) integrates with My Oracle Support and provides configuration information for Oracle software. It assists in the troubleshooting, maintenance, and diagnostics of your EPM System deployment. For more information about Oracle Configuration Manager see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
With this release, many EPM System products support hostnames that resolve to IPv6 addresses. See the Oracle Hyperion Enterprise Performance Management System Certification Matrix. IPv4 support (both hostname and IP address) remains unchanged from earlier releases.
Oracle Enterprise Performance Management System supports the following types of SSL configurations:
Full SSL Deployment (including data access)
SSL Terminating at the Web Server
SSL Accelerators (Off-loading)
For more information on the SSL configurations, see the Oracle Enterprise Performance Management System Security Administration Guide.