> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/application/oracle-fusion-cloud-hcm.md).

# Oracle Fusion Cloud HCM

This article outlines the integration with the Oracle Fusion Cloud HCM connector, enabling streamlined metadata management through features such as crawling, manual lineage, and data preview. The connector extracts metadata from Oracle Fusion Cloud HCM resources, including schemas, tables, columns, and hierarchical relationships, providing comprehensive visibility into HCM data assets and their structure.

The connector establishes connectivity through the Oracle Fusion Cloud HCM REST API (HTTPS) using Basic Authentication. It authenticates using a dedicated Oracle Fusion Cloud HCM service account with the required REST API permissions to validate the connection, crawl metadata, retrieve sample data, and perform related connector operations. 

<div align="left"><img src="/files/RvqhJQ9jjpgZZFg1Jlaj" alt="" height="319" width="624"></div>

## Overview

### Connector Details

| Connector Category                                                                          | Application                                                              |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| OvalEdge Release Supported                                                                  | Release6.3.4 and later                                                   |
| <p>Connectivity</p><p>\[How the connection is established with Oracle Fusion Cloud HCM]</p> | Oracle HCM REST API (HTTPS) using Basic Authentication via OkHttp client |
| Verified Oracle Fusion Cloud HCM Version                                                    | Oracle Fusion Cloud HCM (REST API resources v11.13.18.05 and /latest/)   |

{% hint style="info" %}
The Oracle Fusion Cloud HCM connector has been validated with the mentioned "Verified Oracle Fusion Cloud HCM Version" and is expected to be compatible with other supported Oracle Fusion Cloud HCM versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### Connector Features

<table data-search="false"><thead><tr><th>Feature</th><th align="center">Availability</th></tr></thead><tbody><tr><td>Crawling</td><td align="center">✅</td></tr><tr><td>Delta Crawling</td><td align="center">❌</td></tr><tr><td>Profiling</td><td align="center">❌</td></tr><tr><td>Sample Profiling</td><td align="center">✅</td></tr><tr><td>Query Sheet</td><td align="center">❌</td></tr><tr><td>Data Preview</td><td align="center">✅</td></tr><tr><td>Auto Lineage</td><td align="center">❌</td></tr><tr><td>Manual Lineage</td><td align="center">✅</td></tr><tr><td>Secure Authentication via Credential Manager</td><td align="center">✅</td></tr><tr><td>Data Quality</td><td align="center">❌</td></tr><tr><td>DAM (Data Access Management)</td><td align="center">❌</td></tr><tr><td>Bridge</td><td align="center">✅</td></tr></tbody></table>

### Metadata Mapping

The following objects are crawled from Oracle Fusion Cloud HCM and mapped to the corresponding UI assets.

<table data-search="false"><thead><tr><th width="128">Oracle Fusion Cloud HCM Object</th><th width="199">Oracle Fusion Cloud HCM Attribute</th><th>OvalEdge Attribute</th><th>OvalEdge Category</th><th>OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>OracleFusionHCM (fixed)</td><td>Schema</td><td>Databases</td><td>Schema</td></tr><tr><td>Table</td><td>Resources.{resourceName} key</td><td>Table</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Type = TABLE</td><td>Type</td><td>Tables</td><td>Table</td></tr><tr><td>Columns</td><td>Children (nested resources)</td><td>Sub-table (parent.child)</td><td>Tables</td><td>Table</td></tr><tr><td>Columns</td><td>attributes[].name</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>attributes[].title</td><td>Source Description / Title</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>attributes[].type</td><td>Column Type</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>attributes[].maxLength</td><td>Data Type Size</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>attributes[].required</td><td>Nullable (inverted)</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>ColumnPosition (sequential)</td><td>Column Position</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Self column (tablename)</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>Relationship</td><td>children hierarchy + tableId</td><td>Parent-Child Column Relation</td><td>Relationships</td><td>-</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection:

### Service Account User Permissions

{% hint style="info" %}
Use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
👨‍💻Who can provide these permissions? The Oracle Fusion Cloud HCM administrator grants these permissions, as users may not have the required access to assign them independently.
{% endhint %}

| Operations      | System Tables / Objects                   | Permissions |
| --------------- | ----------------------------------------- | ----------- |
| REST API Access | Oracle HCM REST API                       | GET         |
| REST API Access | hcmRestApi/resources/11.13.18.05/describe | GET         |
| Data/Profiling  | hcmRestApi/resources/latest/{resource}    | GET         |
| Data/Profiling  | Basic Auth                                | GET         |

## Connection Configuration Steps

