Introduction
Bursting Parameters in Oracle Fusion HCM play a critical role when generating and distributing reports dynamically to multiple recipients based on specific data conditions. In real-world Oracle Fusion HCM implementations, especially in reporting scenarios using BI Publisher, bursting is one of the most powerful features consultants rely on to automate report delivery.
Whether you are working on payroll reports, employee data extracts, or compliance reports, understanding bursting parameters ensures that reports are not just generated—but intelligently distributed to the right stakeholders without manual intervention.
In this blog, we will break down bursting parameters in a practical, implementation-focused way, based on real consultant experience.
What are Bursting Parameters in Oracle Fusion HCM?
Bursting parameters are configurations used in BI Publisher reports within Oracle Fusion HCM to:
- Split a single report output into multiple smaller documents
- Deliver each document to different recipients
- Apply delivery formats like PDF, Excel, or CSV
- Automate distribution via email, FTP, or WebDAV
In simple terms:
Instead of generating one large report, bursting allows you to generate and send customized reports per employee, department, or business unit automatically.
Key Features of Bursting Parameters
1. Dynamic Report Splitting
- Split reports based on:
- Employee ID
- Department
- Legal Employer
- Business Unit
2. Multiple Delivery Channels
- FTP / SFTP
- WebDAV
- Printer
3. Format Customization
- Excel (XLSX)
- CSV
- XML
4. Data-Driven Logic
- Bursting logic is driven using SQL queries
5. Scheduling Capability
- Works with scheduled ESS jobs in Fusion
Real-World Implementation Use Cases
Use Case 1: Payslip Distribution
In a payroll implementation:
- A single payroll report is generated
- Bursting splits the report by Employee Number
- Each employee receives their own payslip via email
Result: No manual intervention required
Use Case 2: Department-wise HR Reports
HR wants separate reports for each department:
- Bursting splits data by Department ID
- Sends reports to respective department heads
Use Case 3: Compliance Reports
For statutory reporting:
- Reports split by Legal Employer
- Delivered to compliance teams in different regions
Architecture / Technical Flow
Here’s how bursting works in Oracle Fusion HCM:
- BI Publisher Report is executed
- Data Template generates XML output
- Bursting Query processes XML data
- Report is split based on key column
- Delivery configuration is applied
- Output is sent to recipients
Prerequisites
Before implementing bursting parameters, ensure:
- BI Publisher Report is created
- Data Model includes required fields (like Employee ID, Email)
- Bursting Query is defined
- Email server or FTP setup is configured
- Required roles are assigned:
- BI Administrator
- HCM Extracts access (if applicable)
Step-by-Step Build Process
Step 1 – Create or Identify BI Publisher Report
Navigation:
Navigator → Tools → Reports and Analytics → Browse Catalog
- Create or open an existing report
- Ensure the report generates correct XML output
Step 2 – Design Data Model for Bursting
Include required fields:
- KEY (Split column, e.g., Employee ID)
- TEMPLATE (Template name)
- OUTPUT_FORMAT (PDF, Excel)
- DEL_CHANNEL (EMAIL, FTP)
- PARAMETER1 (Email address)
Step 3 – Define Bursting Query
Example Bursting Query:
employee_number AS “KEY”,
‘Payslip_Template’ AS TEMPLATE,
‘en-US’ AS LOCALE,
‘PDF’ AS OUTPUT_FORMAT,
‘EMAIL’ AS DEL_CHANNEL,
email_address AS PARAMETER1
FROM
per_all_people_f
Explanation:
| Column | Purpose |
|---|---|
| KEY | Splits report |
| TEMPLATE | Template to use |
| OUTPUT_FORMAT | Output type |
| DEL_CHANNEL | Delivery method |
| PARAMETER1 | Email ID |
Step 4 – Configure Bursting in BI Publisher
- Open Data Model
- Go to Bursting section
- Add bursting query
- Map columns accordingly
Step 5 – Attach Template
- Upload RTF or Excel template
- Ensure template name matches bursting query
Step 6 – Save Configuration
- Save Data Model
- Save Report
Testing the Bursting Setup
Test Scenario
Run report for 5 employees:
Expected Behavior:
- 5 separate PDF files generated
- Each sent to respective email ID
Validation Checks
- Check email delivery
- Verify correct employee data in each file
- Confirm correct template formatting
Common Implementation Challenges
1. Incorrect KEY Mapping
- Issue: Reports not splitting properly
- Fix: Ensure KEY column matches data structure
2. Email Not Triggered
- Issue: No emails sent
- Fix: Verify email server setup in Fusion
3. Template Mismatch
- Issue: Report fails during execution
- Fix: Ensure template name matches exactly
4. Data Issues
- Missing email IDs in data source
Best Practices
1. Always Validate XML Output
Before enabling bursting, check raw XML
2. Use Meaningful KEY Columns
Avoid using non-unique fields
3. Test with Small Data Sets
Start with 2–3 records before scaling
4. Handle Null Values
Ensure email or delivery parameters are not null
5. Use Logging
Enable logging for debugging
Summary
Bursting parameters in Oracle Fusion HCM are essential for automating report distribution at scale. From payroll payslips to compliance reports, bursting ensures:
- Accurate report splitting
- Automated delivery
- Reduced manual effort
In real-world projects, mastering bursting can significantly improve reporting efficiency and reduce operational overhead.
For deeper technical reference, always review official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. What is the KEY column in bursting?
The KEY column determines how the report is split. For example, Employee ID splits report per employee.
2. Can bursting be used with scheduled jobs?
Yes, bursting works seamlessly with ESS scheduled jobs for automated report delivery.
3. What happens if email ID is missing?
The report for that record will fail or not be delivered. Always validate data before execution.