# Oracle HCM

<figure><img src="/files/P3BiUdiOo67dSdxj6KkQ" alt=""><figcaption></figcaption></figure>

### What you get

* **Live People directory** — Oracle HCM workers appear in Siit with their full role and org context.
* **Lifecycle triggers** — Hire date, Termination date, and Birthday flow into Siit as workflow triggers.
* **Organization awareness** — department, cost center, location, and legal entity hierarchies are preserved.
* **Manager resolution** — Oracle's reporting structure powers auto‑selected approvers.
* **Multi‑entity support** — legal entity, business unit, and region are synced and usable as workflow conditions.

### What syncs from Oracle HCM

| Category        | Fields                                                         |
| --------------- | -------------------------------------------------------------- |
| Identity        | Preferred name, legal name, work email, person number, user ID |
| Role            | Job title, job code, department, division                      |
| Org structure   | Manager, cost center, location, business unit, legal entity    |
| Employment      | Assignment type, employment status                             |
| Lifecycle dates | Hire date, termination date, date of birth                     |

Work email is the canonical identifier.

### Before you connect

Oracle HCM setup varies significantly by tenant configuration. You'll need:

* An Oracle HCM admin to create an integration user and grant the required REST API privileges.
* Your Oracle HCM REST API endpoint URL.
* Agreement with your Oracle administrator on the scope of data exposed to Siit.

For the recommended setup for your tenant, reach out to support via the in‑app chat — we'll work with you to scope and configure the connection correctly.

### Connect Oracle HCM

1. Have your Oracle admin create an integration user with REST API privileges to read worker data.
2. In Siit, go to **Settings → Integrations**, find **Oracle HCM** in the HRIS section, and click **Connect**.
3. Enter your REST API endpoint, integration user credentials, and any tenant-specific identifiers.
4. Review the imported workers and field mapping, then click **Finish setup**.

### After the connection

* Compare Siit's worker count with your Oracle HCM active worker report.
* In **Settings → People → Fields**, set Oracle HCM as the source of truth for org‑structure fields if you're also connected to an IdP.
* Build a Day‑1 onboarding workflow using the Hire date trigger.

### Sync frequency

Oracle HCM data refreshes every few hours by default. For very large tenants, the schedule is tuned based on worker count. Manual syncs are available from **Settings → Integrations → Oracle HCM → Sync now**.

### Common workflows

**Day‑1 onboarding.** *Trigger: Hire date. Actions: create IdP account, assign apps by department, ship equipment, DM manager.*

**Offboarding on termination.** *Trigger: Termination date. Actions: revoke sessions, remove app access, equipment pickup, notify manager.*

**Business unit‑aware approval.** *Condition: Requester's business unit → Route to the right regional approver.*

### Troubleshooting

**"401 Unauthorized" on connect.** The integration user password is wrong or the account has been locked. Reset and update Siit.

**Workers missing.** The integration user likely lacks REST privileges for a specific business unit or worker type. Ask your Oracle admin to extend the privilege scope.

**Sync is slow on a large tenant.** Reach out via in‑app chat — we can adjust the sync strategy for your tenant.

**Custom field missing.** Make sure the field is exposed via the relevant REST resource and the integration user has access, then re‑map in Siit.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.siit.io/integrations/hris/oracle-hcm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.