Ellipse Gradient for Header

Oracle HCM Cloud Integration Guide

Integrate Oracle HCM Cloud with enterprise applications through REST and SOAP APIs, HCM Extracts, HDL files, and selected event notifications.

Oracle HCM Cloud integration options at a glance

Oracle HCM Cloud supports REST APIs for many workforce, recruiting, absence, benefits, payroll, and organizational resources, while SOAP services remain relevant for selected operations and legacy service contracts. HCM Extracts provide scheduled outbound files, and Oracle HCM Data Loader supports structured bulk inbound processing. Selected resources can provide Atom-feed or event-style notifications, although coverage is not universal. Authentication may use OAuth 2.0 or Basic Authentication subject to tenant configuration and Oracle roles. Martini can consume these APIs, retrieve and transform files, orchestrate asynchronous processing, expose normalized APIs, and apply validation, retry, and synchronization controls.

Integration pointSupported by Oracle HCM Cloud?Common use casesHow Martini supports it
REST APIsYesRetrieve, create, and update Workers, Persons, Assignments, Departments, Jobs, Positions, Locations, and other supported HCM resources. REST is generally the primary transactional integration mechanism.Martini can consume Oracle HCM REST APIs from workflows, handle pagination and filters, transform payloads, and expose a normalized API for downstream applications.
SOAP APIsYesSupport selected HCM operations, enterprise service contracts, and legacy integrations where the required capability is not available or is retained through SOAP.Martini can consume documented Oracle SOAP services, map XML request and response structures, and apply service-specific error handling.
Webhooks / outbound callbacksLimitedOracle HCM provides selected event and Atom-feed notification patterns for supported resources and events; coverage is not universal.Martini can receive supported notification patterns or use them to trigger workflows, then retrieve the authoritative resource and process it idempotently.
Bulk / async / batch APIsYesHCM Data Loader supports bulk inbound loading, while HCM Extracts support scheduled outbound processing. Some REST and SOAP operations may also be asynchronous.Martini can submit files or asynchronous requests, poll for completion, retrieve results, and map row-level errors into an operational model.
File / attachment APIsLimitedHCM Extracts and HDL support file-oriented integration; attachment operations are available only for selected resources and releases.Martini can retrieve, validate, transform, deliver, and archive files, and can process documented attachment endpoints when the Oracle resource supports them.
Analytics and reporting accessLimitedOTBI, BI Publisher, HCM Extracts, and related reporting services support reporting and outbound data delivery. Direct access to the underlying HCM database is not assumed.Martini can consume supported report or extract outputs and route them through workflows, but should use REST or SOAP for operational transactions where appropriate.
AuthenticationYesOracle Cloud integrations may use OAuth 2.0 or Basic Authentication, subject to endpoint, tenant, user-role, and security configuration.Martini stores credentials and tokens in environment configuration or secrets management and applies the authentication required by the Oracle endpoint.
Database accessNoCustomer integrations should not assume direct access to the underlying Oracle HCM Cloud database schema.Martini can use documented APIs, extracts, reports, files, or supported database endpoints elsewhere in the enterprise instead of depending on Oracle HCM database access.

How Oracle HCM Cloud exposes data and business events

Oracle HCM Cloud REST APIs

Oracle HCM Cloud REST APIs provide resource-oriented access to many workforce, workforce-structure, recruiting, absence, benefits, payroll, and related objects. Supported operations and attributes vary by release, enabled module, and security configuration.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates to Oracle, retrieves or receives the required resource, follows pagination, maps the Oracle payload into a canonical model, applies business rules, and writes the result to the target system or returns it through a Martini API.

Implementation sequence

Authenticate with the configured Oracle HCM endpoint
Retrieve the required resource using supported filters
Follow pagination and capture the synchronization watermark
Map Oracle fields to the canonical model
Apply effective-date and business rules
Write the target result and record the outcome

Oracle HCM Cloud SOAP APIs

Oracle HCM Cloud SOAP services remain available for selected operations, enterprise service contracts, and legacy integration scenarios. The appropriate service and operation must be confirmed in Oracle documentation.

Martini implementation pattern

Martini implementation pattern: a workflow builds the documented SOAP request, sends it securely, parses the XML response, distinguishes transport errors from Oracle business faults, and routes successful and failed results consistently.

