Fusion HCM BI Report Migration Guide

Introduction

Fusion HCM BI Report Migration is a critical technical activity in any Oracle Cloud implementation or support project. Whether you are moving reports from a development pod to test, or from test to production, ensuring accurate and consistent migration of BI Publisher (BIP) reports is essential for business continuity. In Oracle Fusion Cloud HCM, reporting plays a central role in payroll processing, HR analytics, compliance, and audit.

From a consultant’s perspective, BI report migration is not just about exporting and importing files—it involves understanding dependencies, data templates, bursting configurations, security roles, and catalog structure.

In real projects, improper migration leads to broken reports, missing data templates, or security issues—especially during go-live.

What is Fusion HCM BI Report Migration?

Fusion HCM BI Report Migration refers to the process of moving BI Publisher artifacts such as:

• Data Templates (.xml)
• Report Layouts (.rtf / .xpt / .xls)
• Sub-templates
• Bursting Definitions
• Data Models
• Report Definitions

from one environment to another within Oracle Fusion.

Typical environments:

• DEV (Development)
• TEST / UAT
• PROD (Production)

Migration is done using:

• BI Catalog (manual export/import)
• Functional Setup Manager (FSM) – limited
• Automated tools via Oracle Integration Cloud (advanced use case)

Real-World Integration Use Cases

1. Payroll Report Migration During Go-Live

A client uses custom payroll reports:

• Payslip layout
• Payroll register
• Bank transfer reports

These are developed in DEV and must be migrated to PROD before payroll run.

Challenge: Ensuring data model compatibility and correct security roles.

2. Compliance Reports Across Regions

A global organization has:

• Country-specific statutory reports
• Localization-specific templates

These reports are migrated from a global template environment to regional pods.

3. Automated Report Deployment via CI/CD

Advanced clients use:

• OIC pipelines
• Scripted deployments

to automate BI report migration across environments.

Architecture / Technical Flow

Fusion HCM BI reporting architecture includes:

1. BI Catalog
   • Stores reports and folders
2. Data Model
   • SQL queries / HCM extracts
3. Layout Template
   • RTF / Excel layouts
4. Security Layer
   • Roles and data access

Migration Flow:

DEV → Export (Catalog Object) → Import → TEST → Validate → PROD

Prerequisites

Before migrating BI reports, ensure:

1. Access Requirements

• BI Administrator role
• BI Author role
• Application Implementation Consultant role

2. Folder Structure Consistency

Example:

Ensure same structure exists in target environment.

3. Data Model Dependencies

Check:

• SQL queries
• Table availability
• Value sets
• Flexfields

4. Security Setup

Verify:

• Duty roles
• Data roles
• Report access permissions

Step-by-Step Build Process (Migration)

Step 1 – Login to Source Environment (DEV)

Navigate:

Navigator → Tools → Reports and Analytics

Click:

Browse Catalog

Step 2 – Locate the Report

Navigate to:

Identify:

• Data Model
• Report Layout
• Sub-templates

Step 3 – Export the Report

Click:

More → Archive

This downloads a .catalog file.

💡 Consultant Tip:
Always export at folder level instead of individual reports when multiple dependencies exist.

Step 4 – Download Supporting Files

Sometimes needed separately:

• RTF templates
• Sub-templates
• Images used in reports

Step 5 – Login to Target Environment (TEST/PROD)

Navigate:

Navigator → Tools → Reports and Analytics → Browse Catalog

Step 6 – Import the Catalog File

Click:

Upload → Archive

Select:

• .catalog file
• Target folder

Step 7 – Resolve Dependencies

After import:

• Open Data Model
• Validate SQL query
• Re-link templates if required

Step 8 – Set Permissions

Click:

More → Permissions

Assign roles:

• HR Specialist
• Payroll Manager
• Custom roles

Step 9 – Save and Validate

Ensure:

• Report opens successfully
• Layout renders properly

Testing the Technical Component

Example Test Case

Report: Employee Salary Report

Input Parameters:

• Business Unit = US Operations
• Payroll Period = Jan 2026

Expected Results:

• Correct employee data
• Accurate salary figures
• Proper formatting

Validation Checks:

Common Errors and Troubleshooting

1. Data Model Not Found

Cause:
Missing or incorrect data model reference

Fix:
Re-upload or relink data model

2. Layout Not Rendering

Cause:
Missing RTF template

Fix:
Upload template again

3. SQL Errors

Cause:
Environment-specific data differences

Fix:
Validate queries against target environment

4. Security Issues

Cause:
Roles not assigned

Fix:
Assign correct roles in catalog permissions

5. Bursting Not Working

Cause:
Incorrect delivery configuration

Fix:
Reconfigure bursting setup

Best Practices

1. Use Consistent Naming Convention

Example:

2. Maintain Folder Standardization

Avoid random folder structures.

3. Always Migrate in Bundle

• Data model
• Report
• Templates

4. Validate in TEST Before PROD

Never migrate directly to production.

5. Document Dependencies

Maintain:

• SQL queries
• Parameters
• Security roles

6. Version Control

Keep versions:

• V1, V2, V3

7. Backup Before Migration

Export existing PROD reports before overwrite.

Real Consultant Insight

In one implementation, a payroll team migrated reports directly to PROD without validating bursting configuration. Result:

• Payslips were sent to wrong employees
• Compliance issue raised

Fix required:

• Immediate rollback
• Manual corrections

👉 Lesson: Always validate in TEST.

FAQs

1. Can we automate BI report migration in Fusion?

Yes. Advanced setups use Oracle Integration Cloud or scripts to automate migration, especially in large enterprises.

2. What is the safest way to migrate reports?

Using catalog archive export/import with full dependency validation is the safest approach.

3. Do BI reports require reconfiguration after migration?

Sometimes yes, especially:

• Security roles
• Bursting setup
• Environment-specific parameters

Summary

Fusion HCM BI Report Migration is a crucial technical activity that ensures reporting continuity across environments in Oracle Fusion Cloud HCM. While the process may seem straightforward, real-world implementations demand careful attention to:

• Dependencies
• Security
• Data models
• Testing

A structured approach—export, validate, import, test—ensures smooth migration without impacting business operations.

For deeper technical reference, always consult the official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html