---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Oracle HCM (Discovery)

# Oracle HCM (Discovery) {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Oracle HCM (Discovery) connector enables access to human capital management data from your Oracle HCM account without moving or copying data. Available tables and columns are discovered at runtime.

Connection admins set up connections to Oracle HCM (Discovery) in the Zero Copy Connector Hub and grant data stewards access. Data stewards use the connection to create data fabric tables and map data from Oracle HCM. Users can then access Oracle HCM data through the table list view or GlideRecord
scripts. For details, see [Managing data fabric tables](https://www.servicenow.com/docs/LoGgZ20y7DmSjp0sb8uhug "Access data virtually from an external source or a local table on your instance using data fabric tables.").{#oracle-hcm-discovery-zcc__oracle-hcm-discovery-zcc-para-1}  
Note:  
Oracle HCM (Discovery) is a REST connector. Before you set up this connection, review [REST connectors](https://www.servicenow.com/docs/8PpL6y3foWFZUQhTXYKEsQ "REST connectors use APIs, instead of JDBC, to retrieve data and metadata from an external source.") for prerequisites, authentication requirements, and API consumption considerations.{#oracle-hcm-discovery-zcc__oracle-hcm-discovery-zcc-para-2}

## Supported data types {#oracle-hcm-discovery-zcc__section_oraclehcmdiscovery_datatypes}

{#oracle-hcm-discovery-zcc__table_oracle_hcm_discovery_datatypes__entry__2}

| Oracle HCM (Discovery) | Data fabric table |
|-|-|
| varchar | String |
| bigint | Long |
| boolean | True/False |
| double | Floating Point Number |
| date | Date |
| timestamp (3) | Basic Date/Time |
[Table 1. Data type mapping]

{#oracle-hcm-discovery-zcc__table_oracle_hcm_discovery_datatypes}

## How Oracle HCM (Discovery) differs from Oracle HCM {#oracle-hcm-discovery-zcc__section_oraclehcmdiscovery_how}

Because Oracle HCM instances can have custom tables and column definitions, this connector does not rely solely on a fixed, built-in set of tables. Instead, it queries your Oracle HCM instance at
runtime to discover which tables and columns are available. This is similar to how a JDBC-based connector discovers schema information from a database. Discovered metadata is cached to avoid repeating this discovery process for every
query.{#oracle-hcm-discovery-zcc__oracle-hcm-discovery-zcc-para-3}  
Note:  
Oracle HCM (Discovery) is a separate connector from Oracle HCM. Choose Oracle HCM (Discovery) if you want the connector to detect available tables and columns directly from your Oracle HCM instance. This approach does not rely on a fixed, built-in set of tables.{#oracle-hcm-discovery-zcc__oracle-hcm-discovery-zcc-para-4}
**Related tasks**   

* [Create an Oracle HCM (Discovery) connection](https://www.servicenow.com/docs/QzOVv88O5tM4wL4rtH3Jrg "Establish a zero copy connection to an external Oracle HCM account in Zero Copy Connector Hub.")  
**Related topics**   

*