Skip to main content
Telara

Integrations / Oracle Fusion Cloud Applications

Oracle Fusion Cloud Applications logo

Oracle Fusion Cloud Applications

Read-only Oracle Fusion REST resources for receivables invoices, procurement purchase orders, and supply-chain product items. These are separate, documented resource contracts; they do not establish broad coverage of other ERP/SCM modules, Oracle E-Business Suite support, or tenant role/business-unit access.

Basic auth
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

An Oracle Fusion Cloud tenant with the required Financials, Procurement, or SCM module enabled.
An administrator who can grant the integration user access to the requested business units or inventory organizations.

Vendor setup

Get the credential

1
Confirm module and release
Identify the enabled Fusion modules and their release. This connector declares read-only receivables invoices, Procurement purchase orders, and SCM Product Lifecycle Management itemsV2 resources; other resources are not implied.
2
Create a least-privilege integration user
Grant only the resource roles and business-unit or inventory-organization data access needed for the requested reads. Oracle Fusion Basic Authentication over HTTPS is the declared method.
3
Configure the connection
In Telara’s Oracle Fusion integration settings, enter the tenant base URL and the integration user’s username and password. Do not use credentials from a production tenant for a trial connection.

In Telara

Connect in Telara

Basic auth

Oracle Fusion Applications Basic Authentication over SSL. Use a dedicated least-privilege integration user with the required resource roles and business-unit data access. OAuth client/assertion flows are not declared by this connector.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Base Url
  • Username
  • Password

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Available records follow the integration user's Oracle roles, business-unit access, and inventory-organization access.
The catalog does not establish OAuth, writes, broad Fusion module coverage, or Oracle E-Business Suite support.