Oracle Fusion Cloud Applications connection
Updated
info
This connector is currently in Early Access. Contact support for details.
Oracle Fusion Cloud Applications syncs Financials (ERP) and Supply Chain Management (SCM) data from your Fusion pod's REST API — AP invoices, GL journals and ledger balances, AR invoices, suppliers, and item costs — into your data warehouse.
Prerequisite
You need a dedicated Fusion integration user with HTTP Basic credentials, and your pod's base REST API URL.
Authentication methods
You use HTTP Basic authentication when you create the connection:
- Integration user name and Integration user password: credentials for a dedicated Fusion integration user.
- Pod Base URL: the full REST API base URL for your pod, including the API version path.
Retrieving your credentials
- Have your Fusion administrator create (or designate) a dedicated integration user with HTTP Basic access and the duty roles needed for the modules you want to sync (Financials, and Procurement/Supplier Model for supplier data).
- Confirm the integration user's Data Access Set includes every ledger you want to report on — GL reports return zero rows for any ledger outside it.
- Find your pod's base REST API URL from your Fusion REST API documentation (Setup and Maintenance > REST API documentation, or your Oracle-provided environment details) — it looks like
https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05. You need the full URL through the API version path, not just the hostname.
Connecting Oracle Fusion to Data Integration
- Navigate to the Data Integration console.
- Select Connections, then select + New Connection.
- Search for and select Oracle Fusion Cloud Applications as the connection type.
- Enter a Connection Name to identify this connection.
- Enter your Integration user name.
- Enter your Integration user password.
- Enter your Pod Base URL — the full URL through the API version path, for example
https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05. - Select Test Connection to confirm Data Integration can authenticate and reach your pod.
- Select Save to finish creating the connection.
Known limitations
- Pod Base URL is a plain text field — enter the full URL exactly as it appears in your Fusion REST API documentation, including the API version path. There's no picker, since this value is specific to your own pod.
- Data returned is scoped by the integration user's Data Access Set and duty roles. If a GL report returns zero rows, confirm the integration user has a Data Access Set assigned that includes the ledger(s) you expect.
- GL Ledger Balances requires selecting at least one ledger and one accounting period — it has no incremental field, so balances are re-pulled for every selected ledger/period combination on each run.
If you need a report or object that isn't currently supported, contact support so it can be evaluated for a future release.