Implementation sequence

Authenticate to the documented SOAP service
Build the operation-specific XML request
Invoke the Oracle HCM SOAP operation
Parse the response and service faults
Map the result to the target model
Store correlation details and handle retryable failures

HCM Extracts and HDL files

HCM Extracts provide scheduled outbound workforce or payroll files, while Oracle HCM Data Loader supports structured bulk inbound loading of supported HCM business objects.

Martini implementation pattern

Martini implementation pattern: a scheduled or file-triggered workflow retrieves or receives the file, validates its structure and identity, transforms the content, submits or delivers it, and monitors Oracle processing and error files.

Implementation sequence

Retrieve or receive the HCM Extract or HDL file
Validate the file name, structure, and source identifier
Transform rows into the required target or HDL format
Submit or deliver the processed file
Poll for import or processing completion
Persist rejected rows and Oracle error details

Selected events and Atom feeds

Oracle HCM Cloud supports selected event and Atom-feed notification patterns, but coverage varies by resource and event and should not be treated as a universal webhook facility.

Martini implementation pattern

Martini implementation pattern: Martini receives a supported notification or periodically checks for changes, retrieves the authoritative Oracle resource, applies deduplication and effective-date logic, and falls back to scheduled REST polling or extracts where notifications are unavailable.

Implementation sequence

Receive the selected Oracle notification or run the scheduled trigger
Validate the notification and identify the affected resource
Retrieve the current Oracle resource state
Apply deduplication and effective-date rules
Map and deliver the change to downstream systems
Record the notification and processing checkpoint

Common Oracle HCM Cloud integration patterns

Pattern 1: Synchronize workers and assignments

When to use this pattern

Use this pattern when Oracle HCM Cloud is the authoritative source for workforce identity, employment, manager, department, or assignment data. It supports scheduled incremental synchronization and can incorporate selected Oracle notifications.

Integration direction
Oracle HCM Cloud
Martini
ServiceNow
Example Mapping
Oracle HCM Cloud FieldCanonical FieldTarget Field
WorkerNumberemployeeIdemployee_number
PersonNamefullNamename
Assignment.DepartmentNamedepartmentNamedepartment
Assignment.ManagerPersonNumbermanagerIdmanager
Martini implementation pattern

Martini queries changed Workers, Persons, Work Relationships, and Assignments with Oracle-supported filters and pagination. It stores a watermark only after successful completion, handles future-dated changes, validates target references, and retries transient failures without creating duplicate updates.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination handling
  • data mapping
  • effective-date business rules
  • idempotency
  • error handling

Pattern 2: Orchestrate joiners, movers, and leavers

When to use this pattern

Use this pattern when workforce lifecycle changes must initiate identity, service-management, CRM, or access actions. Selected Oracle notifications may provide triggers, with scheduled polling or extracts used for changes without notification coverage.

Integration direction
Oracle HCM Cloud
Martini
Microsoft Entra ID
ServiceNow
Example Mapping
Oracle HCM Cloud FieldCanonical FieldTarget Field
Worker.StatusemploymentStatusaccountAction
Assignment.EffectiveStartDateeffectiveDaterequestStartDate
Assignment.DepartmentIddepartmentIddepartment
Assignment.ManagerPersonNumbermanagerIdmanagerReference
Martini implementation pattern

Martini identifies hires, transfers, manager changes, and terminations, then applies lifecycle rules and routes actions to the appropriate downstream APIs. It uses stable identifiers, separates future-dated actions from immediate actions, and records partial failures for controlled replay.

Martini capabilities used
  • event and schedule triggers
  • workflow orchestration
  • conditional routing
  • data transformation
  • business rules
  • retry and replay handling

Pattern 3: Export workforce data with HCM Extracts

When to use this pattern

Use this pattern for payroll-related downstream processing, benefits exchange, workforce reporting, data warehouse ingestion, or periodic identity reconciliation where a file-based delivery is appropriate.

Integration direction
Oracle HCM Cloud
Martini
Data warehouse
Example Mapping
Oracle HCM Cloud FieldCanonical FieldTarget Field
PersonNumberpersonIdperson_id
Assignment.JobCodejobCodejob_code
Assignment.DepartmentCodedepartmentCodedepartment_code
EffectiveDateeffectiveDateeffective_date
Martini implementation pattern

