Hyperion Planning & Budgeting 11.1.2.2 https://hypprd.co.pinellas.fl.us/workspace/index.jsp fy13 http://hyperion.pinellas.local:19000/workspace/index.jsp fy14 http://opusapp4.co.pinellas.fl.us:9704/analytics/saw.dll?bieehome&startPage=1 Linda Benoit Pinellas County Office of Management & Budget 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 Hyperion Integration Oracle Projects Oracle General Ledger Hyperion Public Sector Planning & Budgeting Oracle Human Resources 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 Oracle HRMS Oracle HRMS Integration Oracle Time & Labor (OTL) Oracle Advanced Benefits (OAB) Oracle Payroll Oracle Learning Management (OLM) Oracle Financials Manager Self Service Employee Self Service Oracle Human Resources Oracle Procurement Hyperion Budgeting Oracle Projects Business Intelligence & Reporting Oracle General Ledger General Ledger Integration Accounts Payable Accounts Receivable Assets Oracle Projects & Grants Accounting Oracle Human Resource Management Oracle Financials Oracle General Ledger Other Subledgers Hyperion Planning & Budgeting Human Resources Payroll Advanced Benefits Time & Labor Self-Service HR Learning Management Oracle Procurement Reporting, Dashboards, Business Intelligence Hyperion Planning & Budgeting: Ownership of Data • Hyperion Planning & Budgeting – 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. Hyperion Planning & Budgeting: New Terminology • Dimensions – Parents – Children • Multi-Dimensional vs. Table Drive Data • Cube • Intersection • Point of View (POV) • HR Organization (Org) 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 O5310001 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 FU0000000) Plan Items – this has only 1 value by default, Unspecified Plan Items. Line Item Forms Budget Versions BUDGET STAGES • Stage 1 (aka Baseline) • Target • Department Budget • County Administration • Proposed Budget • Public Hearing 1 • Public Hearing 2 • Adopted Budget 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. Position Budgeting Summary Manage Salary Grades Other Compensation Elements Position Details-General Position Details-Salary Grade Position Details-Other Earnings Position Details-Benefits Position Details-Allocations Line Item Reports Line Item Reports Position Reports Position Reports Position Reports Smartview 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 Questions and Answers