Platform access level: Org Admins
Connecting Oracle HCM to Arist keeps your learner roster current without anyone exporting a file. New hires, profile changes, and departures flow into Arist on a daily schedule, so the right people are always reachable for training. This guide covers the inbound worker sync and is written for the IT and Oracle administrators who set it up.
1. Oracle HCM connection overview
Arist reads worker data from Oracle Fusion through Workato, using the Oracle Fusion Cloud connector with Basic authentication against the Oracle HCM REST API, version 11.13.18.05. The access is read-only, and the sync runs daily. Arist and Oracle never call each other directly, since Workato brokers every request.
Note: Reporting Arist course completions back to Oracle Learning is a separate outbound flow, covered under Related articles.
2. Worker data Arist reads
Arist reads each worker through the expanded Workers endpoint, which returns the worker and its child records in one call rather than many. A typical read expands names, emails, work relationships, assignments, assignment flexfields, and managers.
Purpose | Endpoint |
Worker and HRIS metadata |
|
Human-readable job details |
|
The Workers endpoint provides most fields directly. Job code comes from the worker's assignment, and the human-readable job name, job function, and sub-function are looked up from the Jobs and Jobs LOV endpoints, which is why those need their own access.
3. Field mapping
Arist maps Oracle worker fields to the learner record it builds. The table shows the common mapping, though your exact fields are confirmed during setup.
Arist field | Oracle source | Notes |
Person Number (Employee ID) | PersonNumber | The stable identifier used to match each learner |
First name | names.FirstName | |
Last name | names.LastName | |
Work email | emails.EmailAddress where PrimaryFlag is true | Work email only, the Oracle work email type |
Business title | workRelationships.assignments.AssignmentName | |
Employee type | workRelationships.WorkerType | |
Hire date | workRelationships.StartDate | |
Assignment status | workRelationships.assignments.AssignmentStatusType | |
Termination date | workRelationships.TerminationDate | Drives when a learner is deactivated |
Job details | workRelationships.assignments.JobCode, resolved through Jobs and Jobs LOV | Job code, name, function, and sub-function as separate fields |
Location or country | workRelationships.LegislationCode | |
Manager Person Number | workRelationships.assignments.managers.ManagerAssignmentNumber | Arist strips the leading E and any suffix to get the manager's Person Number |
Custom fields | workRelationships.assignments.assignmentsDFF | Client-specific flexfields, for example a business tier or market area |
4. Who Arist syncs
Not every worker in Oracle should become a learner, so Arist filters the feed. Confirm each rule below against your workforce during setup.
Employees only: Arist includes employees and excludes contingent workers and contractors.
Primary assignment: When a worker holds more than one assignment, Arist uses the primary one.
Active plus recently departed: Arist includes active employees, plus employees terminated within roughly the last 30 days, so a departure syncs once more to deactivate the learner.
Work email present: Arist can require a work email, so workers without one are left out until an address is added.
Note: A worker sent before their work email is populated cannot be reached and is filtered out until the email is added on a later sync. Decide whether records are sent only once complete, or sent early and expected to become reachable later, and agree the acceptable lag.
5. Credentials your IT team provides
Your IT team provisions a read-only API service account and shares the values below with Arist through a secure channel.
Item | What it is |
Subdomain | The host of your Oracle Fusion environment, for example |
Username | The API service account Arist authenticates as, using Basic authentication |
Password | The service account password, shared securely |
Worker access | Read-only access to Worker Details and Worker Employment Details |
Job access | Read access to the Jobs and Jobs LOV endpoints, if you want human-readable job details |
Important: Grant read-only access scoped to the worker and job resources above. The integration never needs write access to Oracle HCM.
6. Matching learners on a stable identifier
Arist matches each learner on the Oracle Person Number, which is the Employee ID and survives job changes, transfers, and rehires. This is also the identifier that ties a learner to their Oracle Learning completions, so keeping it consistent is what lets the completion writeback land on the right record.
If another system such as Teams also provisions learners into Arist, agree which identifier each source keys on, so the same person is never created twice.
Related articles
LMS Integration - Oracle
Arist and Oracle - Technical Guide
HRIS Data Preparation
Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].
