BI Reports in Oracle HCM

Share

 

Introduction

In modern HR operations, reporting is not just about extracting data—it’s about delivering actionable insights. In Oracle Fusion HCM, BI Reports play a critical role in enabling organizations to generate pixel-perfect reports for payroll, compliance, employee data, and audit requirements.

If you’ve worked on an implementation project, you already know that business users frequently ask for custom reports beyond OTBI dashboards. That’s where BI Publisher (BIP) Reports come into play.

This blog provides a complete, consultant-level understanding of BI Reports in Oracle Fusion HCM, including architecture, setup, development, real-time use cases, and troubleshooting.


What are BI Reports in Oracle Fusion HCM?

BI Reports in Oracle Fusion HCM are formatted, printable reports created using Oracle BI Publisher. These reports are designed to:

  • Extract data using SQL queries or data templates
  • Format output using templates (RTF, Excel, PDF, etc.)
  • Deliver reports via UI, email, or bursting

Unlike OTBI, which is more analytical, BI Reports are:

FeatureBI Reports (BIP)OTBI
PurposePixel-perfect reportingInteractive analysis
OutputPDF, Excel, WordDashboard
Data SourceSQL / Data ModelSubject Areas
SchedulingYesLimited

Key Features of BI Reports

1. Pixel-Perfect Formatting

You can design highly formatted reports like payslips, offer letters, and compliance reports.

2. Multiple Output Formats

  • PDF
  • Excel
  • CSV
  • XML

3. Bursting Capability

Generate and send reports to multiple recipients based on conditions (e.g., employee payslips via email).

4. Data Models with Multiple Sources

Combine:

  • SQL Queries
  • HCM Extracts
  • Web Services

5. Parameterized Reports

Allow users to input filters like:

  • Business Unit
  • Department
  • Date range

Real-World Business Use Cases

Use Case 1: Employee Payslip Generation

A global company uses BI Publisher to:

  • Generate monthly payslips
  • Burst reports per employee
  • Email automatically

👉 This is one of the most common real-time implementations.


Use Case 2: HR Compliance Reporting

Government reporting requirements often require:

  • Employee demographic reports
  • Diversity reporting
  • Statutory submissions

👉 BI Reports ensure formatted compliance outputs.


Use Case 3: Offer Letter Automation

During hiring:

  • Offer letters are generated using BI Publisher
  • Data pulled from HCM tables
  • Delivered in PDF format

👉 This integrates with Recruiting and Core HR.


Architecture / Technical Flow

Understanding architecture is critical for interviews and real projects.

BI Report Flow

  1. User runs report
  2. BI Publisher calls Data Model
  3. Data Model executes SQL query
  4. Data is passed to Template
  5. Output generated (PDF/Excel)
  6. Optional bursting logic executed

Components Involved

  • Data Model
  • Report Template
  • Report Definition
  • Bursting Control File

Prerequisites

Before creating BI Reports, ensure:

1. Required Roles

  • BI Administrator Role
  • BI Author Role

2. Access to BI Catalog

Navigation:

 
Navigator → Tools → Reports and Analytics
 

3. SQL Knowledge

You must understand:

  • HCM Tables (PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_M, etc.)
  • Joins and filters

4. Data Security Awareness

Reports must respect:

  • Data roles
  • Security profiles

Step-by-Step Build Process

Let’s walk through a real implementation scenario: Creating an Employee Report.


Step 1 – Navigate to BI Publisher

 
Navigator → Tools → Reports and Analytics
 

Click:

 
Browse Catalog
 

Step 2 – Create Data Model

Go to:

 
Shared Folders → Custom → HCM → Data Models
 

Click:

 
New → Data Model
 

Define SQL Query

Example:

 
SELECT
papf.person_number,
papf.full_name,
paam.assignment_number,
paam.department_id
FROM
per_all_people_f papf,
per_all_assignments_m paam
WHERE
papf.person_id = paam.person_id
 

Key Fields Explanation

FieldDescription
PERSON_NUMBERUnique employee ID
FULL_NAMEEmployee name
ASSIGNMENT_NUMBERJob assignment
DEPARTMENT_IDDepartment

Step 3 – Add Parameters

Example:

  • Business Unit
  • Department

This allows dynamic filtering.


Step 4 – Save Data Model

Save under:

 
/Custom/HCM/Data Models
 

Step 5 – Create Report Template

Download sample XML data and open in MS Word.

Use:

 
BI Publisher Add-in
 

Insert fields:

  • Employee Name
  • Assignment Number

Design layout professionally.


Step 6 – Upload Template

Go back to BI Publisher:

 
New → Report
 

Upload:

  • Data Model
  • Template

Step 7 – Configure Report Properties

Set:

  • Output format (PDF/Excel)
  • Default template
  • Layout

Step 8 – Save Report

Save under:

 
/Custom/HCM/Reports
 

Testing the Technical Component

Test Execution

Navigate:

 
Reports and Analytics → Open Report
 

Provide Input Parameters

Example:

  • Department = Finance

Expected Output

  • List of employees in Finance department
  • Correct formatting
  • No missing data

Validation Checklist

  • Data accuracy
  • Performance (query optimization)
  • Security restrictions

Common Errors and Troubleshooting

1. No Data Returned

Cause:

  • Incorrect SQL joins
  • Missing effective date filters

Solution:
Always include:

 
SYSDATE BETWEEN effective_start_date AND effective_end_date
 

2. Report Not Visible

Cause:

  • Missing catalog permissions

Solution:
Grant access via BI Catalog security.


3. Performance Issues

Cause:

  • Large dataset
  • Inefficient SQL

Solution:

  • Use bind variables
  • Limit columns

4. Bursting Not Working

Cause:

  • Incorrect bursting query

Solution:
Validate:

  • Email field
  • Output format

Best Practices

1. Always Use Effective Dating

HCM tables are date-effective—never skip filters.


2. Use Bind Parameters

Improves performance and flexibility.


3. Avoid Hardcoding Values

Instead of:

 
WHERE department_id = 10
 

Use parameter:

 
WHERE department_id = :P_DEPT
 

4. Optimize SQL Queries

  • Use indexes
  • Avoid unnecessary joins

5. Secure Your Reports

Ensure reports respect:

  • Data roles
  • Business units

6. Version Control

Maintain:

  • Data model versions
  • Template versions

Real Consultant Tip

In one implementation, a client faced slow payroll report generation (30+ minutes). The issue was:

  • No indexing
  • Multiple unnecessary joins

After optimization:

  • Reduced to 2 minutes

👉 Performance tuning is a critical skill for BI Developers.


Summary

BI Reports in Oracle Fusion HCM are essential for delivering structured, formatted, and business-ready outputs. While OTBI is useful for analysis, BI Publisher excels in:

  • Payroll reports
  • Offer letters
  • Compliance reporting

As a consultant, mastering BI Reports means understanding:

  • Data models
  • SQL queries
  • Templates
  • Security

For deeper reference, always check Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html


FAQs

1. What is the difference between BI Reports and OTBI?

BI Reports are used for formatted output, while OTBI is used for interactive analytics.


2. Can BI Reports be scheduled?

Yes, BI Reports can be scheduled and also configured with bursting for automated delivery.


3. What skills are required for BI Publisher?

You need:

  • SQL knowledge
  • Understanding of HCM tables
  • Template design (RTF/Excel)

Share

Leave a Reply

Your email address will not be published. Required fields are marked *