Burst Fusion HCM BI to UCM

Introduction

Bursting a Fusion HCM BI report to UCM is a common requirement in enterprise implementations where organizations need to generate employee-specific reports and automatically distribute or store them. In projects involving Oracle Fusion HCM, report bursting plays a critical role in automating HR communications such as payslips, offer letters, and compliance documents.

In real implementations, clients rarely want a single consolidated report—they need personalized outputs for each employee and seamless delivery into storage like Oracle WebCenter Content (UCM). This is where BI Publisher bursting comes into the picture.

This blog explains how to burst a Fusion HCM BI report to UCM, covering architecture, setup, step-by-step implementation, and real-world troubleshooting.

What is Burst Fusion HCM BI Report to UCM?

Bursting in BI Publisher allows you to:

• Split a single report into multiple outputs based on a key (e.g., Employee ID)
• Deliver each output to a specific destination
• Automate distribution (email, FTP, UCM, etc.)

When integrated with UCM:

• Reports are stored centrally
• Documents are version-controlled
• Secure access is maintained

In HCM projects, bursting to UCM is typically used for:

• Payslip archival
• Employee document storage
• Compliance document distribution

Real-World Integration Use Cases

1. Payslip Generation and Storage

A global organization generates monthly payslips for 20,000 employees:

• BI Report generates payslip data
• Bursting splits per employee
• Output stored in UCM under employee-specific folders

2. Offer Letter Automation

Recruitment team generates offer letters:

• Each candidate gets a separate PDF
• Stored in UCM for audit and retrieval

3. Compliance Reports for Auditors

HR generates statutory reports:

• Split by department/location
• Stored securely in UCM
• Access controlled by roles

Architecture / Technical Flow

The bursting flow works as follows:

1. Data Template → Fetches data
2. BI Publisher Report → Generates output
3. Bursting Control File → Defines split logic
4. Delivery XML → Specifies destination (UCM)
5. Output stored in UCM repository

Typical flow:

In advanced cases, integration with Oracle Integration Cloud is used for orchestration, but basic bursting works standalone.

Prerequisites

Before implementing bursting to UCM, ensure:

1. BI Publisher Access

• BI Administrator role
• Access to Data Models and Reports

2. UCM Configuration

• UCM server enabled
• Proper security roles
• Folder structure defined

3. Required Permissions

• User must have access to:
  • BI Catalog
  • UCM Content Server

4. Data Model Prepared

• Must include:
  • Employee identifier
  • Required report fields
  • Bursting key column

Step-by-Step Build Process

Step 1 – Create Data Model

Navigation:

Create Data Model with:

• SQL Query:

Important:

• Include unique key (person_id)
• Include delivery fields (email, etc.)

Step 2 – Create BI Report

• Upload RTF template
• Map fields properly
• Generate sample output

Step 3 – Create Bursting Query

Bursting query defines:

• Split logic
• Delivery method
• Output format

Example bursting query:

Step 4 – Configure Delivery XML for UCM

This is the most critical part.

Example Delivery XML:

Key Parameters Explained

Step 5 – Attach Bursting Definition

In Data Model:

• Go to Bursting section
• Upload bursting query
• Map fields

Step 6 – Run the Report

Navigation:

Select:

• Output format
• Enable bursting

Testing the Technical Component

Test Scenario

Run report for 3 employees:

Validation Steps

1. Login to UCM
2. Search document using:
   • Document title
   • Employee ID
3. Verify:
   • Correct content
   • Correct security group
   • Proper naming

Common Errors and Troubleshooting

1. UCM Delivery Failure

Error: Delivery failed
Cause: Incorrect UCM parameters
Fix:

• Verify PARAMETER1 (server)
• Check security group

2. No Bursting Output Generated

Cause:

• KEY mismatch
• Incorrect query mapping

Fix:

• Ensure KEY matches report data

3. Permission Issues in UCM

Cause:

• User lacks access

Fix:

• Assign correct roles in UCM

4. Incorrect File Names

Cause:

• OUTPUT_NAME misconfigured

Fix:

• Use dynamic naming logic:

Best Practices

1. Use Meaningful Naming

• Avoid generic file names
• Use employee number or document type

2. Secure UCM Storage

• Use proper security groups
• Avoid public access

3. Optimize Bursting Query

• Keep query lightweight
• Avoid unnecessary joins

4. Validate with Small Dataset

• Test with 5–10 records before full run

5. Monitor Performance

• Large bursting jobs can impact system performance

6. Use Logging

• Enable BI logs for debugging

Summary

Bursting Fusion HCM BI reports to UCM is a powerful capability that enables organizations to automate document generation and storage. In real implementations, this approach is widely used for payslips, offer letters, and compliance reports.

From a consultant’s perspective, the key success factors are:

• Correct bursting query design
• Accurate UCM parameter configuration
• Proper testing and validation

Once configured correctly, this setup significantly reduces manual effort and improves document management efficiency.

For more details, refer to Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. Can we burst reports to multiple destinations simultaneously?

Yes, BI Publisher supports multiple delivery channels like Email, FTP, and UCM in the same bursting definition.

2. Is bursting supported for large datasets?

Yes, but performance tuning is required. Use pagination and optimize queries.

3. Can we control UCM folder structure dynamically?

Yes, using PARAMETER fields in bursting XML, you can dynamically assign folders/accounts.