Oracle has recommended settings for Internet Explorer (IE7, IE8, IE9, IE10 and IE11) when using Hyperion products. I get this question a lot from my clients, so I thought I would share Oracles suggested settings. Without changing these, there will be intermittent problems, and frustration points.
This post looks at the “Allow Expansion” functionality in Financial Reporting Studio. “Allow Expansion” is a great feature, as it gives the user more flexibility when running and displaying reports. However, it can also require more setup work as it makes the report more complex. Two situations that I encountered recently:
This post looks at the “Allow Expansion” functionality in Financial Reporting Studio. “Allow Expansion” is a great feature, as it gives the user more flexibility when running and displaying reports. However, it can also require more setup work as it makes the report more complex. Two situations that I encountered recently:
In Hyperion 11.1.2.1, there is a change in how security is deployed. If you are having an issue deploying Planning security with Essbase adhoc access, and the user can’t
you are not alone. Read more
Kscope was another fantastic event. Kudos to those responsible for organizing it. Thank you to all the speakers who volunteered their time and shared their knowledge. The most frequent request Josh, Rob, and I had, was to make our presentations available. They are available on the Kscope site, but many of you don’t have access. So, we are happy to make them available here.
I also had tremendous feedback on the ribbon. At least half the participants in our sessions used it. We got a couple of great recommendations as well. With some luck (meaning my schedule slows down a little), I will be working on those in the near future.
Download Josh Forrest’s presentation on Hyperion Financial Reporting
Rob Donahue’s presentation on Hyperion infrastructure
Download Kyle Goodfriend’s presentation on Hyperion Planning
All developers understand the power of using objects during development activities, a concept that can be leveraged in the development of Oracle/Hyperion Financial Reports. Utilizing saved objects allows the development team to deliver a product in less time and provides the ability to quickly react to future report modifications. The information below (1) provides common saved object examples and (2) displays how saved objects are created and used.
KScope12 is the premier conference for Hyperion techies and up-and-comers. Whether you are looking to brush up on your skills, learn new skills, or see how others overcome challenges, you will want to participate in this event. If your organization values your development and has a budget for these growth opportunities, mark your calendar for June 24th through the 28th. Registration is open, and as more information is available, it will be published at In2Hyperion.
Presenting a topic is a great way to reduce the cost of the trip. It’s a great way to get your name out in the community as well. If you have something that you think would be valuable for other experts to hear about, submit an abstract.
We hope to see you there. Visit www.kscope12.com for all travel details and abstract submissions.
When developing it’s always best to avoid “recreating the wheel” and the same concept applies when building reports in Hyperion Financial Reporting. An important step in the design phase centers on report row and column sets; these are simply the groups of members which display in the rows and columns of each report. Any reports that “share” groups of members, whether in rows or columns, provide an excellent opportunity for creating Hyperion Row and/or Column Templates. These templates can then be referenced in additional reports, resulting in decreased development effort and less maintenance.
Benefits: When needing to create multiple reports which have similar or identical row and column sets, the user can save time by creating one standardized row and column set, saving it as an object in the repository, and reusing it for multiple reports. The user also has the ability to modify a row/column template at any point and resave it into the repository which automatically updates all grids linked to the template. Read more
When using Workspace to view reports, some users have seen excessively large numbers that don’t belong. If you are having this issue, it could very well be because the default Essbase query engine in 11.1.1.x is the MDX query engine, which can cause documented bug 9062413. Essentially, this bug will cause users to see the same astronomical number in every cell that sits on an intersection to which the user does not have security access. Understandably, this can cause some concern. This issue is expected to be fixed in a future release, but until then, the query engine will need to be manually changed.
The first option is to fix the issue at a report level. This is a relatively quick process and is a good idea if you only have a handful of reports. To change the query engine setting for a particular report, follow the steps below:
1. Open the report.
2. For each grid, select the entire grid.
3. Right-click and select Data Query Optimization Settings.
4. Deselect the option “Essbase Queries Use MDX.”
5. Save the report.
Repeat the above process for each report.
For users that have a larger number of reports, a better option may be to change the query engine in the properties file on the server. The benefit to fixing the issue in the properties file is that changes only need to be made once, and all reports will reflect this change.
The file that needs to be edited is located on the Financial Reporting (app) server, typically on the path D:\<Hyperion Home>\products\biplus\lib where <Hyperion Home> represents the root location of the Hyperion install. The file that needs adjusted is the fr_global.properties file.
Open the properties file and add these lines:
# MDX Query Engine has been set as the default in Essbase 11.1.1.x. This can cause bug 9062413
# which may cause unauthorized users to see a long series of numbers in each cell when running
# reports. To solve this issue, the below line was added, which switches the query engine.
EssbaseUseMDX=false
Any line preceded by “#” is commented out. Therefore, these can say whatever you prefer, but should give anyone that views this file a good indication why this text is in the file.
Once the properties file has been updated, the following services must all be stopped in the following order, then started in the same order for the changes to take effect.
1. Hyperion Financial Reporting – Print Server
2. Hyperion Financial Reporting – Report Server
3. Hyperion Financial Reporting – Scheduler Server
4. Hyperion Financial Reporting – Web Application (Note – This service may be on the FR (Web) server, not the FR(App) server like the other three services.)
Note – This modification will apply to everyone using the server on which they are made, so be careful when making changes to a shared server.
The ability to import font types into Hyperion Financial Reporting is a common request by many companies, typically a request resulting from corporate reporting standards. Not only is this possible, it’s a quick and easy exercise that is detailed out below.
Step 1: Locate the Font Folder.
The font type files (normally identified by a .TTF or .ttf extension) can be found in the “Fonts” folder located in your Windows directory (Likely on your ‘C’ drive). The key here is locating this folder on the server where Hyperion Financial Reporting has been installed.
Step 2: Copying& Pasting the New Font File.
This is as easy as it sounds… just copy and paste the new file into this directory.
Step 3: Creating a Report.
Opening Hyperion Financial Reporting and create/modify a report. When selecting the font type, notice the new Font Type that was just added in Step 2 above. Note that it’s best to close the Financial Reporting client before importing the new Font file onto the server; this will insure that the client will recognize the new file.
