OIIdentity and access management
Oracle HCM to One Identity integration: Oracle HCM Cloud as the HR source for One Identity Manager
An integration between Oracle HCM Cloud and One Identity Manager turns every employee in Oracle into a Person in One Identity Manager, with legal employer, department, job and manager from the primary work relationship. One Identity has an Oracle Fusion Cloud connector in Starling Connect, but no ready-made HR template for Oracle; KoppelHet builds the mapping to Person and Department and monitors the synchronisation.
What the integration does
Organisations that use Oracle HCM Cloud worldwide and One Identity Manager for accounts and permissions look in vain for Oracle among One Identity's Cloud HR templates. Those exist for SuccessFactors, Workday and Dayforce. Without a template it remains a monthly export, and a transfer to another legal employer only reaches One Identity Manager weeks later.
- In Oracle we create an integration user with read-only rights on workers, work relationships and assignments.
- In Starling Connect we configure the Oracle Fusion Cloud connector with a SCIM endpoint for employees, including future hires.
- In the Synchronization Editor we build a custom mapping from the Employees endpoint to Person and Department.
- We filter on the primary, active work relationship and assignment, so every person has one source.
- After each run KoppelHet compares the number of persons and the end dates with Oracle and reports deviations.
What to watch for with Oracle HCM Cloud and One Identity
- One Identity Manager's Cloud HR Systems module has templates for SuccessFactors, Workday and Dayforce, not for Oracle. Starling Connect does have an Oracle Fusion Cloud connector, originally meant for accounts and roles in Oracle and later extended with employees. Without a template KoppelHet builds the mapping to Person and Department itself in the Synchronization Editor.
- In Oracle an employee has one or more work relationships, each with its own assignments. Since December 2025 the Starling connector can select work relationships and assignments on active status and the primary flag. KoppelHet enables that selection, so One Identity Manager gets exactly one department and job per person instead of a random one.
- Since 2024 Starling Connect has a separate endpoint for future employees in Oracle. A hire with a start date three weeks out is already fixed in Oracle, but does not yet belong in One Identity Manager as an active Person with permissions. KoppelHet includes those employees with their start date, so accounts are ready but only get permissions on the first working day.
- Oracle has a separate event for a cancelled work relationship, for example when a candidate drops out before the start. In One Identity Manager such a person would otherwise remain as a leaver with history. KoppelHet marks that Person as never started, so the administrator can clean it up without the audit trail of a real departure.
- In an early version of Starling's Oracle connector the userID was not mapped in the employee schema; One Identity has fixed that. Still KoppelHet ties Person to the PersonNumber and not to the Oracle username, because an employee without an Oracle login would otherwise have no key.
- Oracle can have several types of managers per assignment, such as a line manager and a project manager. One Identity Manager uses the manager for approvals and attestations. KoppelHet only takes the line manager of the primary assignment, so an attestation does not land with a temporary project lead.
- The Starling connector has supported custom fields from Oracle, such as a flexfield for contract type, since February 2026. Such fields must be in Starling's SCIM schema before the Synchronization Editor sees them. KoppelHet reloads the schema after each change on the Oracle side and only then adjusts the mapping.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Can it be done without Starling Connect?
Yes. KoppelHet then prepares the data from Oracle as a file and One Identity Manager reads it with the CSV connector.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Starling Connect Oracle Fusion Cloud connector (since December 2021): Employees endpoint with update employee (2022), extra attributes, Future dated Employees endpoint and filtering on all endpoints (2024), selection of workrelations and workAssignments on active status and primary flag (December 2025), custom attributes (February 2026); also roles, role membership and data security records (beta).
- One Identity Manager: synchronisation project with the SCIM connector to the Starling endpoint (Cloud HR Systems module for non-standard SCIM object types; the CSM and UCI modules only process Users, Groups and Roles), custom mapping to Person and Department. Oracle side: workers with workRelationships, assignments and managers, Atom feeds newhire, empassignment, termination and cancelworkrelship for checks.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in One Identity | Notes |
|---|---|---|
PersonNumber | PersonnelNumber | Fixed key, also on transfer |
KnownAs of FirstName, LastName | FirstName, LastName | |
DepartmentName (primaire assignment) | Department | |
LegalEmployerName | Bedrijf (eigen kolom) | |
JobName en LocationName | Functie en Locality | |
Lijnmanager (managers) | Manager van de Person | |
WorkerType | IsExternal | Contingent worker as external |
StartDate en TerminationDate (arbeidsrelatie) | EntryDate, ExitDate |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud