Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 54 Oracle Analytics and AI Sharing Center
- 26 Oracle Analytics and AI Lounge
- 312 Oracle Analytics and AI News
- 57 Oracle Analytics and AI Videos
- 16.4K Oracle Analytics and AI Forums
- 6.7K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 117 Oracle Analytics and AI Trainings
- 24 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Include Enterprise Onboarding and Enterprise Onboarding Step Categories in FDI – HCM Journeys Subjec
🚨
Product
Fusion Data Intelligence (FDI)
Module
HCM – Journeys
Problem Statement
Currently, the Journey categories Enterprise Onboarding (ORA_ONB_ENT_ONBOARDING) and Enterprise Onboarding Step (ORA_ONB_ENT_ONBOARDING_STEP) are not available in the FDI HCM – Journeys subject area.
Although these categories exist in Fusion HCM, are active, and are correctly stored in FDI dimension tables, they are not exposed in the FDI semantic model and are excluded from reporting and analytics.
Oracle Support confirmed during an OWC that these categories are out of scope of the current FDI semantic model, and advised opening an Idea for enhancement.
Business Impact
- Customers are unable to report on Enterprise Onboarding journeys, which are core onboarding processes.
- Inconsistent analytics: other Journey categories (Person, Contextual, Onboard, Offboard, Transfer, etc.) are available, while Enterprise Onboarding categories are missing.
- Limits visibility, compliance tracking, and onboarding KPIs for enterprise onboarding processes.
- Forces customers to rely on Fusion HCM transactional reports instead of FDI analytics.
- The lack of Enterprise Onboarding analytics in FDI has direct and indirect financial consequences, including:
- Increased operational cost: HR and Analytics teams must build manual extracts or parallel reports in Fusion HCM, increasing effort, rework, and support costs.
- Delayed onboarding completion: Without visibility into onboarding progress and bottlenecks, delays in onboarding steps can directly impact employee productivity and time-to-value.
- Risk of compliance penalties: Enterprise onboarding often includes mandatory legal, policy, and compliance steps. Lack of centralized analytics increases the risk of missed or late completions, which may result in fines, audit findings, or legal exposure.
- Inefficient workforce planning: Executives lack reliable onboarding metrics to forecast workforce readiness, potentially causing overstaffing, understaffing, or delayed project starts.
- Reduced ROI on FDI investment: Customers pay for FDI expecting end-to-end HCM analytics. Excluding a core onboarding category reduces adoption and undermines the business case for the analytics platform.
- For large enterprises with high onboarding volumes, even small inefficiencies or delays can translate into significant recurring financial losses over time.
Evidence / Current Behavior
- The categories ORA_ONB_ENT_ONBOARDING and ORA_ONB_ENT_ONBOARDING_STEP:
- Exist in Fusion HCM Journey Templates.
- Exist in FDI dimension table DW_JRNY_CHECKLIST_CATEGORY_D_TL.
- Do not appear in FDI facts (e.g., DW_JRNY_ALLOCATED_CHECKLIST_EF_SEC).
- Do not appear in the FDI HCM – Journeys subject area (Category / Category Code).
- Other Journey categories are successfully exposed and reportable in FDI.
- Oracle Support confirmed this is not a data issue, but a semantic model scope limitation.
Documentation Reference
Oracle documentation states that FDI supports HCM – Journeys metrics broadly, without explicitly excluding Enterprise Onboarding categories:
https://docs.oracle.com/en/cloud/saas/analytics/25r4/fahia/hcm---journeys-metrics.html
This creates a gap between documented capabilities and actual FDI behavior.
Expected Behavior
- Enterprise Onboarding and Enterprise Onboarding Step categories should be:
- Included in the FDI HCM – Journeys semantic model.
- Available in Journey dimensions (Category / Category Code).
- Properly linked to Journey facts, allowing full reporting and filtering.
- FDI should provide complete Journey analytics, consistent with Fusion HCM.
Proposed Enhancement
Extend the FDI HCM – Journeys semantic model to include:
- ORA_ONB_ENT_ONBOARDING
- ORA_ONB_ENT_ONBOARDING_STEP
Ensuring consistency with other supported Journey categories and with Fusion HCM functionality.
Customer Use Case
Organizations rely on Enterprise Onboarding journeys for:
- New hire onboarding at scale
- Compliance and mandatory onboarding steps
- Process monitoring and executive reporting
Excluding these categories significantly reduces the value of FDI for HCM onboarding analytics.