Oracle produces the scheduled extract and Martini retrieves or receives it, validates the source and checksum, parses and transforms the file, loads the target, and separates technical transfer success from business validation success. Failed rows and source files are retained for investigation.

Martini capabilities used
  • scheduled workflows
  • file processing
  • XML or JSON handling
  • data mapping
  • validation
  • batch processing
  • monitoring

Pattern 4: Load bulk HCM updates with HDL

When to use this pattern

Use this pattern when a source application must create or update a large set of supported Oracle HCM business objects and individual REST requests would be inefficient or inappropriate.

Integration direction
Source application
Martini
Oracle HCM Cloud
Example Mapping
Oracle HCM Cloud FieldCanonical FieldTarget Field
employeeIdpersonExternalIdSourceSystemId
departmentCodedepartmentReferenceDepartment
employmentStartDateeffectiveStartDateEffectiveStartDate
jobCodejobReferenceJob
Martini implementation pattern

Martini validates source data, orders parent and child HDL objects, applies effective dates and external identifiers, submits the file through the configured Oracle process, polls status, and maps row-level errors. Replay is controlled using source identifiers and immutable input files.

Martini capabilities used
  • workflow orchestration
  • file transformation
  • validation
  • business rules
  • asynchronous polling
  • bulk processing
  • error handling

Applications commonly integrated with Oracle HCM Cloud

Oracle HCM Cloud can serve as a workforce system of record for identity lifecycle, service management, CRM ownership, finance, and multi-HCM processes. The exact direction and ownership of each object should be defined for the enterprise landscape.

Application Scenario Direction Martini Pattern
Salesforce Synchronize worker, manager, territory, and user information to support CRM ownership and workforce processes. Oracle HCM Cloud → Martini → Salesforce Martini retrieves changed Workers, Persons, or Assignments, maps them to Salesforce user or ownership data, applies ownership rules, and retries transient API failures with idempotent identifiers.
ServiceNow Drive joiner, mover, and leaver workflows, update user records, and coordinate access-related service requests. Oracle HCM Cloud → Martini → ServiceNow A scheduled or notification-driven Martini workflow detects workforce changes, maps lifecycle attributes, creates or updates ServiceNow records, and records correlation and error details.
Microsoft Entra ID Provision, update, or disable workforce identities using employment status, assignment, and termination data. Oracle HCM Cloud → Martini → Microsoft Entra ID Martini reads authoritative worker and assignment changes, applies identity lifecycle rules, invokes the target API, and prevents duplicate actions through stable Oracle and external identifiers.
SAP SuccessFactors Exchange workforce or organizational information during coexistence, migration, or multi-system HCM programs. Oracle HCM Cloud → Martini → SAP SuccessFactors Martini coordinates bidirectional workflows with explicit object ownership, effective-date handling, canonical mappings, conflict rules, and replay-safe updates.
Workday Exchange workforce information in organizations operating multiple HCM platforms or executing an HCM migration. Oracle HCM Cloud → Martini → Workday Martini stages source changes, transforms worker and organization models, routes objects according to ownership rules, and retains processing checkpoints for migration or coexistence batches.
Oracle ERP Cloud Synchronize workers, departments, legal entities, cost centers, suppliers, and finance-related workforce data across Oracle Cloud applications. Oracle HCM Cloud → Martini → Oracle ERP Cloud Martini orchestrates REST or file-based exchanges, validates reference-data dependencies, maps shared Oracle business concepts, and handles asynchronous or bulk results.
Jira Create or update onboarding, access, and project tasks based on HCM lifecycle changes. Oracle HCM Cloud → Martini → Jira Martini detects hires, transfers, or terminations, applies task-routing rules, sends normalized requests to Jira, and logs failed or duplicate task operations.
NetSuite Synchronize employee, department, subsidiary, or approval-related information in organizations using NetSuite alongside Oracle HCM Cloud. Oracle HCM Cloud → Martini → NetSuite Martini maps Oracle workforce and organization objects to NetSuite fields, validates subsidiary and department references, and coordinates bidirectional updates where ownership is defined.

How to build a Oracle HCM Cloud integration in Martini

Objective

