Oracle HCM Cloud (Oracle Fusion Human Capital Management) is not a collection of disconnected HR modules—it's a unified, multi-tenant SaaS platform built on Oracle Cloud Infrastructure (OCI) that manages the entire employee lifecycle from hire to retire. Understanding its architecture is essential for anyone designing, implementing, or documenting enterprise HR solutions.
Here's a complete guide to Oracle HCM Cloud architecture diagrams—what they include, how they work, and how to build them.
Cloud Architecture
Create cloud architecture diagrams for AWS, Azure, GCP, and more. Design scalable infrastructure with professional cloud icons.
Complete guide to Oracle HCM Cloud architecture diagrams—UI, modules, business logic, data layer, security, HDL/OIC integration patterns, analytics, and best practices.
Click Cloud Architecture to open AI Line Studio and generate diagrams from natural language in seconds.
Oracle HCM Cloud Architecture defines how different components of the HCM system are structured, interact, and process data within the Oracle Cloud ecosystem. At a high level, it includes:
Oracle Fusion HCM runs on Oracle Cloud Infrastructure (OCI) and follows a multi-tenant SaaS model, meaning Oracle manages the infrastructure while customers configure business processes. Updates (like 26A) are applied automatically—this is fundamentally different from legacy on-premise systems like EBS.
This is what end users interact with. The UI is completely metadata-driven, meaning configurations reflect instantly.
What to include in your diagram:
This layer contains all business functionalities. Core modules include:
| Module | Purpose |
|---|---|
| Core HR | Global Human Resources—person, assignment, organization management |
| Absence Management | Leave and time-off tracking |
| Payroll | Global payroll processing |
| Benefits | Employee benefits administration |
| Talent Management | Performance, goals, succession planning |
| Compensation | Salary, bonuses, and rewards |
| Recruiting (ORC) | Oracle Recruiting Cloud |
| Learning (OLC) | Oracle Learning Cloud |
| Workforce Management | Time & Labor, absence |
Each module operates independently but shares a common data model.
This is where rules are processed.
Components to diagram:
Example: When an employee applies for leave, the system validates eligibility, routes approval based on hierarchy, and applies accrual logic—all in the business logic layer.
This is the backbone of Oracle Fusion HCM.
Key tables:
PER_ALL_PEOPLE_F — Employee recordsPER_ALL_ASSIGNMENTS_M — Job assignmentsPER_PERSON_NAMES_F — Person namesPER_JOBS_F — Job definitionsCharacteristics:
Example: If an employee changes department, a new row is created and old data is preserved—critical for audit and reporting.
Oracle Fusion uses a role-based security model.
Types of roles:
Security layers:
Example: An HR Manager in India cannot view US employee data.
Integration is one of the most critical parts of the architecture.
Tools used:
Example: Integrating a payroll system: Employee data extracted via REST API → sent to external payroll via OIC → results loaded back using HDL.
Oracle provides multiple reporting tools:
| Tool | Purpose |
|---|---|
| OTBI | Real-time analytics and dashboards |
| BI Publisher | Pixel-perfect reports |
| HCM Extracts | Data extraction for external systems |
Example: Monthly headcount report → OTBI. Payroll report → BI Publisher.
Oracle documents the enterprise topology for the Oracle Fusion Human Capital Management domain as a three-tier architecture:
| Tier | Components |
|---|---|
| Web Tier / DMZ | Web servers, hardware load balancers |
| Application Tier | Application servers, business logic |
| Data Tier | Databases containing customer data and schemas |
This tiered structure should be clearly represented in any Oracle HCM Cloud architecture diagram.
Integration is mission-critical for Oracle HCM Cloud. It enables seamless information exchange between systems for accurate transaction processing and reporting.
Oracle HCM Cloud has multiple capabilities for batch and real-time integration scenarios:
| Pattern Type | Examples |
|---|---|
| Inbound Batch/File | HDL, HSDL, File-based integrations |
| Inbound API | REST APIs, SOAP Web Services |
| Outbound Batch/File | HCM Extracts, BI Publisher |
| Outbound API | REST APIs for downstream systems |
External/internal applications send files in HCM Data Loader (HDL) format. The HDL process consumes files and imports data into HCM base tables. HDL can decrypt files using shared key pairs.
Diagram elements:
When external applications cannot send files in HDL format, transformation Fast Formulas inside Payroll flow convert non-cloud files into HDL format.
Note: This works well for low/medium volume transformations. For high volume with complex calculations, consider alternative patterns.
Real-time integration where external systems push data via REST or SOAP APIs directly into HCM Cloud.
HCM Extracts use BI Publisher as the delivery mechanism for extracted data. A reference architecture shows how to configure Oracle Data Integrator (ODI) to replicate data from Fusion HCM Cloud using HCM Extracts into an Autonomous Data Warehouse (ADW).
Data flow:
Oracle HCM Cloud integrates with OCI IAM for authentication and authorization.
Key concepts:
Diagram elements:
Oracle Transactional Business Intelligence (OTBI) provides real-time analytics on HCM data. Key components include:
Fusion HCM Analytics provides comprehensive workforce and turnover data sourced from Fusion HCM Cloud in a warehouse designed to support broad analytics use cases. For specific use cases, HCM data can be complemented with payroll and costing data using HCM Extracts.
Clearly show the Web Tier (DMZ), Application Tier, and Data Tier.
OIC and HDL are the central nervous system of HCM architecture. Show:
Security is foundational to HCM architecture. Include:
Include key Fusion tables and their relationships:
Integration patterns differ by direction. Show:
Oracle provides official icons through the OCI Architecture Diagram Toolkit. Using unofficial icons creates confusion and undermines credibility.
A generic "Database" label is not enough. Write "PER_ALL_PEOPLE_F — Employee Records" or "HDL Process — Bulk Data Load" to be precise.
Oracle provides official icons in multiple formats:
.pptx): Most comprehensive, with templates and examples.zip): Pre-loaded with OCI icon library.zip): Official OCI stencilsOracle provides reference architecture diagrams for HCM analytics, integrations, and enterprise topology.
AI Line Studio generates cloud architecture diagrams from natural language descriptions in 15–20 seconds, supporting 3,000+ officially licensed icons across AWS, Azure, GCP, and OCI. The AI cloud diagram generator helps you iterate quickly during design sessions. The AI architecture diagram builder enables collaborative editing and refinement, and the AI system architecture generator creates end-to-end diagrams for complex systems. The cloud architecture diagram tool provides editable templates with official icons.
Mistake 1: Treating HCM modules as silos. Oracle HCM Cloud is a unified platform with a common data model. Your diagram must show how modules share data.
Mistake 2: Ignoring the integration layer. OIC and HDL are central to HCM architecture. Omitting them misses the most important part of the story.
Mistake 3: Using the wrong integration pattern. Most failures are due to incorrect pattern selection. Use HDL for bulk inbound, REST APIs for real-time, and HCM Extracts for outbound.
Mistake 4: Treating BI Publisher and OTBI as integration tools. They are reporting tools, not integration tools. Use HCM Extracts for data extraction.
Mistake 5: Leaving security invisible. Security isn't optional—it's foundational. Show IAM, roles, and data security in your diagram.
Mistake 6: Not showing the tiered architecture. HCM uses a three-tier model: Web Tier, Application Tier, and Data Tier. Your diagram should reflect this structure.
Mistake 7: Forgetting about date-effectiveness. Fusion tables are date-effective. Your data layer diagram should show how history is tracked.
Oracle HCM Cloud architecture diagrams are the blueprint for how your organization manages its workforce. The platform's unified data model, role-based security, and comprehensive integration capabilities demand a careful, layered approach to diagramming.
Start with the three-tier architecture: Web Tier, Application Tier, and Data Tier. Show the functional modules (Core HR, Payroll, Talent Management, Recruiting). Include the integration layer (OIC, HDL, REST APIs, HCM Extracts). Document the security framework (roles, functional security, data security). And always—always—show how data flows between systems.
The best Oracle HCM Cloud architecture diagrams tell a complete story: how employee data moves from hire to retire, how it's secured and governed, and how it integrates with payroll, benefits, and analytics. If your diagram can't tell that story, it's not doing its job.