Migrate Oracle Hyperion Reports Between Environments
Financial Reporting Studio helps teams move highly formatted Oracle Hyperion reports between environments while preserving the report definitions that finance users depend on. The steps below explain how to reach the BI Catalog, export the required files, import them into the target environment, and confirm that the migration completed correctly.
Oracle Hyperion Financial Reporting generates highly formatted, book-quality financial and management reports like a GAAP-complaint Balance Sheet and Income Statement for your company’s Annual Report. While Oracle Financial Reporting Studio is used to create and edit reports, changes to the report folder structure like deleting reports, copying reports within an instance, or migrating reports between instances and environments, can be made in the Workspace for Financial Reports.
Access the Financial Reporting Studio Report Catalog
- 1. Click on the Financial Reporting Center icon
- 2. Click on the task list icon on the upper right corner > Open Workspace for Financial Reporting
- 3. On the new page, click on the Application drop-down > BI Catalog. Make sure pop-ups are enabled for your browser.
Export Reports from the Source Environment
- 4. On the BI Catalog page of the source environment, click on File > Export
- 5. Click the folder of the report to export > Select the report > click ok. This will download the report to your default download location in a .des format.
- 6. Open the folder where you want to store the imported report
- 7. Click on File > Import > Financial Reports
- 8. In the new dialog box, navigate to the folder where the .des file you downloaded in the previous step resides > Select the .des file and click open
- 9. Confirm the database connection detail to match the target database > Click ok.
Next, ensure that the hierarchies used on the rows and columns of the report match in the source and target environments before importing the reports to the target. In case the hierarchies don’t match, the target report will not run as is. This is because the members on the target report are still referencing the IDs from the hierarchy in the source environment and will need to be selected again, once the report is imported.
Import and Validate Reports in the Target Environment
Best Practices for a Reliable Report Migration
Before starting, confirm that the source and target environments use compatible application structures, security assignments, data sources, and folder conventions. Create a dated backup of the report package and record the original catalog path. This preparation gives administrators a clear rollback point and reduces confusion if similarly named folders already exist in the target.
After the import, open several representative reports in Financial Reporting Studio. Test prompts, member selections, calculations, formatting, charts, books, and scheduled batches. A report definition can import successfully but still require attention when connections, aliases, fonts, or application metadata differ between environments. Validate both the design view and rendered output before releasing the reports to business users.
For production changes, use a controlled promotion process and document who completed each validation step. Keep the exported package unchanged until user acceptance is complete. Compare a small sample of output files with the source, including page breaks, headers, totals, and suppression behavior, and ask a report owner to confirm the results. This practical checklist makes the migration easier to audit and helps teams resolve exceptions without altering the original instructions on this page.
Related Oracle Hyperion Resources
For more Financial Reporting Studio planning guidance, explore Financial Reporting Studio services, Oracle Hyperion solutions, Oracle EPM consulting, business intelligence services, Oracle Hyperion application support. Also review the official Oracle report migration documentation to confirm current options and limitations.
