Bursting in Oracle Fusion HCM: Complete Consultant Guide
Bursting in Oracle Fusion HCM is a critical concept every functional and technical consultant must understand, especially when working with BI Publisher reports. In real implementations, clients rarely want a single bulk report—they want personalized, distributed outputs (like payslips, offer letters, or performance documents). That’s where bursting becomes essential.
This guide explains bursting from a practical implementation perspective, based on real project experience in Oracle Fusion Cloud (26A aligned).
What is Bursting in Oracle Fusion HCM?
Bursting is a BI Publisher feature that allows you to:
- Split a report into multiple outputs based on data
- Deliver each output to different recipients
- Use different delivery channels (Email, FTP, Printer, etc.)
- Customize templates and formats dynamically
Simple Example
Instead of generating one large payslip report:
- Each employee gets their own payslip
- Delivered via email automatically
- Based on their employee email ID
That entire automation is handled using bursting.
Why Bursting is Important in Oracle HCM
In almost every HCM implementation, bursting is used for:
- Payroll outputs
- HR letters (Offer, Experience, Promotion)
- Performance reports
- Compliance reports
Without bursting, HR teams would need manual intervention for distribution—which is not scalable.
Key Features of Bursting
1. Data-Based Splitting
Report output is split based on a key field:
- Person Number
- Assignment ID
- Department
2. Dynamic Delivery
Each output can go to:
- FTP
- WebDAV
- Printer
3. Template Selection
Different templates can be applied based on:
- Country
- Business Unit
- Employee Type
4. Output Format Control
Formats supported:
- Excel
- RTF
- XML
5. Conditional Logic
You can control:
- Who receives what
- Which template applies
- Delivery method
Real-World Implementation Use Cases
Use Case 1: Payslip Distribution
Client Requirement:
- Send monthly payslips automatically
- Each employee receives only their payslip
Solution:
- Burst by PERSON_NUMBER
- Email delivery using employee email
- PDF format
Use Case 2: Offer Letter Generation
Client Requirement:
- Generate offer letters for candidates
- Different templates per country
Solution:
- Burst by Candidate ID
- Template selection using country code
- Output stored in Content Server
Use Case 3: Performance Review Reports
Client Requirement:
- Send manager-specific performance summaries
Solution:
- Burst by Manager ID
- Email to manager
- Excel format for analysis
Architecture / Technical Flow
Bursting works as part of BI Publisher:
- Data Template / Data Model
- Fetches report data
- Bursting Query
- Defines how data is split and delivered
- Layout Template
- Defines output format
- Delivery Configuration
- Defines email/FTP/printer setup
- BI Publisher Engine
- Executes bursting logic
Prerequisites
Before implementing bursting:
- BI Publisher report must be created
- Data model should support bursting key (e.g., PERSON_NUMBER)
- Email server must be configured
- Required roles:
- BI Administrator
- BI Author
- Valid email IDs must exist in HCM
Step-by-Step Bursting Configuration in Oracle Fusion
Step 1 – Create BI Report
Navigation:
Navigator → Tools → Reports and Analytics → Browse Catalog
- Create Data Model
- Create Report Layout (RTF/Excel)
Step 2 – Add Bursting Query
In the Data Model:
Go to:
Data Model → Bursting
Create a bursting query like:
PERSON_NUMBER AS “KEY”,
‘EMAIL’ AS “DEL_CHANNEL”,
EMAIL_ADDRESS AS “PARAMETER1”,
‘PDF’ AS “OUTPUT_FORMAT”,
‘Payslip_Template’ AS “TEMPLATE”,
‘en-US’ AS “LOCALE”
FROM PER_ALL_PEOPLE_F
WHERE EMAIL_ADDRESS IS NOT NULL
Explanation of Fields
| Column | Purpose |
|---|---|
| KEY | Splitting identifier |
| DEL_CHANNEL | Delivery method |
| PARAMETER1 | Email / destination |
| OUTPUT_FORMAT | PDF/Excel |
| TEMPLATE | Layout name |
| LOCALE | Language |
Step 3 – Configure Delivery Channel
Go to:
Administration → Delivery Configuration
Set up:
- Email server (SMTP)
- FTP details (if required)
Step 4 – Enable Bursting in Report
- Open Report Properties
- Enable Bursting
- Link Data Model bursting query
Step 5 – Save and Deploy
- Save report
- Place in shared folder
- Assign security roles
Testing the Bursting Setup
Example Test Case: Payslip
- Run report for a specific payroll period
- System generates:
- Individual PDFs per employee
- Emails sent automatically
Expected Results
- Each employee receives only their data
- Correct template used
- No data leakage across employees
Validation Checks
- Email received
- Correct attachment
- Data accuracy
- No missing recipients
Common Implementation Challenges
1. Email Not Triggering
Reason:
- SMTP not configured
Fix:
- Verify email server setup
2. Incorrect Data Splitting
Reason:
- Wrong KEY column
Fix:
- Ensure unique identifier (e.g., PERSON_NUMBER)
3. Template Not Applied
Reason:
- Template name mismatch
Fix:
- Verify exact template name in bursting query
4. Performance Issues
Large datasets may:
- Delay report generation
- Cause timeout
Solution:
- Schedule report in batches
- Optimize SQL
Best Practices from Real Projects
1. Always Use Unique Bursting Key
Avoid:
- Department
Use: - Person Number
2. Keep Bursting Query Lightweight
Avoid complex joins
- Fetch only required columns
3. Validate Email Data Early
Before go-live:
- Run SQL to check null emails
4. Use Separate Templates for Localization
Example:
- India vs US payslip formats
5. Test with Small Dataset First
- Validate logic before full run
6. Secure Sensitive Reports
Payslips contain sensitive data:
- Restrict report access
- Use role-based security
Summary
Bursting in Oracle Fusion HCM is not just a reporting feature—it is a critical automation capability that enables:
- Personalized report delivery
- Scalable HR operations
- Reduced manual effort
In real implementations, mastering bursting makes a huge difference in:
- Payroll automation
- Employee communication
- Compliance reporting
If you understand data model + bursting query + delivery setup, you can handle 90% of real-world reporting requirements.
For deeper reference, always check Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. What is the difference between bursting and scheduling?
- Scheduling runs reports at specific times
- Bursting distributes report output to multiple recipients
2. Can we use bursting for Excel reports?
Yes, bursting supports:
- Excel
- RTF
- XML
3. Can bursting send reports to multiple channels?
Yes, you can configure:
- Email + FTP + Printer simultaneously