Skip to content
Data warehouse ⇄ Human resources

Exasol to Oracle Fusion Cloud HCM integration — real-time, two-way sync

Keep Exasol and Oracle Fusion Cloud HCM in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Exasol and Oracle Fusion Cloud HCM

Land the people and organization records from Oracle Fusion Cloud HCM in Exasol as live tables for workforce reporting, without extract jobs, and write computed results back where Oracle Fusion Cloud HCM can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Oracle Fusion Cloud HCM is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Exasol next to everything else the company measures.

Stacksync syncs Positions, Departments (Organizations), Locations, Grades and Salaries from Oracle Fusion Cloud HCM into tables in Exasol continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Exasol, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Oracle Fusion Cloud HCM where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Keep dimension tables such as customers and products aligned with the systems of record.
  • 02 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.
  • 03 Two-way sync Workers and Assignments with an operational Postgres so internal apps read reporting lines, departments, and locations in SQL while HR keeps mastering data in Oracle HCM.
  • 04 Provision identities and app access downstream when an Atom new-hire or termination feed event fires, joining Workers, Assignments, Departments, and Locations.

Common sync patterns

Queryable history for planning and audit

A continuously synced copy in Exasol gives you a durable, queryable record of how Oracle Fusion Cloud HCM's records change over time, for headcount planning and audit questions.

Write-back of computed values

Segments, rollups, or risk flags computed in Exasol sync back onto the matching records in Oracle Fusion Cloud HCM, where the HR team sees them in the system they already use.

HR data in the warehouse, minus the pipeline

People and organization records from Oracle Fusion Cloud HCM arrive in Exasol as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

What you can sync between Exasol and Oracle Fusion Cloud HCM

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Exasol objects Oracle Fusion Cloud HCM objects How this pairing syncs
Views Read-only query surfaces often used as curated sources for reverse ETL. Grades and Salaries Grade, grade-rate, and worker compensation records; usually read out for compensation and headcount analytics, and written back for corrections. Views is specific to Exasol and Grades and Salaries to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. Virtual schemas is specific to Exasol and Absences (workerAbsenceEntries) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. Workers (publicWorkers) Person master with personNumber, names, national IDs, and work relationships; synced two-way via the /workers resource, which replaced the desupported /emps resource. UDF scripts is specific to Exasol and Workers (publicWorkers) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. Assignments Child of a worker's work relationship carrying job, position, department, location, grade, and manager; effective-dated, so writes go through PATCH with an effective date. Users and roles is specific to Exasol and Assignments to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Schemas Namespaces that group the tables a sync reads from or writes into. Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. Schemas is specific to Exasol and Jobs to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. Tables is specific to Exasol and Positions to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.

How changes propagate between Exasol and Oracle Fusion Cloud HCM

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Exasol Oracle Fusion Cloud HCM Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

DeliveryEach detected change is written to Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.

Oracle Fusion Cloud HCM Exasol Sub-second propagation

DetectionChanges in Oracle Fusion Cloud HCM are captured at the source via change data capture — no polling loop against its API. Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change).

DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • Oracle Fusion Cloud HCM: Oracle publishes no fixed per-tenant REST rate limit; pages are capped via limit/offset and Oracle recommends client-side throttling, backoff, and using HDL for mass loads rather than transactional REST.
What ships with Exasol ⇄ Oracle Fusion Cloud HCM

Connect Exasol and Oracle Fusion Cloud HCM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Oracle Fusion Cloud HCM connection.

Real-time

Two-way sync

Changes in Exasol or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Exasol or Oracle Fusion Cloud HCM data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Exasol or Oracle Fusion Cloud HCM record.

Observability

Monitoring

Track your Exasol ⇄ Oracle Fusion Cloud HCM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Exasol and Oracle Fusion Cloud HCM.

How the Exasol and Oracle Fusion Cloud HCM connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

Oracle Fusion Cloud HCM

Integration surface
REST API (/hcmRestApi/resources), Atom feeds, and HCM Data Loader (HDL) for bulk
Authentication
OAuth 2.0 bearer tokens via Oracle Identity Cloud Service (IDCS/IAM); HTTP Basic and SAML/JWT bearer over SSL are also accepted, enforced by Oracle Web Services Manager (OWSM)
Change detection
Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change); REST q= filters on LastUpdateDate and HCM Extract in incremental mode cover broader deltas
Capabilities
read · write · CDC
Rate limits
Oracle publishes no fixed per-tenant REST rate limit; pages are capped via limit/offset and Oracle recommends client-side throttling, backoff, and using HDL for mass loads rather than transactional REST.
How it works

How to connect Exasol to Oracle Fusion Cloud HCM — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Exasol and Oracle Fusion Cloud HCM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Exasol connected
    Oracle Fusion Cloud HCM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Exasol and Oracle Fusion Cloud HCM objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Exasol ⇄ Oracle Fusion Cloud HCM
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Exasol Oracle Fusion Cloud HCM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Exasol and Oracle Fusion Cloud HCM integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 431 integrations available for Exasol and Oracle Fusion Cloud HCM.

Popular · 7 of 431
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.