Skip to main content

Arist and Oracle - Technical Guide

The technical reference for the Oracle integration, covering both directions: how Arist reads worker data from Oracle Fusion to create and target learners, and how Arist reports course completions back to Oracle Learning.

Platform access level: Org Admins


This guide is the technical reference for the Oracle integration. It covers both directions: how Arist reads worker data from Oracle Fusion to create and target learners, and how Arist reports course completions back to Oracle Learning. It is written for the IT and Oracle administrators who provision access and connect the two systems.


1. Integration overview

The Oracle integration uses two different mechanisms, one per direction, because Oracle reads and Oracle learning-record loads use different interfaces.

  • Inbound worker sync: Arist reads workers from the Oracle HCM REST API through Workato, using the Oracle Fusion Cloud connector with Basic authentication. The access is read-only and the sync runs daily.

  • Outbound completions: Arist reports completions to Oracle Learning as an HCM Data Loader (HDL) file, delivered over SFTP or loaded through Oracle WebCenter Content, rather than through a live API write.

Arist does not publish course content into Oracle. Completions reference courses that already exist in Oracle Learning.


2. Reading worker data

Arist reads each worker through the expanded Workers endpoint, which returns the worker and its child records in a single call. Job details are resolved through the Jobs endpoints.

Purpose

Endpoint

Worker and HRIS metadata

GET /hcmRestApi/resources/11.13.18.05/workers expanded across names, emails, workRelationships.assignments, assignmentsDFF, and managers

Human-readable job details

GET /hcmRestApi/resources/11.13.18.05/jobs and /jobsLov


3. Mapping Oracle fields to Arist fields

The common field mapping is below. Your exact fields are confirmed during setup.

Arist field

Oracle source

Person Number (Employee ID)

PersonNumber

First and last name

names.FirstName, names.LastName

Work email

emails.EmailAddress where PrimaryFlag is true

Business title

workRelationships.assignments.AssignmentName

Employee type

workRelationships.WorkerType

Hire date and termination date

workRelationships.StartDate, workRelationships.TerminationDate

Assignment status

workRelationships.assignments.AssignmentStatusType

Job details

workRelationships.assignments.JobCode, resolved through Jobs and Jobs LOV

Location or country

workRelationships.LegislationCode

Manager Person Number

workRelationships.assignments.managers.ManagerAssignmentNumber, with the leading E and any suffix stripped

Custom fields

workRelationships.assignments.assignmentsDFF


4. Determining who Arist syncs

Arist filters the worker feed so only the intended population becomes learners. Confirm each rule against your workforce.

  • Employees only, excluding contingent workers and contractors.

  • The primary assignment, when a worker holds more than one.

  • Active employees plus those terminated within roughly the last 30 days, so a departure syncs once more to deactivate the learner.

  • Workers with a work email, since a record without one cannot be reached and is filtered out until an address is added.

Arist matches each learner on the Person Number, which is the Employee ID and survives job changes, transfers, and rehires. It is also the key that ties a learner to their Oracle Learning completions.


5. Reporting completions to Oracle

When a learner completes a course in Arist, Arist records it in Oracle Learning as a learning record on the worker, reporting status as Not Started, In Progress, or Completed. The completion is produced as an HDL file, the format Oracle's HCM Data Loader uses to load learning records in bulk.

Two matches must line up first: every course reported on exists in Oracle Learning with a course number that matches the course's Arist External ID, and each learner's Oracle Person Number matches their Arist User ID.

Arist can deliver the file two ways, chosen by how much Oracle access your security team grants.

  • File drop to your SFTP (recommended): Arist builds, compresses, and encrypts the file and places it on an SFTP location you provide. Your team runs HCM Data Loader to import it. This needs only SFTP write access and your encryption key.

  • Automated load through REST and UCM: Arist uploads the file to Oracle WebCenter Content (UCM) and initiates and monitors the load through the dataLoadDataSets REST resource. This removes the client-side import but requires elevated access: permission to run HCM Data Loader, REST access to trigger and monitor loads, write access to the UCM staging location, and rights to manage learning records.


6. Fields in the completion file

Each completion record carries the fields below. Arist populates the learner, course, and dates from the completion and sends the Oracle constants as fixed values.

Field

Value or source

Notes

LearnerNumber

The learner's Oracle Person Number

Matches the learner to their worker record

LearningItemNumber

The Oracle course number

Must match the course's Arist External ID

LearningItemType

ORA_COURSE

Sent as a constant

AssignmentType

ORA_REQUIRE_ASSIGNMENT

Sent as a constant

AssignmentAttributionType

ORA_PERSON

Oracle accepts ORA_PERSON or ORA_SPECIALIST; Arist sends ORA_PERSON

AssignmentSubType

ORA_EVT_SUBT_ADMIN

Sent as a constant

AssignedByPersonNumber

Person Number of whoever assigned the course

Optional

LearningRecordValidFromDate

The learning item start date

Optional

LearningRecordCompletionDate

The completion date

Set when the status is Completed

LearningRecordExpiryDate

The learning item expiry or end date

Optional


7. File format and delivery

Oracle's HCM Data Loader is strict about the file, so Arist builds it to these rules and delivers it encrypted.

  • Dates use the format YYYY/MM/DD, and no special characters appear in any field.

  • The completion data is a .dat file named to the HDL specification, compressed into a .zip archive.

  • Arist encrypts the archive with your PGP public key before placing it on your SFTP.

For the SFTP file drop, your team provides the hostname, the port (typically 22), the account credential (a password or SSH key), and a PGP public key for encryption. Arist writes the file on a schedule, and your team collects it and runs the import.


8. Access and security

The two directions need different access, and both are kept to the least the integration requires.

  • Inbound: A read-only Basic-auth API service account with access to Worker Details and Worker Employment Details, plus the Jobs and Jobs LOV endpoints if human-readable job details are needed. Arist connects to your Oracle Fusion subdomain over the REST API.

  • Outbound, file drop: SFTP write access and your PGP public key. No Oracle API write access is required, since your team runs the load.

  • Outbound, automated load: The elevated Oracle access listed in section 4, only if you choose the automated path.

Traffic is encrypted in transit, credentials are shared through a secure channel and never over email or chat, and the completion file is PGP-encrypted before it leaves Arist.


Related articles

  • HRIS Integration - Oracle

  • LMS Integration - Oracle

  • HRIS Data Preparation

Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].

Did this answer your question?