OIC Prebuilt Adapters Guide

Introduction

Oracle Integration Cloud Pre-Built Adapters are one of the most powerful accelerators in modern cloud integration projects. In Oracle Integration Cloud (OIC Gen 3), adapters eliminate the complexity of handling low-level APIs, authentication, and connectivity, allowing consultants to focus on business logic instead of plumbing.

In real-world Oracle Fusion implementations, especially across HCM, ERP, and SCM modules, adapters significantly reduce development time. Instead of writing custom REST/SOAP integrations, consultants can leverage pre-built adapters that already understand Oracle applications, third-party systems, and protocols.

From a consulting perspective, I’ve seen projects where using the right adapter reduced integration effort by 40–60% compared to custom API-based builds.

What are Oracle Integration Cloud Pre-Built Adapters?

Oracle Integration Cloud Pre-Built Adapters are ready-to-use connectors that simplify integration with SaaS, on-premises applications, and third-party systems.

These adapters handle:

• Authentication (OAuth, Basic, API keys)

• Connection configuration

• Data mapping structures

• API interaction (REST/SOAP abstraction)

• Error handling frameworks

Instead of manually coding integrations, you configure adapters through a UI-driven approach in OIC.

Common Adapter Categories

Real-World Integration Use Cases

Use Case 1: Employee Data Sync (HCM → External Payroll)

A client needed to send employee updates from Oracle HCM to a third-party payroll system.

Solution:

• HCM Cloud Adapter → Extract employee data

• REST Adapter → Push data to payroll API

Outcome:

• Near real-time sync

• No custom API coding required

Use Case 2: Supplier Invoice Integration (ERP → Banking System)

Invoices created in ERP needed to be sent to a banking system for payment processing.

Solution:

• ERP Cloud Adapter → Fetch invoice data

• FTP Adapter → Send file to bank

Outcome:

• Automated daily batch processing

• Reduced manual file handling

Use Case 3: Order Integration (SCM → E-commerce Platform)

Sales orders from an e-commerce platform needed to be pushed into Oracle SCM.

Solution:

• REST Adapter → Receive orders

• SCM Cloud Adapter → Create sales orders

Outcome:

• Fully automated order flow

• Improved order processing speed

Architecture / Technical Flow

In OIC Gen 3, adapters fit into a standard integration flow:

Source Adapter → Integration Logic → Target Adapter

Typical Flow

1. Trigger Adapter (Inbound)

2. Data Transformation (Mapper)

3. Business Logic (Conditions, Loops)

4. Invoke Adapter (Outbound)

Example

Key Insight from Projects

Adapters act as abstraction layers, meaning:

• You don’t deal with raw APIs

• Oracle maintains compatibility with SaaS updates

• You focus on business transformation logic

Prerequisites

Before working with adapters in OIC Gen 3:

Environment Setup

• OIC Gen 3 instance provisioned

• Access to Integration Designer

• Required roles:

  • Service Developer

  • Integration Specialist

Connectivity Requirements

• SaaS credentials (Fusion ERP/HCM/SCM)

• API endpoints (for REST/SOAP)

• FTP server details (if applicable)

Security Setup

• OAuth or Basic authentication

• Certificates for secure communication

• Whitelisting IPs (for on-prem systems)

Step-by-Step Build Process

Let’s walk through a practical example: Integrating Oracle ERP Cloud with an external REST system

Step 1 – Create Connection (ERP Adapter)

Navigation:

Navigator → Integrations → Connections → Create

Steps:

1. Select ERP Cloud Adapter

2. Enter:

   • Name: ERP_Invoice_Connection

   • Role: Invoke

3. Configure:

   • URL: ERP instance URL

   • Authentication: Basic/OAuth

4. Test connection

Step 2 – Create REST Adapter Connection

1. Select REST Adapter

2. Enter:

   • Name: External_REST_Service

3. Configure:

   • Base URL: External API endpoint

   • Security: API Key / OAuth

4. Test connection

Step 3 – Create Integration

Navigation:

Navigator → Integrations → Create → App Driven Orchestration

Steps:

• Name: ERP_to_REST_Integration

• Select trigger:

  • ERP Adapter (e.g., Business Event or Scheduled Extract)

Step 4 – Configure Trigger

• Choose ERP Business Object:

  • Example: Invoice

• Select operation:

  • Get Invoice Data

Step 5 – Add Mapping

Map ERP fields to REST payload:

Use OIC mapper to drag and drop fields.

Step 6 – Add Invoke (REST Adapter)

• Select REST connection

• Choose:

  • POST method

  • Endpoint resource

Step 7 – Add Error Handling

• Add Scope

• Configure Fault Handler

• Log errors using:

  • Tracking variables

  • Notification emails

Step 8 – Activate Integration

• Click Activate

• Enable tracing if required

Testing the Technical Component

Test Scenario

Trigger integration with a sample invoice.

Sample Input (ERP Data)

Expected REST Payload

Validation Checks

• Integration instance completed successfully

• Data received in external system

• No fault messages in OIC tracking

Common Errors and Troubleshooting

1. Authentication Failure

Issue: 401 Unauthorized

Fix:

• Check credentials

• Validate OAuth token

2. Incorrect Endpoint

Issue: 404 Not Found

Fix:

• Verify REST URL

• Check resource path

3. Mapping Errors

Issue: Data not transforming correctly

Fix:

• Validate source schema

• Use XPath functions carefully

4. Timeout Issues

Issue: Integration fails due to delay

Fix:

• Increase timeout settings

• Optimize API response

Best Practices

1. Use Standard Adapters First

Avoid custom REST/SOAP unless absolutely required.

2. Reuse Connections

• Create shared connections

• Avoid duplication across integrations

3. Enable Tracking Fields

• Use business identifiers (Invoice ID, Employee ID)

• Helps in debugging

4. Implement Fault Handling

Always configure:

• Global fault handler

• Notifications

5. Optimize Payload Size

• Avoid unnecessary fields

• Use filtering

6. Follow Naming Conventions

Example:

• ERP_INV_TO_BANK_INT

• HCM_EMP_SYNC_INT

7. Secure Credentials

• Use OIC Vault

• Avoid hardcoding sensitive data

Expert Consultant Insights

From real implementations:

• Always validate adapter capabilities before designing integration

• ERP/HCM adapters often provide business object-level operations, not just APIs

• REST adapter is flexible but requires careful schema design

• For high-volume integrations, combine adapters with stage file processing

Summary

Oracle Integration Cloud Pre-Built Adapters are essential for building scalable, maintainable, and efficient integrations in modern Oracle Cloud environments.

They:

• Reduce development time

• Simplify complex API interactions

• Provide standardized connectivity

• Improve integration reliability

In real-world projects, mastering adapters is one of the fastest ways to move from a beginner to an advanced OIC consultant.

For deeper technical understanding, refer to Oracle’s official documentation:

https://docs.oracle.com/en/cloud/paas/application-integration/index.html

FAQs

1. What is the advantage of using OIC adapters over custom APIs?

Adapters eliminate the need for manual API handling, provide built-in authentication, and reduce development effort significantly.

2. Which adapter is most commonly used in OIC?

The REST Adapter is widely used because of its flexibility, followed by ERP and HCM Cloud adapters.

3. Can we use multiple adapters in a single integration?

Yes, a single integration can use multiple adapters (e.g., ERP + REST + FTP) depending on the business requirement.