# Connect Oracle Integration Cloud (OIC) To Fusion ERP > Source: https://netray.co/erp-help/fusion-oracle-integration-cloud-with-fusion-erp > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need. ## Kind how-to ## System oracle-fusion ## Erp Oracle Fusion Cloud ERP ## Module Oracle Integration Cloud (OIC) / Fusion Adapter ## Query How to connect Oracle Integration Cloud to Fusion ERP ## Alternate Queries - OIC Fusion ERP adapter connection setup - Oracle Integration Cloud integration with Fusion Applications - OIC ERP Cloud adapter authentication - when to use OIC instead of direct REST calls to Fusion ## Applies To Oracle Integration Cloud (OIC Gen 3), Oracle Fusion Cloud ERP and SCM, standard ERP Cloud Adapter ## Steps ### Set up an OIC connection to Fusion ERP **Items:** In OIC, create a new Connection and select the Oracle ERP Cloud Adapter (or Oracle ERP Cloud - for Integration) from the adapter catalog. Enter the Fusion instance host URL and choose the security policy - typically OAuth-based (Resource Owner Password Credentials or a configured confidential application) or Basic Authentication with an integration user, depending on what your tenant's identity setup supports. Test the connection; a successful test confirms OIC can reach the Fusion instance and authenticate, not that any specific business object is accessible yet. Create an integration flow (App Driven or Scheduled) and add the ERP Cloud connection as an invoke; the adapter wizard lets you browse and pick the business object, operation, and whether it is a SOAP or REST-based service. Map source and target payloads in the integration canvas; for BI Publisher-based extracts, use the adapter's report/BIP options instead of manually calling BI Publisher's web service. Add error handling with a fault scope or Business Identifiers so failed instances are traceable in OIC's Monitoring, and configure retry policy for transient Fusion-side errors like a Blocked ESS job. Activate and test end to end with realistic data volumes before relying on scheduled or event-driven triggers in production. ## Sections ### Why Use The Adapter Instead Of Raw REST **Body:** The ERP Cloud Adapter discovers available Fusion REST and SOAP services, exposes their operations and payload structures inside the OIC design canvas, and handles OAuth or Basic Auth token mechanics for you. Calling Fusion REST endpoints directly with a generic REST adapter still works and is sometimes necessary, but you lose the guided object picker and take on more manual payload and auth handling. ### Authentication Choices **Body:** Most ERP Cloud Adapter connections authenticate with either Basic Authentication against a dedicated integration user, or an OAuth flow backed by an Identity Cloud or OCI IAM application registered for Fusion. The right choice depends on what your tenant's identity provider is configured to support - check with whoever administers Fusion's Identity and Access Management before building the connection, since a mismatch here is the most common reason a connection test fails. ### Event-Driven Vs Scheduled Integrations **Body:** Fusion can publish business events (through Oracle Integration Cloud's event subscription or the Fusion Applications event framework) that trigger an OIC integration in near real time, which suits things like a new supplier invoice notification. For bulk or batch-style movement - nightly master data sync, period-end extracts - a scheduled integration calling FBDI, HDL, or BI Publisher through the adapter is usually simpler and more predictable than trying to force an event-driven design onto bulk data. ### Common Failure Points **Body:** A connection that tests fine can still fail mid-flow if the integration user lacks the data security scope for a specific business unit, or if a BI Publisher report referenced by the adapter has been renamed or moved to a different folder in the Fusion BI catalog. Both surface as generic OIC runtime errors, so check the Fusion-side security and report path first before assuming the OIC flow itself is broken. ## Pitfalls Reusing a personal Fusion login as the integration user instead of a dedicated service account with scoped roles - it breaks when that person's password rotates. Assuming a successful connection test in OIC guarantees access to every business object - function and data security are still evaluated per API call. Building bulk data movement as an event-driven integration when a scheduled FBDI/HDL-based flow through the adapter would be simpler and more reliable. Not setting a retry policy for transient Fusion errors, such as an ESS job temporarily Blocked, causing an integration to fail permanently on a condition that would have cleared in minutes. Hardcoding a BI Publisher report path in the integration instead of confirming it against the current Fusion BI catalog folder structure after a report gets moved or renamed. Skipping realistic volume testing, so pagination limits and governance thresholds only surface once the integration is already in production. ## Ai Angle ERPray grounded on both your Fusion tenant and your integration landscape can trace a failed OIC-to-Fusion flow back to its actual cause - a data security gap, a renamed BI Publisher report, or a Blocked ESS job on the Fusion side - instead of you switching between OIC Monitoring and Fusion Scheduled Processes to piece the failure together manually. ## Faq ### Do I need the ERP Cloud Adapter, or can I use a generic REST adapter? **Answer:** The generic REST or SOAP adapter can call any Fusion web service directly and works fine, but you lose the ERP Cloud Adapter's object picker, prebuilt operation list, and simplified authentication handling. Most implementations prefer the ERP Cloud Adapter for anything it already supports and fall back to generic REST only for newer or niche services it does not yet expose. ### Can OIC trigger a Fusion FBDI or HDL load directly? **Answer:** Yes - the ERP Cloud Adapter can invoke the Load Interface File for Import and related scheduled processes, or drop files for HDL pickup, as part of an OIC integration flow, letting you orchestrate file generation, upload, and job submission from a single integration rather than scripting each step separately. ### Why does my OIC integration fail only for certain business units? **Answer:** This is almost always a Fusion-side data security gap: the integration user's role has function access to the API but not the data role or security profile covering that particular business unit or ledger, which produces an access error only when the flow touches that scope. ### Is Basic Authentication still supported for OIC to Fusion connections? **Answer:** It remains a commonly used option for the ERP Cloud Adapter alongside OAuth-based flows, but which one your tenant supports depends on how Identity and Access Management is configured for Fusion. Confirm the current supported options with your Fusion security administrator before building the connection. ## Search terms Oracle Integration Cloud Fusion ERP adapter, OIC ERP Cloud Adapter setup, connect OIC to Fusion ERP, OIC Fusion authentication OAuth, Oracle Integration Cloud business events Fusion, OIC integration monitoring Fusion errors, ERP Cloud Adapter connection test failed, OIC scheduled integration FBDI --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json