Skip to main content
Feedback

Oracle Fusion Cloud Applications connection

Updated 
note
Oracle Fusion Cloud Applications connector is part of Boomi's Early Access program, which offers beta versions of Boomi innovations on an "as is" basis, with no warranties. These features are not final production releases, are unsupported under Boomi's service agreements and support services, and are not intended for production use. While Boomi will work to address issues encountered during the preview and welcomes participant feedback, any feedback provided — whether ideas, suggestions, code, or recommendations, oral or written — is irrevocably assigned to Boomi, LP. By participating, you confirm you have the authority to provide that feedback, will not assert any intellectual property claims against Boomi, and that Boomi may freely implement it without violating any party's rights. If a beta feature doesn't meet Boomi's standards or raises significant concerns, it may never reach general availability, and Boomi cannot guarantee any particular innovation will be released in a supported form. Note that some innovations may only be available as open source or for specific runtime configurations. Documentation may be provided as PDFs, online, or on Community forums.

Refer to the Early Access page to view current programs and request Early Access for a specific feature.

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.

Prerequisites

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

  1. 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).
  2. 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.
  3. 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

  1. Navigate to the Data Integration console.
  2. Select Connections, then select + New Connection.
  3. Search for and select Oracle Fusion Cloud Applications as the connection type.
  4. Enter a Connection Name to identify this connection.
  5. Enter your Integration user name.
  6. Enter your Integration user password.
  7. 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.
  8. Select Test Connection to confirm Data Integration can authenticate and reach your pod.
  9. Select Save to finish creating the connection.

Notes

  • 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.

On this Page