> ## Documentation Index
> Fetch the complete documentation index at: https://www.integrate.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# ETL: Oracle Fusion

> Configure the Oracle Fusion source in Integrate.io ETL to read invoices, suppliers, customer accounts, purchase orders, and workers from Oracle Fusion Cloud.

Use the Oracle Fusion source component to read data from Oracle Fusion Cloud Applications into your [Integrate.io](http://integrate.io/) ETL pipeline. The connector reads six objects from Fusion Financials, Procurement, CRM, and HCM through the Fusion REST API. All six objects support incremental loads on `LastUpdateDate`.

Use this component instead of exporting Fusion reports to CSV files and reading them from SFTP or cloud storage.

## Prerequisites

* An Oracle Fusion Cloud pod. The pod URL has the form `https://<pod>.fa.<region>.oraclecloud.com`.
* A Fusion user name and password with REST API access to the objects you want to read.

## Connection setup

Create an Oracle Fusion connection from **Connections → New connection**. Oracle Fusion is listed under **Services**.

| Field | Description |
| :- | :- |
| Name | Display name for the connection inside Integrate.io. |
| Fusion Pod URL | The address you use to sign in to Fusion, for example `https://acme.fa.us2.oraclecloud.com`. You can paste a full page URL from the Fusion UI. Integrate.io ignores any path after the host. |
| Username | Your Fusion user name. |
| Password | The password for that user. Integrate.io sends the user name and password with HTTP Basic authentication. |

The pod URL must meet these rules, or the connection does not save:

* It uses `https`.
* The host ends in `.fa.<region>.oraclecloud.com`. Custom (vanity) domains are not accepted.
* It does not include a port.

After you fill in the form, click **Test connection**. The test reads one record from the `suppliers` resource. A user without access to suppliers fails the test, even if the user can read other objects such as `workers`.

## Source properties

The source component is configured in Step 02 of the component editor.

### Source table (object)

Select the Oracle Fusion object to read data from:

| Object | Fusion REST resource | Incremental load |
| - | - | - |
| ap\_invoices | `fscmRestApi` `invoices` | Supported |
| ar\_invoices | `fscmRestApi` `receivablesInvoices` | Supported |
| suppliers | `fscmRestApi` `suppliers` | Supported |
| customer\_accounts | `crmRestApi` `accounts` | Supported |
| purchase\_orders | `fscmRestApi` `purchaseOrders` | Supported |
| workers | `hcmRestApi` `workers` | Supported |

Integrate.io reads resource version `11.13.18.05` and requests 500 records per page, sorted by `CreationDate`.

> [!NOTE]
>
> `customer_accounts` reads the CRM `accounts` resource. Your Fusion user needs access to CRM accounts to read this object.

### Load type

Select how records are loaded on each pipeline run:

* **Full Load.** Fetches all records for the selected object on every run.
* **Incremental Load.** Fetches only records updated after or before a reference date.

### Incremental load settings

When **Incremental Load** is selected, the following options appear:

**Sync date field.** Use `LastUpdateDate`. It is the only field Oracle Fusion filters on for this connector.

**Load records.** Choose `newer than` or `older than` the reference date.

**Reference date.** Choose the source of the date value:

* **Last successful run.** Loads records since the last successful run of this pipeline, using the `$_PACKAGE_LAST_SUCCESSFUL_JOB_SUBMISSION_TIMESTAMP` system variable. Recommended for scheduled pipelines.
* **Fixed Date.** Pick a specific calendar date.
* **Variable.** Use a custom package variable.

The component preview sends the filter to Fusion as a `q` expression:

```text theme={null}
q=LastUpdateDate>='2026-06-01T00:00:00Z'
```

> [!WARNING]
>
> Incremental jobs read every record of the object from Fusion and then keep the records that match the reference date. An incremental run reduces the rows written to your destination, not the number of API calls to Fusion.

## Source schema

After configuring the source properties, the **Schema** section (Step 03) displays the available fields with their detected data types. Use the field selector to choose which columns to include in your pipeline. You can rename fields with aliases and change data types as needed.

Nested JSON objects in Fusion responses are flattened into individual columns with underscore-separated names. Integrate.io requests `onlyData=true`, so the per-record `links` arrays are not included.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.