{% hint style="info" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log into OvalEdge, go to Administration > Connectors, click + **(New Connector)**, search for **Oracle Fusion Cloud HCM**, and complete the required parameters.

   **Note**: Fields marked with an asterisk (\*) are mandatory for establishing a connection.

<table><thead><tr><th width="218">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Oracle Fusion Cloud HCM (Human Capital Management)" is displayed as the selected connector type.</td></tr></tbody></table>

**Connector Settings**

<table data-header-hidden data-search="false"><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>Connector Name*</td><td>Enter a unique name for the Oracle Fusion Cloud HCM connection (Example: "OracleFusionCloudHCM_Prod").</td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.<br><br>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>End Point*</td><td>Enter the Oracle Fusion Cloud HCM service endpoint URL to be accessed by the connector.</td></tr><tr><td>Username*</td><td>Enter the username of the Oracle Fusion Cloud HCM account used to authenticate the connector. </td></tr><tr><td>Password*</td><td>Enter the password associated with the Oracle Fusion Cloud HCM user account used for the connection. </td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to enable proxy settings or No to connect directly without a proxy.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="219"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>Select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl/Profile

{% hint style="info" %}
To perform crawl/profile operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling and profiling.

1. Navigate to the **Connectors page** and click **Crawl/Profile**.
2. Select the schemas to be crawled.
3. The **Crawl** option is selected by default. To perform both operations, select the **Crawl & Profile** radio button.
4. Click **Run** to collect metadata from the connected source and load it into the Data Catalog.
5. After a successful crawl, the information appears in the **Data Catalog > Databases** tab.

The **Schedule** checkbox allows automated crawling and profiling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the **Select Period** drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the selected operation (**Crawl** or **Crawl & Profile**) at the scheduled time.

### Other Operations

The **Connectors page** in OvalEdge provides a centralized view of all configured connectors, including their health status.

**Managing connectors includes**:

* **Connector Health**: Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including databases, tables, columns, and views.

**Nine Dots Menu Options**:

To view, edit, validate, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the connection's integrity.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Profiler**: Customize data profiling rules and methods.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table data-search="false"><thead><tr><th width="85">S.No.</th><th width="219">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Failed to authenticate with Oracle Fusion HCM. </td><td><p>Error Description: The Oracle Fusion Cloud HCM connector cannot establish a connection because authentication with the Oracle Fusion HCM service failed. This issue is typically caused by incorrect endpoint details, invalid credentials, or insufficient API access permissions.</p><p><br>Resolution:</p><ul><li>Verify that the endpoint URL is correct (https://&#x3C;pod>.fa.&#x3C;dc>.oraclecloud.com).</li><li>Confirm that the configured username and password are valid.</li><li>Ensure that the user account has the required Oracle Fusion HCM REST API access permissions.</li><li>Test the endpoint GET {endpoint}/hcmRestApi/resources/11.13.18.05 and verify that it returns an HTTP 200 response.</li><li>Retry the connection after validating the endpoint, credentials, and API access permissions.</li></ul></td></tr><tr><td>2</td><td>Failed to get API response / Connection timeout </td><td><p>Error Description: The Oracle Fusion Cloud HCM connector fails to establish a connection because the API request does not receive a response within the expected time. This issue may occur due to blocked network access, proxy configuration issues, or connectivity problems between the application and Oracle Cloud.</p><p></p><p>Resolution:</p><ul><li>Ensure that port 443 (HTTPS) is open and whitelisted for outbound communication.</li><li>Verify Bridge connectivity to the Oracle Fusion Cloud environment if the connector is using Bridge.</li><li>Validate that the proxy settings are correctly configured when IS_PROXY_ENABLED is enabled.</li><li>Confirm that the Oracle Fusion Cloud endpoint is reachable from the application environment.</li><li>Retry the connection after verifying the network, proxy, and Bridge configuration.</li></ul></td></tr><tr><td>3</td><td>Error getting remote tables </td><td><p>Error Description: The Oracle Fusion Cloud HCM connector failed to retrieve the list of remote tables. This issue occurs when the service account lacks the required API permissions or when the configured API version is unsupported.</p><p></p><p>Resolution:</p><ul><li>Verify that the service account has permission to access the /hcmRestApi/resources/11.13.18.05/describe endpoint.</li><li>Confirm that the configured Oracle Fusion Cloud HCM REST API version (11.13.18.05) is supported and matches the target environment.</li><li>Validate that the REST API endpoint URL is correct and accessible.</li><li>Ensure that the configured credentials are valid and have the required privileges.</li><li>Retry the connection after verifying the API permissions and version compatibility.</li></ul></td></tr><tr><td>4</td><td>Error getting first N rows/sample profiling failure </td><td><p>Error Description: The Oracle Fusion Cloud HCM connector fails to retrieve sample records during profiling because the configured user lacks sufficient access to the HCM resource, or the requested nested fields are invalid. As a result, sample profiling cannot be completed.</p><p></p><p>Resolution:</p><ul><li>Verify that the configured user has read access to the required HCM resource using the /hcmRestApi/resources/latest/{resource} endpoint.</li><li>Confirm that the specified resource name is valid and available in the Oracle Fusion Cloud HCM environment.</li><li>For child or sub-tables, ensure that the nested fields parameter is correctly configured and supported.</li><li>Validate that the configured credentials have the required permissions to access the resource.</li><li>Retry the sample profiling operation after updating the resource access and nested field configuration.</li></ul></td></tr><tr><td>5</td><td>No columns returned for table </td><td><p>Error Description: The Oracle Fusion Cloud HCM Connector could not retrieve column metadata for the selected table. This issue may occur when the cached table metadata is unavailable or has not been populated during a previous crawl.</p><p></p><p>Resolution:</p><ul><li>Re-crawl the Oracle Fusion Cloud HCM connection to refresh the metadata.</li><li>Ensure that the table crawl completes successfully before performing column-level operations.</li><li>Verify that the connector has the required permissions to access the table metadata.</li><li>Confirm that the target table exists and contains column definitions.</li><li>Retry the operation after the crawl refreshes the cached metadata.</li></ul></td></tr><tr><td>6</td><td>Generic Errors </td><td><p>Error Description: The Oracle Fusion Cloud HCM Connector encountered an unexpected error during connection validation or metadata retrieval. The error details are not displayed in the application, so the root cause must be identified by analyzing the logs.</p><p></p><p>Resolution:</p><ul><li>Review the OvalEdge application logs for OracleFusionHCMDto error entries.</li><li>Identify the corresponding error using the connection ID and timestamp.</li><li>Verify that the Oracle Fusion Cloud HCM connection details and credentials are correct.</li><li>Ensure that the Oracle Fusion Cloud HCM service is accessible and responding.</li><li>Contact OvalEdge Support and provide the connection ID, timestamp, and relevant log entries for further investigation.</li></ul></td></tr></tbody></table>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/application/oracle-fusion-cloud-hcm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.