4Maintenance and Migration

This chapter contains the following:

How to Manage Financial Reporting Studio Versions

You could run into issues with Financial Reporting Studio reports if the Financial Reporting Studio version on your client is different from the Financial Reporting server version in the application. You must therefore manage the Financial Reporting Studio client version during the course of the regular Oracle Fusion Applications Cloud updates.

Using Financial Reporting Studio Between Test and Production Updates

Your test environment is always updated before your production environment.

During this period, the version of the Financial Reporting server on your test environment may be different than the version on your production environment. When this happens, the existing Financial Reporting Studio client currently installed on your computer may not work with your test environment due to the version mismatch between its server and client. Thus, during this period, you must uninstall and reinstall the Financial Reporting Studio client from the test or production environment accordingly, depending on which environment you work on, to ensure the client version matches the server version.

Using Financial Reporting Studio After the Production Update

After the production environment is updated, the Financial Reporting Studio versions for the test and production environments will be the same.

If you already installed Financial Reporting Studio from the test environment, you won't have to make any changes. Otherwise, you should immediately uninstall, download, and reinstall Financial Reporting Studio from the financial reporting workspace in the production environment.

Comparing the Client and Server Versions

To compare the Financial Reporting Studio client version with the Financial Reporting server version, perform the following steps:

  1. Launch Financial Reporting Studio.

  2. From the Help menu, select About Reporting Studio.

  3. Compare the Oracle Hyperion Financial Reporting version with the Report Server Version to confirm that they match.

The following figure shows an example of the Financial Reporting Studio window with matching client and server versions. The Oracle Hyperion Financial Reporting version is and the Report Server Version is

This figure shows the page that displays when you
select About Reporting Studio from the Financial Reporting Studio
Help menu.

You can also check the server version from the Help menu of the financial reporting workspace.

  1. From the Financial Reporting Center, select the Open Workspace for Financial Reports task.

  2. From the Help menu, select About Oracle Enterprise Performance Management System Workspace.

  3. Click Show Details.

The following figure shows an example of the Enterprise Performance Management System Workspace window with the report server version.

This figure shows the page that displays when you
select About Oracle Enterprise Performance Management System Workspace
from the Help menu in the financial reporting workspace.

Installing Financial Reporting Studio

Perform the following prerequisite steps:

  1. Uninstall the previous version, if any, using the Windows Control Panel.

  2. Delete the existing directory structure. For example, C:\Oracle\Middleware\EPMSystem11R1\products\FinancialReportingStudio.

  3. Restart your computer.

Download the version of the Financial Reporting Studio from that environment's workspace:

  1. Navigate to the Financial Reporting Center and select the Open the Financial Reporting Workspace task.

  2. From the menu, select Tools > Install > Financial Reporting Studio and save the file.

  3. Right-click the executable file and select Run as administrator.

    Caution: Don't close the command window that appears near completion. It will automatically close itself.

    The following figure shows an example of the command window that appears while the executable file is running.

    This figure shows the command window, which automatically
  4. Click Finish on the install window after the command window closes.

Lastly, when designing reports, you can't design a Financial Reporting Studio report using a client version that's higher than the report server version, and then export or import the report to a lower client version level. The report may not work.

How to Tune Performance for Analytics and Reports

When you create analyses and reports, don't use blind queries and include sufficient filters when creating analytics or reports with hierarchies.

Blind Queries

Avoid blind queries because they're run without filters and fetch large data sets. Performance can be an issue with these queries and can easily overload the application. All queries on large transactional tables must be time bound. For example, include a time dimension filter and additional filters to restrict by key dimensions, such as worker. Apply filters to columns that have database indexes in the transactional tables. This ensures a good execution plan is generated for the query from the BI Server.

Hierarchies and Trees

Queries on trees and hierarchical dimensions such as manager can have an impact on performance. The BI Server uses a column-flattening approach to quickly fetch data for a specific node in the hierarchy. But, because there is no pre-aggregation for the different levels of the hierarchy, it's important to carefully craft any query involving hierarchies to ensure that enough filters are applied to keep the result set small.

Review SQL Statements Used in Analyses

You can review logical and physical SQL statements using either of the following procedures.

Logical and Physical SQL

Logical SQL is non-source specific SQL that's issued to the Oracle BI Server for an analysis. Logical queries use column names from the subject areas in the Presentation Layer in the repository (RPD) metadata. Based on the logical request, the BI Server issues optimized source-specific SQL to the actual data sources in the Physical Layer of the metadata. If you have administrative privileges, you can review both logical and physical SQL for analyses.

Edit Mode

  1. Open the analysis in Edit mode and click the Advanced tab.

  2. In the SQL Issued section, review the logical SQL statement.

Administration Page

  1. On the Administration page, in the Session Management section, click the Manage Sessions link.

    Note: You must be a Business Intelligence Administrator to access the Administration and Manage Sessions page.
  2. On the Manage Sessions page, in the Action column, click the View Log link to review the SQL statement.

Archive and Move Analytics

You can archive your analytic objects and move them to a new location. You can bundle the whole catalog, specific folders, or multi-component objects as a .catalog file and upload the file to unarchive its data in another location.

Note: It's important to note that folders that contain seeded content should not be changed. Moving or adding a child folder to a seeded folder results in analytics not being visible in dashboards or infolets.

Create an Archive

  1. Locate the object in the catalog.

  2. Select More and then select Archive.

  3. In the Archive dialog box, select one or more of the following options:

    • Keep Permissions: Maintain the object or folder's existing permissions. If you don't select this, the archiving process doesn't include any permissions. Once unarchiving, the parent folder's permissions are assigned to all of the objects and folders.

    • Keep Time stamps: Maintain the Creation Time, Last Modified, and Last Accessed times assigned to the object or folder. Upon unarchiving, the Last Modified time is updated to indicate the time when the object or folder is unarchived. If you select this option, the Old option in the Paste Overview area of the Preferences dialog box is available when unarchiving. Use the Old option to overwrite existing catalog items older than the items in the archive.

      If you don't select this option, then the archiving process doesn't include time information and the Old option in the Paste Overview area of the Preferences dialog box isn't available.

  4. Click OK to download the archive file.

Move an Archived Object to a New Location

  1. Select the folder in the catalog where you want to upload the archived file.

  2. In the Tasks pane click Unarchive.

  3. In the Unarchive dialog box, browse for and select the archive file.

  4. Use the Replace option to specify whether to replace an existing folder or object with the same name.

    • All: Replace any existing folders or objects with the same names as folders or objects included in the archive file that you're uploading.

    • Old: Replace folders or objects except those folders or objects that exist, unless they're older than the source.

    • None: Add any new folders or objects, but preserve any existing folders or objects.

    • Force: Add and replace all folders or objects.

  5. Use the Access Control Lists option to specify how the folders or objects are assigned permissions using Access Control Lists Access when unarchived.

    • Inherit: Inherits the folder or object's permissions from its new parent folder.

    • Preserve: Preserves the folder or object's permissions as it was in the original, mapping accounts as necessary.

    • Create: Preserves the folder or object's permissions as it was in the original, creating and mapping accounts as necessary.

  6. Click OK.


You can export your financial reports from a source environment and import them to a target environment using implementation projects.

Only the financial reports in the /shared/Custom/Financials folder are exported, so make sure to copy all the financial reports, or the folders containing them, to this folder. In the Setup and Maintenance work area, create an implementation project that includes only the Create Financial Statements task. Then use the Manage Configuration Packages task to export and import the reports.

Note: For the Financial Reporting report definition migration service, from a source to a target environment, references to version IDs of dimension members hierarchies are synchronized to their version IDs in the target environment.