Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: TiDB and Oracle Fusion Cloud HCM share the same people, positions, and org structure in real time.

Oracle Fusion Cloud HCM is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. TiDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Grades and Salaries, Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments in Oracle Fusion Cloud HCM need to exist as queryable Sequences, Databases, Tables, Views in TiDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Sequences, Databases, Tables, Views in TiDB with Grades and Salaries, Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments in Oracle Fusion Cloud HCM field by field, in real time. You decide which system owns which fields — Oracle Fusion Cloud HCM typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
  • 02 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
  • 03 Sync Absences (workerAbsenceEntries) into a scheduling or workforce-management database for coverage planning.
  • 04 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.

Common sync patterns

Reporting and analytics on current data

Grades and Salaries, Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments replicate into TiDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Oracle Fusion Cloud HCM stay consistent in TiDB, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in TiDB write onto the matching record in Oracle Fusion Cloud HCM where those fields are writable, keeping the people system enriched.

What you can sync between Oracle Fusion Cloud HCM and TiDB

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 TiDB objects How this pairing syncs
Locations Physical work locations referenced by assignments; synced so downstream provisioning and directory tools resolve the same location codes. Databases MySQL-style schemas addressed by any MySQL-compatible client. Locations is specific to Oracle Fusion Cloud HCM and Databases to TiDB — each maps to any object or custom field on the other side.
Grades and Salaries Grade, grade-rate, and worker compensation records; usually read out for compensation and headcount analytics, and written back for corrections. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Grades and Salaries is specific to Oracle Fusion Cloud HCM and Tables to TiDB — each maps to any object or custom field on the other side.
Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. Views Logical views for shaping reads before syncing outward. Absences (workerAbsenceEntries) is specific to Oracle Fusion Cloud HCM and Views to TiDB — 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. Columns MySQL-compatible types mapped to fields in the paired system. Workers (publicWorkers) is specific to Oracle Fusion Cloud HCM and Columns to TiDB — 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. Indexes Secondary indexes that keep incremental sync queries efficient. Assignments is specific to Oracle Fusion Cloud HCM and Indexes to TiDB — 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. Sequences Server-side ID generation relevant when external systems write rows. Jobs is specific to Oracle Fusion Cloud HCM and Sequences to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Oracle Fusion Cloud HCM and TiDB

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 TiDB 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 TiDB as a row-level write, with types converted between the two schemas.

TiDB Oracle Fusion Cloud HCM Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

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.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Oracle Fusion Cloud HCM ⇄ TiDB

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

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

Real-time

Two-way sync

Changes in Oracle Fusion Cloud HCM or TiDB 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 TiDB 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 TiDB record.

Observability

Monitoring

Track your Oracle Fusion Cloud HCM ⇄ TiDB 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 TiDB.

How the Oracle Fusion Cloud HCM and TiDB 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.

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

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

    Choose tables

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

Oracle Fusion Cloud HCM and TiDB 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 7 of 428
All Oracle Fusion Cloud HCM integrations All TiDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own