1. Hyperion Planning & Budgeting 11.1.2.2 Linda Benoit
fy13
fy14
Linda Benoit
Pinellas County Office of Management & Budget

2. Hyperion Databases
Oracle Hyperion Public Sector Planning and Budgeting is really 2 databases: 
Line Item Budgeting for Expenditures and Revenues
Position Budgeting for personal services costs
A Hyperion process runs to push the position data to the line item budget

3. Hyperion Public Sector Planning & Budgeting Oracle Human Resources
Hyperion Integration
Oracle Projects
Oracle General Ledger
Hyperion Public Sector Planning & Budgeting
Oracle Human Resources

4. Hyperion Planning & Budgeting: Module Integrations
General Ledger
A regularly scheduled data feed from the Oracle E-Business applications to Budget will occur. Final budget will be sent to GL after adoption
Project Accounting
Project information will be extracted from Projects and fed to Hyperion once when CIP budgeting is complete
Human Resources
Employee and position data will be extracted from HR and used as a basis for position budgeting in Hyperion

5. Oracle HRMS Integration Oracle HRMS
Time
&
Labor (
OTL )
Advanced
Benefits
OAB
Oracle Learning
Management
OLM
Oracle Payroll
Financials
Procurement
Oracle Projects
Hyperion
Budgeting
Business
Intelligence
Reporting
Oracle Human Resources
Manager Self -
Service
Employee Self
All Oracle HRMS applications have a single source of information because they share the same tables within the Oracle database. This eliminates data redundancy, reduces the possibility of conflicting data in different databases and creates a consistent, complete and reliable picture of every employee.

6. General Ledger Integration Oracle General Ledger
Financials
General
Ledger
Oracle Human
Resource
Management
Oracle Projects
&
Grants
Accounting
Procurement
Accounts Payable
Accounts Receivable
Assets
Human Resources
Payroll
Advanced Benefits
Time
Labor
Self -
Service HR
Learning Management
Hyperion
Budgeting
Other Subledgers
Reporting ,
Dashboards
Business Intelligence
As shown in this illustration the GL is integrated with other Oracle modules, with the modules and subledgers feeding data to GL. In turn, information can be extracted from GL through online inquiries, for budgeting, reporting and analysis.
Planning &

7. Hyperion Planning & Budgeting: Ownership of Data
The Office of Management and Budget (OMB) is the business owner of the Hyperion Planning & Budgeting application.
Prior actual account balances are interfaced in from GL.
Position records are interfaced in from HR.
Budget submissions are entered by departments.

8. Hyperion Planning & Budgeting: New Terminology
Dimensions
Parents
Children
Multi-Dimensional vs. Table Drive Data
Cube
Intersection
Point of View (POV)
HR Organization (Org)

9. Line Item Dimensions
Year – The budget year we are working on. (In Jun-13 it is FY14)
Period – The sub-divisions of a year (Total Year, Quarter, Month)
Scenario – The segment of the budget information we are working on. (Prior Year Actuals, Current Year Budget, Current Year Estimate, Proposed Budget, Decision Package1, Decision Package2)
Version – The stage of the budget that we are working on. (Baseline, Target, Department Budget, County Administrator Budget, Proposed , Adopted)
Fund – The GL Fund segment. (In Budget, there’s an F prefix, like F0001, general fund)
Entity – The GL Center segment. (In Budget, there’s an C prefix, like C321110, OMB)
Account – The GL Account segment. (In Budget, there’s an O prefix, like O Professional Services) (That’s O, as in object code)
Program – The GL Program segment. (In Budget, there’s a PM prefix, like PM1001 Administration)
Project – The GL Program segment. (In Budget, there’s a P prefix, like P000007A, Public Safety Facility)
Future – The GL Future segment. (In Budget, there’s a FU prefix, and one value FU )
Plan Items – this has only 1 value by default, Unspecified Plan Items.

10. Line Item Forms

11. Budget Versions BUDGET STAGES Stage 1 (aka Baseline) Target
Department Budget
County Administration
Proposed Budget
Public Hearing 1
Public Hearing 2
Adopted Budget

12. Position Budgeting Dimensions
Entity – The HR Organization (Org) from the HR system. (Example, BCC:Office of Management and Budget or BCC:Planning)
Year – The next budget year we are preparing.  (In January-2013, it will be FY14)
Scenario – The segment of the budget information we are working on. (Current Year Estimate, Proposed Budget, Decision Package1, Decision Package2)
Version – The stage of the budget that we are working on. (Baseline, Target, Department Budget, County Administrator Budget, Proposed , Adopted)
Position – The position number from HR.  Positions are assigned to an HR Org.
Job Code – The Job Code from HR.  Job Codes are assigned to Positions.
Compensation Elements – These are the components of total compensation for an employee or a position. (Salary grade, additional earnings, employer-paid benefits, employer-paid taxes)
Budget Items – These are the components needed to define position budgets. (FTE, Status, Allocation Assignment Costing)
Account - this contains additional information about a position, like Pay Type, Default Weekly Hours, Salary Basis, Position Type, etc.

13. Position Budgeting Summary

14. Manage Salary Grades

15. Other Compensation Elements

16. Position Details-General

17. Position Details-Salary Grade

18. Position Details-Other Earnings

19. Position Details-Benefits

20. Position Details-Allocations

21. Line Item Reports

22. Line Item Reports

23. Position Reports

24. Position Reports

25. Position Reports

26. Smartview

27. Key Points Flexible by design Need for knowledgeable technical staff
Reports are all custom
Database design defines processing speed
Position calculations are processes
Line item roll-ups are processes

28. Questions and Answers