Configure the Oracle HCM Cloud endpoint and authentication according to the tenant and service requirements.

Instructions in Martini

  • Choose OAuth 2.0 or Basic Authentication only where supported by the Oracle endpoint
  • Store credentials, tokens, and environment-specific values in Martini configuration or secrets management
  • Confirm Oracle users, job roles, duty roles, data roles, and security profiles for each required object

Objective

Select the trigger that matches the Oracle integration method and required freshness.

Instructions in Martini

  • Use a REST or SOAP API workflow for transactional requests
  • Use a scheduler for polling, extracts, and reconciliation
  • Use a supported event or Atom-feed notification only for confirmed resource coverage

Objective

Retrieve current Oracle HCM resources or receive and validate HCM files before processing.

Instructions in Martini

  • Use supported filters, effective dates, and pagination
  • Capture Oracle request identifiers and synchronization watermarks
  • Treat HCM Extract and HDL files as immutable inputs and prevent duplicate ingestion

Objective

Coordinate Oracle calls, dependent reference data, transformations, target writes, and asynchronous processing.

Instructions in Martini

  • Sequence Jobs, Departments, Locations, Workers, and Assignments when dependencies require it
  • Poll asynchronous or bulk operations until a terminal status is available
  • Separate technical transfer completion from business import completion

Objective

Convert Oracle REST, SOAP, extract, or HDL structures into canonical and target-specific models.

Instructions in Martini

  • Map stable Oracle identifiers rather than display names
  • Handle XML, JSON, CSV, or other documented file structures
  • Preserve effective dates, external identifiers, and source lineage

Objective

Apply workforce lifecycle, authorization, reference-data, and effective-date rules before committing changes.

Instructions in Martini

  • Validate required Jobs, Positions, Departments, Locations, and legal-employer references
  • Route hires, movers, and leavers according to business policy
  • Reject validation and business-rule failures without blindly retrying them

Common Oracle HCM Cloud data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
WorkersSynchronize current and future workforce information, employment status, and lifecycle changes.Microsoft Entra ID, ServiceNow, Salesforce, data warehousesMartini retrieves filtered and paginated resources, applies effective-date and security rules, maps stable identifiers, and writes idempotent target updates.
PersonsExchange person identity and demographic information used by downstream workforce and identity processes.Microsoft Entra ID, ServiceNow, Salesforce, reporting platformsMartini maps permitted attributes to a canonical person model and preserves Oracle identifiers and synchronization watermarks.
Work RelationshipsRepresent the relationship between a person and an employer or employment context.Identity platforms, payroll processes, ServiceNow, reporting platformsMartini validates relationship status and dates, handles effective-dated changes, and routes only authorized populations.
AssignmentsSynchronize job, department, manager, location, status, and assignment-level organizational information.Salesforce, ServiceNow, Oracle ERP Cloud, identity platformsMartini resolves reference-data dependencies, handles future-dated slices, and applies business rules before target updates.
DepartmentsDistribute organizational structures and cost-center-related reference data.Oracle ERP Cloud, NetSuite, Salesforce, data warehousesMartini synchronizes changes with stable identifiers, validates parent or reference relationships, and manages ownership rules.
JobsProvide job and role reference data for workforce, access, reporting, and organizational integrations.Identity platforms, ServiceNow, Oracle ERP Cloud, reporting platformsMartini treats Jobs as reference data, validates dependent assignments, and stages changes before dependent transactions.

Authentication and security considerations

Authentication and authorization

Oracle HCM Cloud integrations may use OAuth 2.0 or Basic Authentication depending on the endpoint, tenant configuration, and security policy. Selected file-transfer arrangements may use certificate or key-based security, but this should not be generalized to every HCM REST resource.

Authentication does not by itself provide access to HCM data. The Oracle integration user requires appropriate job roles, duty roles, data roles, security profiles, and OAuth scopes for the required objects and populations.

  • Store credentials, tokens, and environment values in Martini secrets or secure configuration.
  • Use HTTPS or Oracle-supported secure transfer channels.
  • Validate access to Workers, Assignments, organizational structures, and any payroll data before production use.
  • Apply least-privilege access and review role changes after Oracle quarterly updates.

Operational considerations for Oracle HCM Cloud integrations

