oracle hyperion public sector planning and budget椊渀最 刀攀瀀...
TRANSCRIPT
O R A C L E ® H Y P E R I O N P U B L I C S E C T O RP L A N N I N G A N D B U D G E T I N G , F U S I O N E D I T I O N
R E L E A S E 1 1 . 1 . 2
M A P P I N G R E P O R T I N GA P P L I C A T I O N S A D D E N D U M
CONTENTS IN BRIEF
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Creating the Reporting Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Setting Up the Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Mapping the Salary Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Mapping for Headcount and FTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Allocating Expenses to General Ledger Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Pushing Data to Reporting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
OverviewThis Addendum guides you to mapping your compensation expenses and information from aOracle Hyperion Public Sector Planning and Budgeting, Fusion Edition, application to areporting application, so you can aggregate and report on the complete data. Pushing data fromPublic Sector Planning and Budgeting applications to a reporting application enables thefollowing capabilities:
l Easy reporting on comprehensive Public Sector Planning and Budgeting data in thereporting application
l Aggregations and queries on Smart Lists, which are converted to regular dimensions in thereporting application
l Linking Public Sector Planning and Budgeting data to multiple reporting applications forvarious consolidations
For more information on mapping reporting applications, see the Oracle Hyperion PlanningAdministrator's Guide.
Summary of the steps:
l “Creating the Reporting Application” on page 2
l “Setting Up the Applications” on page 3
l “Mapping the Salary Dimensions” on page 3
l “Mapping for Headcount and FTE” on page 6
l “Allocating Expenses to General Ledger Accounts” on page 9
l “Pushing Data to Reporting Applications” on page 10
Creating the Reporting ApplicationIn Oracle Essbase, create a reporting application with these characteristics:
l It is an aggregate storage type (not block storage type).
l Create dimensions in it that correspond to each Public Sector Planning and Budgetingdimension: the seeded dimensions and the user-defined General Ledger line itemdimensions. For examples of dimension names in the reporting dimension, see “Mappingthe Salary Dimensions” on page 3 and “Mapping for Headcount and FTE” on page6.
For instructions on creating line item dimensions in Public Sector Planning and Budgetingapplications, see chapter “Preparing Line Item Budgets” in the Oracle Hyperion Public SectorPlanning and Budgeting User's Guide.
l Into the reporting application dimensions, load members that map to the Public SectorPlanning and Budgeting members on which you want to report or aggregate. You can loadmembers in multiple ways; for example, use Oracle Hyperion Financial Data QualityManagement ERP Integration Adapter for Oracle Applications.
2 Mapping Reporting Applications Addendum
See the Oracle Essbase Database Administrator's Guide.
Next, perform the steps in “Setting Up the Applications” on page 3.
Setting Up the ApplicationsYou set up two application mappings; each mapping contains different intersections.
ä To set up the mappings:
1 In Oracle Hyperion Planning, Fusion Edition, select Administration, and then Map ReportingApplications.
2 To create a new mapping, click New.
3 Under Details, enter a name and description.
For example, name the first application mapping “Salary” and the second applicationmapping “FTE and Headcount.”
4 Under Source Application, for Plan Type, select HCP.
HCP is the default name for Public Sector Planning and Budgeting applications. If youspecified another name, select it.
5 Under Reporting Application, select the Essbase server on which the reporting application resides, andthen select the target reporting application.
See “Creating the Reporting Application” on page 2.
6 Click Next.
7 See “Mapping the Salary Dimensions” on page 3.
Mapping the Salary DimensionsOn the Map Dimensions tab, map the Public Sector Planning and Budgeting dimensions andSmart Lists on the left to the reporting application members on the right.
Note: The following mappings assume you are using Position- and Employee-based budgeting.Use a similar approach for Employee-only and Position-only budget details.
ä To define the dimension mappings:
1 For each Public Sector Planning and Budgeting dimension or Smart List, select a Mapping Type, selectthe Dimension or Smart List, select its members, and then select the corresponding reporting applicationdimension.
See Table 1, “Mapping Salary Dimensions,” on page 4.
About Mapping Type:
Mapping Reporting Applications Addendum 3
l Dimension to Dimension: Displays the available unmapped dimensions in the PublicSector Planning and Budgeting application. To push data, the dimension and all of itsmembers must reside in both the source and target applications.
Dimensions that are identical between the Public Sector Planning and Budgeting andreporting applications (for example, Scenario to Scenario) are automatically mapped.
l Smart List to Dimension: Displays the available Smart Lists. When a Smart List isselected, the account members associated with it are displayed. If only one memberexists, it is automatically selected.
The following table provides guidelines for the first application mapping for Public SectorPlanning and Budgeting applications.
Note: You can select only level 0 members.
Table 1 Mapping Salary Dimensions
MappingType
Dimension/
Smart List Name
Member Selection Reporting ApplicationDimension Name
DimensiontoDimension
Account Percentage Allocation, AllocatedExpense
the name of yourAccount dimension
Smart List toDimension
Salary_Account_List Account Segment the name of yournatural account
DimensiontoDimension
Period level 0 members
For example: ILvl0Descendants(Period)
Period
Include the entiredimension in the reportingapplication.
DimensiontoDimension
Year the fiscal years to include
For example: FY09,FY10,FY11
Year
Include the entiredimension in the reportingapplication.
DimensiontoDimension
Budget Item level 0 members
For example: ILvl0Descendants(AllocationAssignments)
Budget Item
Include the entiredimension in the reportingapplication.
DimensiontoDimension
Version the version to include
For example, Final
Version
DimensiontoDimension
Currency Local Currency
4 Mapping Reporting Applications Addendum
MappingType
Dimension/
Smart List Name
Member Selection Reporting ApplicationDimension Name
DimensiontoDimension
Element level 0 members
For example: ILvl0Descendants(Element)
Element
Include the entiredimension in the reportingapplication.
Smart List toDimension
Entity_List Entity Segment your General Ledgerdimension
For example, Cost_Center
DimensiontoDimension
Position level 0 members
For example: ILvl0Descendants(Position)
Note: Applies only to Position-based budgeting
Position
Include the entiredimension in the reportingapplication.
DimensiontoDimension
Employee level 0 members
For example: ILvl0Descendants(Employee)
Note: Applies only to Employee-based budgeting
Employee
Include the entiredimension in the reportingapplication.
DimensiontoDimension
Scenario the scenario you want to report oraggregate on
Typically, the scenario member is Budget
Scenario
Include the entiredimension in the reportingapplication.
Smart List toDimension
the Smart Listthat correspondsto your GeneralLedger dimension
Create a separate rowmapping for each of yourimplementation-specificSmart Lists.
Examples:
l Activity_List
l Fund_List
l Program_List
l Project_List
See “Preparing Line ItemBudgets” in the OracleHyperion Public SectorPlanning and BudgetingUser's Guide.
the General Ledger segment member
Examples:
l Activity Segment
l Fund Segment
l Program Segment
l Project Segment
the General Ledgerdimension
For example:
Mapping Reporting Applications Addendum 5
2 Click Next to display the Point of View tab.
Dimensions that are not already mapped or that are missing from either the source or targetapplication are displayed so that you can specify a POV.
3 On the Point of View tab, for the Entity dimension, select level 0 members:(ILvl0Descendants(Entity).
All POV dimensions must have only one member selected.
For example:
4 Define the second application mapping.
See “Mapping for Headcount and FTE” on page 6.
Mapping for Headcount and FTE
ä To define the second application mapping:
1 Follow the steps in “Setting Up the Applications” on page 3 and “Mapping the Salary Dimensions” onpage 3.
2 For each Public Sector Planning and Budgeting dimension, select a Mapping Type, Dimension or SmartList name, its member selection, and the corresponding reporting application dimension name.
The following table provides guidelines for the second application mapping.
6 Mapping Reporting Applications Addendum
Table 2 Mapping for Headcount and FTE
Mapping Type Dimension /Smart ListName
Member Selection Reporting ApplicationDimension Name
Dimension toDimension
Account the level 0 members for Total FTE andHeadcount
For example: ILvl0Descendants(Total FTE),ILvl0Descendants(Headcount)
the name of yourAccount dimension
Optionalmapping forstatisticalreporting:
Not Linked
the name of yournatural account
Dimension toDimension
Period level 0 members
For example: ILvl0Descendants(Period)
Period
Include the entire dimension inthe reporting application.
Dimension toDimension
Year the fiscal years to include
For example: FY09,FY10,FY11
Year
Include the entire dimension inthe reporting application.
Dimension toDimension
Budget Item Unspecified Budget Item Budget Item
Include the entire dimension inthe reporting application.
Dimension toDimension
Version the version to include
For example: Final
Version
Dimension toDimension
Currency Local Currency
Dimension toDimension
Element level 0 members
For example: ILvl0Descendants(Element)
Element
Include the entire dimension inthe reporting application.
Dimension toDimension
Entity level 0 members
For example: ILvl0Descendants(Entity)
your General Ledgerdimension
For example, Cost_Center
Dimension toDimension
Position level 0 members
For example: ILvl0Descendants(Position)
Note: Applies only to Position-based budgeting
Position
Include the entire dimension inthe reporting application.
Dimension toDimension
Employee level 0 members
For example: ILvl0Descendants(Employee)
Note: Applies only to Employee-based budgeting
Employee
Include the entire dimension inthe reporting application.
Mapping Reporting Applications Addendum 7
Mapping Type Dimension /Smart ListName
Member Selection Reporting ApplicationDimension Name
Dimension toDimension
Scenario the scenario you want to report oraggregate on
Typically, the scenario member is Budget
Scenario
Include the entire dimension inthe reporting application.
Not Linked Examples:
l Activity Segment
l Fund Segment
l Program Segment
l Project Segment
your General Ledgerdimensions
For example:
l Activity
l Fund
l Program
l Project
For example:
3 Click Next to display the POV tab.
4 On the Point of View tab, select one member for each unmapped dimension on the left.
For example:
Table 3 POV Member Selection
Unmapped Dimensions Member Selection
Your Account dimension the account member on which to report or aggregate
For example: 511100
8 Mapping Reporting Applications Addendum
Unmapped Dimensions Member Selection
your General Ledger dimensions
For example: Activity, Fund, Program, and Project
the General Ledger segment on which to report oraggregate
For example:
Activity
For example: 00000
For example:
Fund
For example: 00
For example:
5 Click Save.
6 See “Allocating Expenses to General Ledger Accounts” on page 9.
Allocating Expenses to General Ledger AccountsBefore pushing data to the reporting application, follow this procedure.
ä To allocate expenses to the General Ledger accounts:
1 Perform the workaround for defect number 9537364, described in the “Public Sector Planning andBudgeting” section of the Oracle Hyperion Planning Release 11.1.2 Readme.
The workaround shows you how to clear the Hide runtime prompt property for theapplicable AllocDistCost business rule.
2 Select Tools and then Business Rules.
3 Select the following allocation business rule for the HCP plan type:
l For Position and Employee budget detail:
m For multicurrency applications: EP_AllocDistCost
m For single currency applications: EP_SC_AllocDistCost
l For Position-only budget detail:
m For multicurrency applications: PO_AllocDistCost
m For single currency applications: PO_SC_AllocDistCost
Mapping Reporting Applications Addendum 9
l For Employee-only budget detail:
m For multicurrency applications: EO_AllocDistCost
m For single currency applications: E0_SC_AllocDistCost
Tip: To list only the business rules that apply to the HCP plan type, clear the Plan Typecheck boxes for the other plan types.
4 Click Launch.
5 When you are prompted, select members to include in the allocation and then click Launch.
You typically select the parent member for each runtime prompt field (for example,Total Employees and All Positions).
A message confirms that the business rule executed successfully.
6 See “Pushing Data to Reporting Applications” on page 10.
Pushing Data to Reporting ApplicationsAfter setting up application mappings, you push data from a Oracle Hyperion Public SectorPlanning and Budgeting, Fusion Edition application to the reporting application, using theapplication mappings that you set up in “Mapping the Salary Dimensions” on page 3 and“Mapping for Headcount and FTE” on page 6.
Note: If you made changes to the reporting application after creating it, before you push data,refresh dimensions and members by selecting the reporting application and then clickingRefresh.
ä To push data to the reporting application:
1 Select Administration and then Map Reporting Application.
2 Under Application Mapping Name, select the two application mappings you set up.
3 Click Push Data.
A message confirms when data has been successfully copied to the reporting application.
You can now aggregate and report on data in the reporting application.
10 Mapping Reporting Applications Addendum
Mapping Reporting Applications Addendum 11
COPYRIGHT NOTICE
Public Sector Planning and Budgeting Mapping Reporting Applications Addendum, 11.1.2
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
Authors: EPM Information Development Team
This software and related documentation are provided under a license agreement containing restrictions on use and disclosureand are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, youmay not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or displayany part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless requiredby law for interoperability, is prohibited. The information contained herein is subject to change without notice and is notwarranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation 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 andagency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subjectto the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the termsof the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License(December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intendedfor use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you usethis software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, andother measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damagescaused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respectiveowners.
This software 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 tothird-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, ordamages incurred due to your access to or use of third-party content, products, or services.