Hyperion Financial Reporting (HFR) - Interview
1. What are the data sources supported by Hyperion Financial Reporting?
3 data sources like HFM, Essbase, planning. These are the data sources which are supported by Hyperion financial reporting.
2. Which is used to store the created reports in Hyperion Financial Reporting?
It stores the reports in central repository.
3. What is the difference between Hyperion Financial Reporting studio and web client?
Reporting studio enables you to create, edit and delete the report objects, report and snap
Shot reports. Web client enables you to book of reports, schedule batches, view batches and
Schedule for future Processing.
4. What is Report object?
Report objects are basic components for designing reports in Financial Reporting Studio.
Report objects include text boxes, grids, images, and charts.
5. What is the need of studio work space?
It is to open a new or existing report in the report designer and access the repository.
6. What is the need of property sheet?
The property sheet enables you to set various options for the currently selected reports.
7. What we need to do display and hide the property sheet?
Click View property sheet.
8. To provide the ability to report which are used to categorize the data in general ledger?
Chart of accounts.
9. How many data bases are used to connect Hyperion financial reporting studio?
Single data base is used to connect reporting studio.
10. What are the steps to create a new report?
Click on file, New, Click on new report button.
11. What are the required components to create grid?
Point of view,
12. Relationship functions allow reports to be more flexible by relying on hierarchies within the
AND/OR logic functions can achieve complex reports.
13. When adding a member, select the member and then click the Add Relationship button?
14. Why are dimensions listed on the user POV when changing them has no effect on the grid?
Multiple grids can be included in a report, where one or more of the grids are affected by
Changes to those dimensions on the user POV.
15. Why is the grid POVs not displayed in the Report Designer Workspace?
If the administrator chooses to disable the grid POV, Workspace viewers cannot see it.
16. How will a user running Workspace know that the dimension is set on the grid POV?
The Report designer should design the grid with a text row footnote that the grid POV for a
Dimension is set to a particular member in the grid. Another option for the Report designer is
to put the dimension value into the row or column headers. If the designer turned off the grid
POV, the column description (using a custom heading) would correctly denote that the grid is
Displaying Actual for the Scenario dimension.
17. How can a report are designed so that any changes to a user's user POV changes the members selected from a row, column, or page axis on a grid?
Use the CurrentPOV member for the selected axis or choose a member selection function with
CurrentPOV as the member parameter. When the report runs, the axis value is taken from the
user POV. You can design a grid so that all axis values are taken from the user POV, making the
report completely dynamic on a per user basis.
18. Why do you need a book POV?
It allows anyone running the book to use the same default values for all grids in all reports in
the book simultaneously each time the book is run. It is specific to a database connection for a
book, but not specific to any report or grid object in a report in that book. As the book POV
values are saved with the book itself, changes to the book POV do not affect the book designer's
19. What are Report Member Selections?
The Report Member Selections define the values for any dimensions not on a grid's row, column,
or page axis or set in the grid POV for all Grids in a specific report in the book.
20. Why not just call Report Member Selections the report POV?
All POVs allow a single member to be set for a dimension. Report Member Selections allow
Multiple members to be set for a dimension. If multiple members or member selection functions resulting in multiple members are set for a dimension, the report in the book is run for each
member. If multiple members or member selection functions resulting in multiple members are
set for multiple dimensions, the report in the book is run for all combinations of those members.
21. Why do you need a batch POV?
It allows anyone scheduling the batch to use the same default values for all grids in all reports
in the batch simultaneously when the batch is run. It is specific to a database connection for a
batch, but not specific to any report or grid object in a report in that batch. Since the batch POV
values are only saved when the batch is scheduled, you can set different values for the same batch.
Changes to the batch POV do not affect the batch designer's user POV. Also, the changes to the
batch designer's user POV do not affect the batch POV.