Burst HCM BI Report to SFTP

Introduction

Burst Fusion HCM BI Report to SFTP is a very common requirement in real-world Oracle implementations, especially when organizations need to distribute employee, payroll, or HR data securely to external systems. In Oracle Fusion HCM, BI reporting combined with bursting and secure file transfer ensures automated, scalable, and compliant data delivery.

From a consulting perspective, this requirement typically arises during payroll integrations, third-party benefits processing, or compliance reporting—where data must be delivered in structured formats like CSV or XML directly to external vendors via SFTP.

This blog walks you through a complete implementation approach using Oracle BI Publisher bursting functionality to deliver reports to an SFTP server.

What is Burst Fusion HCM BI Report to SFTP?

Bursting in BI Publisher is a mechanism that allows a single report to be split into multiple outputs based on specific criteria and delivered to different destinations.

When we combine bursting with SFTP delivery:

• Report runs once
• Data splits based on bursting logic
• Each output file is generated
• Files are automatically sent to SFTP location

This avoids manual download/upload and supports automation.

Key Features

1. Automated File Delivery

• No manual intervention required
• Scheduled jobs can trigger report bursting

2. Dynamic File Splitting

• Reports can be split by:
  • Business Unit
  • Legal Entity
  • Department
  • Employee

3. Secure Data Transfer

• Uses encrypted SFTP protocol
• Ensures compliance for sensitive HR data

4. Flexible Output Formats

• CSV
• XML
• Excel
• PDF

5. Integration Ready

• Works seamlessly with external payroll vendors
• Can be combined with Oracle Integration Cloud if needed

Real-World Business Use Cases

Use Case 1: Payroll Vendor Integration

A company sends monthly payroll data to a third-party vendor.

• Report extracts employee payroll data
• Bursting splits by country
• Files sent to vendor SFTP

Use Case 2: Benefits Provider Data Feed

Benefits provider requires employee eligibility data daily.

• Report scheduled daily
• Bursting by benefit plan
• Output delivered to SFTP automatically

Use Case 3: Compliance Reporting

Government requires employee data submission.

• Report generates statutory format
• Bursting splits by region
• Files delivered securely

Architecture / Technical Flow

Here’s how it works in a typical implementation:

1. Data Model fetches data from HCM tables
2. BI Report template formats output
3. Bursting Query defines:
   • Split logic
   • Delivery details
4. BI Publisher processes report
5. Files generated
6. Files transferred to SFTP server

Prerequisites

Before implementation, ensure:

1. BI Report is Ready

• Data Model created
• Template designed

2. SFTP Server Details

You must have:

• Host name
• Port (usually 22)
• Username
• Password or SSH key
• Target directory path

3. Roles & Access

User must have:

• BI Administrator Role
• Report Developer Role

4. Bursting Requirement Clarity

• How to split data?
• File naming convention?
• Output format?

Step-by-Step Build Process

Step 1 – Create Data Model

Navigation:

• Create SQL Query
• Example:

Step 2 – Create BI Report

Navigation:

• Upload template (Excel/RTF)
• Define layout

Step 3 – Create Bursting Query

Bursting query is the core component.

Example:

Key Columns Explained

Step 4 – Configure Bursting in Report

• Open Report
• Go to Properties
• Enable Bursting
• Attach bursting query

Step 5 – Configure SFTP Delivery

In bursting query:

• Use SFTP as delivery channel
• Provide correct credentials
• Ensure server is accessible from Fusion

Step 6 – Save Configuration

• Validate report
• Save in shared folder
• Assign proper permissions

Testing the Technical Component

Test Scenario

Run report manually:

Expected Output

• Report splits based on department
• Multiple files generated:
  • OUTPUT_HR.csv
  • OUTPUT_FINANCE.csv

Validation Checks

• Files appear in SFTP folder
• File format is correct
• Data is accurate
• Naming convention is followed

Common Errors and Troubleshooting

1. SFTP Connection Failure

Cause:

• Incorrect host/port
• Firewall issues

Fix:

• Validate connectivity
• Check credentials

2. Bursting Not Triggered

Cause:

• Bursting not enabled

Fix:

• Enable bursting in report properties

3. File Not Generated

Cause:

• Incorrect KEY mapping

Fix:

• Ensure KEY column matches report grouping

4. Permission Issues

Cause:

• No access to SFTP directory

Fix:

• Update SFTP permissions

Best Practices

1. Use Secure Credentials Storage

Avoid hardcoding passwords:

• Use encrypted storage
• Rotate credentials regularly

2. Standardize File Naming

Example:

3. Schedule Reports

• Use ESS jobs for automation
• Avoid manual execution

4. Monitor Logs

• Always check BI logs after deployment
• Enable debugging if needed

5. Combine with OIC for Advanced Use Cases

For complex integrations:

• Use Oracle Integration Cloud
• Add transformations, validations, retries

Summary

Burst Fusion HCM BI Report to SFTP is a critical integration pattern used in almost every enterprise implementation. It enables:

• Automated report delivery
• Secure file transfer
• Scalable data distribution

From a consultant’s perspective, mastering bursting + SFTP setup in Oracle Fusion HCM significantly improves your ability to handle real-time client requirements, especially in payroll and compliance integrations.

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

FAQs

1. Can we use SSH key instead of password for SFTP?

Yes, BI Publisher supports SSH key-based authentication, which is more secure and recommended.

2. Can bursting send files to multiple destinations?

Yes, you can configure multiple delivery channels like Email, FTP, and SFTP in the same bursting query.

3. Can we schedule bursting reports?

Yes, you can schedule them using ESS jobs or BI Scheduler for complete automation.