Introduction
In real-time Oracle implementations, one of the most common client requirements is to automatically send reports to business users—without manual intervention. This is where bursting Fusion HCM BI reports to email becomes critical. Using Oracle Fusion HCM along with Oracle BI Publisher, consultants can design scalable reporting solutions that distribute personalized reports to hundreds or thousands of employees.
From payroll registers sent to managers to employee data extracts shared with HR teams, bursting is a must-have feature in enterprise deployments.
This article walks you through the complete implementation of bursting BI reports to email in Fusion HCM, using a practical consultant approach.
What is Bursting in Fusion HCM BI Reports?
Bursting is a feature in BI Publisher that allows a single report to be:
- Split into multiple outputs
- Delivered to different recipients
- Customized per recipient (PDF/Excel/etc.)
Instead of generating one large report, bursting distributes data intelligently based on business logic.
Example:
A Payroll report can be:
- Split by Department
- Sent to each Department Manager
- Delivered as a PDF attachment via email
Key Features of BI Publisher Bursting
1. Dynamic Email Distribution
Emails are not hardcoded—recipients are picked from data (like employee or manager email).
2. Output Customization
Each user can receive:
- Excel
- CSV
3. Scheduling Support
Reports can be:
- Scheduled daily/weekly
- Triggered post payroll run
4. Data Security
Each recipient sees only their relevant data.
5. Template Flexibility
Different templates can be used for different users.
Real-World Implementation Use Cases
Use Case 1: Payroll Register Distribution
A global company wants:
- Payroll reports per department
- Sent only to respective managers
Bursting logic: Department → Manager Email
Use Case 2: Employee Payslip Emails
Each employee receives:
- Their individual payslip
- As a password-protected PDF
Bursting logic: Employee ID → Employee Email
Use Case 3: HR Compliance Reports
HR teams receive:
- Location-wise employee data
- Weekly scheduled emails
Bursting logic: Location → HR Email Group
Architecture / Technical Flow
Here’s how bursting works internally:
- BI Report fetches data
- A Bursting Query determines:
- How data is split
- Who receives it
- BI Publisher:
- Splits report
- Applies template
- Sends email
Components Involved
| Component | Description |
|---|---|
| Data Template | Main report query |
| Layout Template | RTF/XSL format |
| Bursting Query | Controls distribution |
| Delivery Channel | Email, FTP, etc. |
Prerequisites
Before configuring bursting, ensure:
- BI Report is already created
- Output format (PDF/Excel) is finalized
- Email server is configured in environment
- Required roles assigned:
- BI Author Role
- BI Administrator Role
Step-by-Step Build Process
Step 1 – Create BI Report
Navigation:
Navigator → Tools → Reports and Analytics → Browse Catalog
- Create a Data Model
- Add SQL Query
- Create Layout (RTF Template)
Example Query:
employee_id,
employee_name,
department_name,
email_address,
salary
FROM per_all_people_f
Step 2 – Create Bursting Query
The bursting query defines how report splits and sends.
Example Bursting Query:
department_name AS “KEY”,
‘EMAIL’ AS “DEL_CHANNEL”,
email_address AS “PARAMETER1”,
‘Payroll Report’ AS “PARAMETER2”,
‘Please find attached report’ AS “PARAMETER3”,
‘PDF’ AS “OUTPUT_FORMAT”
FROM your_table
Step 3 – Configure Bursting in Data Model
- Open Data Model
- Go to Bursting Definition
- Add:
| Field | Value |
|---|---|
| Split By | department_name |
| Deliver By | department_name |
- Attach bursting query
Step 4 – Configure Email Delivery
In bursting settings:
| Parameter | Description |
|---|---|
| PARAMETER1 | Email Address |
| PARAMETER2 | Subject |
| PARAMETER3 | Email Body |
Step 5 – Link Template
- Assign layout template
- Define output format (PDF/Excel)
Step 6 – Save and Validate
- Save Data Model
- Validate bursting setup
Testing the Technical Component
Step 1 – Run Report Manually
- Navigate to report
- Click Run
Step 2 – Provide Parameters
Example:
- Department = Finance
Step 3 – Validate Output
Check:
- Email received
- Correct attachment
- Data accuracy
Expected Results
| Check | Expected Outcome |
|---|---|
| Email Delivery | Successful |
| Report Split | Correct per department |
| Format | PDF/Excel |
| Data Accuracy | Valid |
Common Errors and Troubleshooting
1. Email Not Received
Cause:
- Email server issue
Fix:
- Check SMTP configuration
2. All Data Sent to One User
Cause:
- Incorrect bursting key
Fix:
- Verify Split By column
3. Report Not Splitting
Cause:
- Missing KEY column
Fix:
- Ensure KEY matches split logic
4. Attachment Missing
Cause:
- Output format mismatch
Fix:
- Verify OUTPUT_FORMAT field
Best Practices from Real Projects
1. Always Test with Small Data
Avoid running full dataset initially.
2. Use Meaningful Email Subjects
Example:
- “Payroll Report – Finance Department”
3. Secure Sensitive Data
- Use password-protected PDFs for payroll
4. Avoid Hardcoding Emails
Always fetch from database.
5. Monitor Scheduled Jobs
Check:
Navigator → Tools → Scheduled Processes
Summary
Bursting Fusion HCM BI reports to email is one of the most powerful capabilities in reporting automation. Using Oracle BI Publisher, consultants can design solutions that:
- Reduce manual effort
- Ensure secure data delivery
- Scale across large organizations
In real implementations, bursting is not just a feature—it’s a business-critical automation layer that supports HR, Payroll, and Compliance reporting.
For deeper reference, consult official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. Can we send different formats to different users?
Yes. The bursting query can dynamically assign formats like PDF or Excel per user.
2. Can bursting be scheduled automatically?
Yes. Use Scheduled Processes to automate report execution and delivery.
3. Is bursting secure for payroll data?
Yes, if implemented properly with:
- Data filters
- Secure email handling
- Optional password protection