Oracle Fusion HCM OTBI - Chapter 10: OTBI Real-Time vs Historical Reporting
๐ Content
What’s the Difference Between Real-Time and Historical Reporting in OTBI?
OTBI is primarily designed for real-time, transactional reporting. However, Fusion HCM also supports historical and trend analysis, often handled through archived data or data warehouse tools like Oracle BI Publisher (BIP), Data Warehouse Cloud (PaaS), or Oracle Analytics Cloud (OAC).
๐ Real-Time Reporting in OTBI
Real-time subject areas directly reflect the most current data in the Oracle Fusion application.
✅ Characteristics:
-
Instant visibility of HR, payroll, or absence changes
-
Used for operational reports and daily tasks
-
Data pulled directly from live transactional tables
๐ Examples:
-
Employee transfers today show up immediately
-
Absences approved a minute ago appear in OTBI Absence Real Time
-
Real-time headcount dashboards
๐ Historical Reporting in Fusion
Historical data reporting requires capturing past snapshots, which OTBI doesn't retain by default.
๐น Use Cases:
-
Headcount trends over time
-
Salary progression of employees
-
Year-on-year attrition rate
๐น How to achieve this:
-
Use Workforce Trend Analysis subject areas (available with Oracle Analytics Cloud or HCM Data Warehousing)
-
Use BI Publisher with custom queries if needed
-
Alternatively, use Extracts or HDL to store periodic data snapshots manually
๐ง Real-Time Scenario Comparison
Use Case | Tool | Subject Area |
---|---|---|
See current employee’s department | OTBI | Worker Assignment Real Time |
See employee’s department history over the last 5 years | BI Publisher or Data Warehouse | Workforce Assignment Event History |
Monthly headcount tracking | BIP with snapshot logic | Custom extracts or OAC |
❗ Limitations of OTBI Real-Time Reporting
Limitation | Explanation |
---|---|
No snapshot support | Can't compare "today" vs "last month" directly |
No cross-subject joins | Limited to one subject area per analysis |
Audit trail not available | No default history unless you use event-based subject areas |
๐ When to Use OTBI vs BI Publisher
Requirement | Use OTBI? | Use BIP? |
---|---|---|
Current values (live) | ✅ Yes | ❌ No |
Past changes / audit | ❌ No | ✅ Yes |
Complex formatting / PDFs | ❌ Limited | ✅ Yes |
Scheduled bursting to email | ❌ No | ✅ Yes |
Cross-subject joins or data warehouse | ❌ No | ✅ Yes |
๐ก Best Practices
-
For daily insights and dashboards → use OTBI
-
For trend analysis, scheduled reporting, or snapshot history → use BI Publisher or OAC
-
Use event-based OTBI subject areas like Worker History Event Real Time for partial history needs
No comments:
Post a Comment