Skip to content
Human resources ⇄ Data warehouse

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

Keep Oracle Fusion Cloud HCM and Starburst Enterprise 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 Oracle Fusion Cloud HCM and Starburst Enterprise

Land the people and organization records from Oracle Fusion Cloud HCM in Starburst Enterprise 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 Starburst Enterprise next to everything else the company measures.

Stacksync syncs Locations, Grades and Salaries, Absences (workerAbsenceEntries), Workers (publicWorkers) from Oracle Fusion Cloud HCM into tables in Starburst Enterprise continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Starburst Enterprise, 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 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • 02 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 03 Replicate Grades and Salaries into a warehouse for compensation and headcount analytics without exporting HDL files.
  • 04 Keep Positions and Departments aligned between Oracle HCM and a finance/ERP system so cost centers and reporting structures match.

Common sync patterns

HR data in the warehouse, minus the pipeline

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

Headcount and cost joined with everything else

Analysts combine Oracle Fusion Cloud HCM's workforce records with finance, product, or operational data already in Starburst Enterprise for reporting the HR system cannot produce on its own.

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

What you can sync between Oracle Fusion Cloud HCM and Starburst Enterprise

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.

Oracle Fusion Cloud HCM objects Starburst Enterprise objects How this pairing syncs
Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. Columns Typed per the Trino type system, mapped from each source's native types. Absences (workerAbsenceEntries) is specific to Oracle Fusion Cloud HCM and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Workers (publicWorkers) is specific to Oracle Fusion Cloud HCM and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Assignments is specific to Oracle Fusion Cloud HCM and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.
Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. Tables Queryable relations; writes pass through to sources whose connectors support them. Jobs is specific to Oracle Fusion Cloud HCM and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. Views Engine-level SQL views used to shape federated data before syncing it out. Positions is specific to Oracle Fusion Cloud HCM and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
Departments (Organizations) Org-structure records that define cost centers and reporting lines; typically mastered in HCM and read into other systems. Materialized views Precomputed results that make repeated sync reads cheaper. Departments (Organizations) is specific to Oracle Fusion Cloud HCM and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Oracle Fusion Cloud HCM and Starburst Enterprise

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.

Oracle Fusion Cloud HCM Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Oracle Fusion Cloud HCM Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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

Rate-limit considerations

  • 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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Oracle Fusion Cloud HCM ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Oracle Fusion Cloud HCM or Starburst Enterprise 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 Oracle Fusion Cloud HCM or Starburst Enterprise record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Oracle Fusion Cloud HCM and Starburst Enterprise connectors work

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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Oracle Fusion Cloud HCM to Starburst Enterprise — 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 Oracle Fusion Cloud HCM and Starburst Enterprise 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
    Oracle Fusion Cloud HCM connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Oracle Fusion Cloud HCM and Starburst Enterprise 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 · Oracle Fusion Cloud HCM ⇄ Starburst Enterprise
    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
    Oracle Fusion Cloud HCM Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Oracle Fusion Cloud HCM and Starburst Enterprise 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:

Coworkers laughing in front of a laptop in a casual office setting

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