Bursting in Oracle HCM Guide

Bursting in Oracle Fusion HCM: Complete Consultant Guide

Introduction

Bursting in Oracle Fusion HCM is one of the most powerful features used in reporting and document distribution, especially when working with BI Publisher (BIP). In real-world implementations, bursting allows you to automatically split a single report into multiple outputs and deliver them to different recipients based on business rules.

If you have ever worked on payslip distribution, employee letters, or department-wise reports, bursting becomes a critical component of your solution.

This blog explains bursting in Oracle Fusion HCM from a practical consultant perspective, covering setup, use cases, configuration steps, and troubleshooting.

What is Bursting in Oracle Fusion HCM?

Bursting is a BI Publisher feature that allows you to:

• Split a report output into multiple documents
• Apply different templates or formats
• Deliver output to multiple recipients (email, FTP, WebDAV, etc.)

In simple terms:

One report → Multiple outputs → Delivered automatically

Key Features of Bursting

Here are the core capabilities you should understand:

1. Dynamic Output Generation

• Split report by employee, department, or business unit
• Each output can be unique

2. Multiple Delivery Channels

• Email
• FTP / SFTP
• Printer
• WebDAV

3. Template Selection

• Assign different templates dynamically
• Example: English vs French payslip

4. Parameter-Based Distribution

• Control output using SQL logic
• Route reports based on business rules

5. Integration with HCM Processes

• Used in:
  • Payslip generation
  • Compensation letters
  • Offer letters
  • Payroll reports

Real-World Business Use Cases

Use Case 1: Payslip Distribution

A global organization wants:

• Each employee to receive their payslip via email
• Output format: PDF
• Language based on employee preference

Bursting Logic:

• Split by PERSON_ID
• Email fetched from PER_EMAIL_ADDRESSES
• Template selected dynamically

Use Case 2: Department-Wise Reports

HR wants:

• One report per department
• Delivered to respective department heads

Bursting Logic:

• Split by DEPARTMENT_ID
• Email mapped via lookup table

Use Case 3: Offer Letter Automation

Recruitment team needs:

• Offer letters generated per candidate
• Automatically emailed

Bursting Logic:

• Split by CANDIDATE_ID
• Attach PDF and send via email

Configuration Overview

Before configuring bursting, ensure:

Required Components

Step-by-Step Configuration in Oracle Fusion HCM

Step 1 – Navigate to BI Publisher

Navigation:
Navigator → Tools → Reports and Analytics → Browse Catalog

Step 2 – Create or Open Report

• Create a Data Model
• Upload Data Template (if needed)
• Add RTF Template

Step 3 – Define Bursting Query

This is the most critical step.

Example Bursting Query:

Explanation:

Step 4 – Configure Bursting in Report

• Open report properties
• Go to Bursting Definition
• Enable bursting
• Upload bursting query

Step 5 – Map Key Field

Ensure:

• KEY column in bursting query matches report grouping field

Example:

• If report grouped by PERSON_ID → KEY = PERSON_ID

Step 6 – Save Configuration

• Save report
• Validate bursting query

Testing the Setup

Test Scenario: Payslip Distribution

Input:

• Run payroll report for 10 employees

Expected Output:

• 10 separate PDF files
• Each sent to respective employee email

Validation Checklist

• Each employee receives correct document
• Email addresses are correct
• Template applied properly
• No missing records

Architecture / Technical Flow

Here is how bursting works internally:

1. Report executes → Data generated
2. Bursting query runs → Determines split logic
3. Output divided based on KEY
4. Templates applied dynamically
5. Delivery engine sends output

Common Implementation Challenges

1. Incorrect KEY Mapping

• Report does not split correctly

Fix:
Ensure grouping field matches bursting KEY

2. Email Not Delivered

• Incorrect email or SMTP configuration

Fix:
Validate email column and BI Publisher delivery settings

3. Template Not Applied

• Wrong template name in query

Fix:
Check exact template name in catalog

4. Performance Issues

• Large reports take time

Fix:

• Optimize SQL
• Use filters

5. Security Issues

• Users unable to access reports

Fix:

• Assign roles properly
• Check catalog permissions

Best Practices from Real Projects

1. Always Test with Small Data

Start with:

• 2–3 records
• Validate logic before scaling

2. Use Meaningful KEY Fields

Avoid generic values:

• Use PERSON_ID or ASSIGNMENT_ID

3. Maintain Email Data Quality

Ensure:

• Email addresses are valid
• Primary flag is correct

4. Version Control Templates

• Maintain versions for:
  • Payslips
  • Letters

5. Log and Audit Deliveries

• Maintain logs for:
  • Sent emails
  • Failures

Frequently Asked Interview Questions

1. What is bursting in Oracle Fusion HCM?

Bursting is a BI Publisher feature used to split reports and deliver outputs to multiple recipients automatically.

2. What is the purpose of KEY in bursting?

KEY identifies how the report should be split into multiple outputs.

3. What delivery channels are supported?

Email, FTP, printer, WebDAV.

4. What is PARAMETER1 in bursting?

It is used to pass delivery-specific values like email address.

5. Can we use multiple templates in bursting?

Yes, templates can be dynamically selected using SQL.

6. What happens if KEY is incorrect?

Report will not split properly.

7. Where is bursting configured?

In BI Publisher report properties.

8. Can bursting be used for payslips?

Yes, it is widely used for payslip distribution.

9. What is LOCALE used for?

To define language/region of output.

10. How to debug bursting issues?

• Check SQL
• Validate email
• Review logs

Real Implementation Scenario

In one implementation for a global company:

• Payroll runs generated 25,000 payslips
• Bursting was used to:
  • Split by employee
  • Apply country-specific templates
  • Deliver via email

Challenges faced:

• Performance issues
• Incorrect email mapping

Solution:

• Optimized SQL
• Created staging table for email data

Expert Tips

• Always validate bursting query independently in SQL Developer
• Use aliases properly in SQL
• Avoid hardcoding values
• Keep templates simple for performance
• Use logging for troubleshooting

Summary

Bursting in Oracle Fusion HCM is a must-know feature for any consultant working with BI Publisher. It enables:

• Automated report distribution
• Personalized outputs
• Scalable document delivery

When implemented correctly, bursting can significantly reduce manual effort and improve efficiency in HR operations.

FAQs

1. Can bursting send reports to multiple email addresses?

Yes, you can include multiple emails separated by commas in PARAMETER1.

2. Is bursting available in all reports?

Bursting is available only in BI Publisher reports, not OTBI.

3. Can we schedule bursting reports?

Yes, bursting works with scheduled BI Publisher jobs.

Additional Reference

For deeper technical documentation, refer to:

https://docs.oracle.com/en/cloud/saas/index.html