Design for Oracle HCM Cloud operating conditions

  • Handle REST pagination and bounded batch sizes for Workers, Assignments, and collection resources.
  • Define whether current, future-dated, historical, or all effective-dated slices are required.
  • Use bounded concurrency, backoff, and retry policies for throttling and transient 5xx responses.
  • Use Oracle identifiers, HDL keys, or external identifiers to prevent duplicate updates.
  • Distinguish transport, authorization, payload, business-rule, and row-level bulk errors.
  • Capture Oracle request IDs, correlation identifiers, import statuses, and error files where available.
  • Test mappings against a representative Oracle pod and review them for quarterly release changes.
  • Validate reference data such as Jobs, Positions, Departments, Locations, Legal Employers, and Business Units before dependent transactions.
  • Keep attachment and binary processing separate from ordinary JSON synchronization and verify resource-specific support.

Why use Martini instead of scripts or point-to-point integrations?

Centralize integration behavior

Scripts and point-to-point integrations often duplicate authentication, pagination, mapping, retry, and monitoring logic. Martini provides a maintainable workflow layer for orchestrating Oracle HCM APIs, SOAP services, files, notifications, and downstream applications.

  • Build reusable workflows and APIs around Oracle HCM integration patterns.
  • Apply consistent mapping, validation, effective-date, and business-rule handling.
  • Coordinate synchronous, scheduled, event-driven, bulk, and asynchronous processing.
  • Centralize error handling, retries, checkpoints, monitoring, and operational logging.
  • Expose controlled canonical APIs so downstream applications do not depend directly on Oracle-specific payloads.
  • Extend integration logic with custom code when documented endpoint behavior requires additional flexibility.

Frequently asked questions

How can Oracle HCM Cloud be integrated with enterprise systems?

Oracle HCM Cloud can integrate through REST APIs, selected SOAP services, HCM Extracts, Oracle HCM Data Loader files, and selected event or Atom-feed notification patterns. REST is generally preferred for supported transactional resources, while files and bulk processing are appropriate for high-volume or scheduled exchanges.

Can Martini integrate with Oracle HCM Cloud?

Yes. Martini can integrate with Oracle HCM Cloud by consuming its REST and SOAP APIs, processing HCM Extract and HDL files, coordinating selected Oracle notifications, and orchestrating scheduled workflows. No native Martini Oracle HCM Cloud connector is verified in the supplied documentation.

Do I need a connector to integrate Oracle HCM Cloud with Martini?

No. A dedicated Oracle HCM Cloud connector is not required. Martini can use Oracle's confirmed REST APIs, SOAP services, file-based integrations, authentication methods, and selected notification mechanisms through workflows and APIs.

Is there any extra Lonti cost to integrate Oracle HCM Cloud with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle HCM Cloud. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment choices.

Which Oracle HCM Cloud integration method should a new project use?

Use REST APIs for supported transactional resources and modern resource-oriented integrations. Use SOAP when Oracle documents the required operation through SOAP or an existing service contract must be retained. Use HCM Extracts and HDL for scheduled or bulk file processing.

Does Oracle HCM Cloud support webhooks or events for employee changes?

Oracle HCM Cloud supports selected event and Atom-feed notification patterns, but coverage varies by resource and event. It should not be treated as a universal webhook facility. Martini can supplement notifications with scheduled REST polling, effective-date queries, or HCM Extracts.

How does Martini synchronize changed Workers or Assignments?

Martini can use Oracle-supported filters, pagination, timestamps, effective dates, selected Atom feeds, or incremental HCM Extracts. The workflow stores a synchronization watermark only after the complete process succeeds and uses stable identifiers to make downstream updates idempotent.

Can Martini expose a simplified API over Oracle HCM Cloud?

Yes. Martini can expose a REST API that accepts a canonical request, invokes one or more Oracle HCM REST or SOAP operations, applies mapping and business rules, and returns a controlled response without exposing Oracle-specific structures to every consumer.

Related Martini documentation

API Consumption

Workflows

Security

Operations

Build a maintainable Oracle HCM Cloud integration

Use Martini to connect Oracle HCM Cloud APIs, files, notifications, and bulk processes to the systems that depend on workforce data. Design secure workflows with reusable mappings, business rules, retries, and operational visibility.

EXPLORE MARTINI
BOOK A DEMO