1. Oracle HFM 11.1.2.2 Implementation Boot Camp Presented by Saravanan Singaravadivelan Developed by Saravanan Singaravadivelan Senior Consultant Qubix International Ltd

2. VIII. End User

3. End User – Workspace Web user interface used to access all Oracle Hyperion and non-Oracle Hyperion content Modular business intelligence platform, providing access to management reporting, query and analysis capabilities for a wide variety of data sources in a single environment Allow users to set preferences for the Hyperion products installed.

4. End User – Data Grids Data grids offer user capabilities to view the data in any possible way. End users are encouraged to create grids or find existing grids that meet their needs. Point of view usage critical to data grids. Grids can be saved with security class or marked private to limit access. You can perform consolidation and translation of data using data grids

5. End User – Data Forms Convenient for input of supplemental data Should not be used for balance sheet or profit and loss input – supplemental input only Changes to balance sheet, profit and loss accounts should be via journals Users should not have ability to create/modify forms Data forms can be created via: Data forms wizard if simple forms Excel if complex forms with heavy formatting Data forms can be exported or imported to Excel

6. End User – Journals Journals used for debit/credit style adjustments Are stored in one of four value dimension members – effect on data depends on which member used Security controls whether users are limited to creating journals, approving journals, and/or posting journals Journal listings and detail can be filtered and reported Administrator must open the period before journals are allowed Periods can be closed and reopened as needed

7. End User – Intercompany Matching Intercompany accounts use the ICP dimension to store the partner entity Intercompany balances are, by default, eliminated at the first common parent Intercompany accounts can be matched against others (like IC receivable vs. IC payable) or can be eliminated one-sided (IC sales eliminating to IC cost of sales [and netting against non-IC cost of sales]) Intercompany setup is done in metadata: Which entities can be partners Which accounts are designated intercompany Which account is the plug account for intercompany account(s) The plug account will hold any out of balances among the intercompany accounts If everything matches, the plug account will be zero Reporting is available for all users to analyze and reconcile intercompany balances

8. End User – Tasklists Tasklists can be used to direct users through specific tasks, grids, forms, etc. Depending on security role provisioning a user can be restricted to tasklist navigation only Tasklists can be exported / imported out of Workspace They can contain folders, tasklists, documents, form, grid, links to web pages, reports and tasks

9. End User – Process Control Process control is subject to design and controls implemented by the administrator Validations must be passed and the data calculated before signoff can occur Once a user signs off on the data, they lose the ability to change – any required change would have to be done by someone at a level above them or the data rejected back to them Accounts and customs can be signed off in phases: financials could be the first phase and supplemental data in the second phase

10. Exercise: End User

11. Main Steps: Lab 7 Navigate HFM Workspace and set user preferences Maintain Data Grids Maintain Data Forms Maintain Journals Create and modify intercompany matching reports Maintain Tasklists Manage Process Control

12. A Q &