OIC File Adapter Explained

Share

Introduction

The Oracle Integration Cloud File Adapter is one of the most commonly used components in Oracle Integration Cloud (OIC Gen 3), especially in real-time and batch integration scenarios. In almost every enterprise implementation, consultants deal with file-based integrations—whether it is inbound employee data, outbound financial reports, or supplier uploads.

From my experience working on multiple Oracle Fusion implementations, nearly 60–70% of integrations involve file handling in some form. That’s where the File Adapter becomes critical.

In this blog, we will go deep into how the File Adapter works, how to configure it, real-world use cases, and practical troubleshooting insights that consultants actually use during projects.


What is Oracle Integration Cloud File Adapter?

The File Adapter in Oracle Integration Cloud is a connectivity component that allows integrations to read, write, list, stage, and process files from various file systems such as:

  • SFTP servers
  • FTP servers
  • File Server (OIC File Server)
  • Local staging area within OIC

It acts as a bridge between external file-based systems and Oracle Fusion applications like HCM, ERP, and SCM.

Key Capabilities

  • Read and write files in multiple formats (CSV, XML, JSON, Fixed-width)
  • Support for large file processing
  • File chunking and streaming
  • PGP encryption/decryption
  • Zip/unzip support
  • File polling and scheduling

Real-World Integration Use Cases

1. HCM Employee Data Load via HDL

A common scenario:

  • HR team uploads employee data in CSV format to SFTP
  • OIC picks up the file using File Adapter
  • Transforms it into HDL format
  • Sends it to Oracle HCM Cloud

👉 This is one of the most standard enterprise use cases.


2. ERP Invoice Processing

  • Vendors upload invoice files to FTP
  • OIC reads the file
  • Validates and transforms the data
  • Pushes it to Oracle ERP via REST APIs

👉 File Adapter ensures seamless automation without manual intervention.


3. SCM Bulk Item Upload

  • External system generates item master data
  • File is dropped in a secure location
  • OIC processes and sends data to Oracle SCM

👉 Used heavily in manufacturing and retail implementations.


Architecture / Technical Flow

Here’s how the File Adapter works in a typical integration:

  1. File is placed in SFTP/FTP server
  2. OIC integration is triggered (scheduled or event-based)
  3. File Adapter reads the file
  4. Data is parsed using a schema (XSD/CSV definition)
  5. Mapping/transformation is applied
  6. Data is sent to target system (Fusion, DB, REST API)
  7. Optional: File is archived or deleted

Logical Flow

Source System → File Server → File Adapter → Integration → Target System

Prerequisites

Before configuring File Adapter in OIC Gen 3, ensure the following:

1. SFTP Server Details

  • Host name
  • Port
  • Username/password or SSH key

2. File Format Definition

  • CSV structure
  • XML schema (XSD)
  • JSON sample

3. Connectivity Setup

  • Create connection in OIC
  • Configure security (Basic/SSH Key)

4. Access Permissions

  • Read/write permissions on directories

Step-by-Step Build Process

Let’s walk through a practical implementation scenario: Reading a CSV file from SFTP and processing it.


Step 1 – Create File Adapter Connection

Navigation Path:

OIC Console → Integrations → Connections → Create

Select Adapter:

  • Choose File Server Adapter or FTP Adapter

Configuration:

  • Connection Name: SFTP_EMPLOYEE_FILE_CONN
  • Host: sftp.company.com
  • Port: 22
  • Security: SSH Key or Username/Password

👉 Test and Save the connection.


Step 2 – Create Integration

Navigation Path:

OIC → Integrations → Create → App Driven Orchestration

  • Name: Read_Employee_File_Integration

Step 3 – Configure Trigger (File Read)

Drag File Adapter as Trigger.

Configuration Details:

  • Operation: Read File
  • Directory: /inbound/hr/
  • File Name Pattern: Employee_*.csv
  • Schema Definition: Upload sample CSV

Important Fields:

Field Explanation
Directory Folder path on SFTP
File Pattern Controls which files are picked
Schema Defines file structure

👉 Define columns like:

  • Employee Number
  • Name
  • Department
  • Salary

Step 4 – Parse File Structure

OIC automatically generates schema based on CSV.

Example:

EmployeeNumber,Name,Department,Salary 1001,John,IT,50000

👉 This schema is used in mapping.


Step 5 – Add Processing Logic

Add For-Each Loop to process records.

Inside loop:

  • Map fields to target structure
  • Perform validations (optional)

Step 6 – Add Target Adapter

Example: REST Adapter to push data to Fusion

Map:

  • EmployeeNumber → PersonNumber
  • Department → Organization

Step 7 – Archive File (Optional)

Add File Adapter again:

  • Operation: Move File
  • Source: /inbound/hr/
  • Target: /archive/hr/

Step 8 – Save and Activate

  • Validate integration
  • Activate

Testing the Technical Component

Test Scenario

Upload file:

Employee_20260401.csv

Expected Flow

  1. Integration triggers
  2. File is read successfully
  3. Records are processed
  4. Data is sent to target system
  5. File is moved to archive

Validation Checks

  • Check integration instance tracking
  • Verify payload in OIC logs
  • Confirm data in target system

Common Errors and Troubleshooting

1. File Not Picked Up

Cause:

  • Incorrect directory path
  • File naming mismatch

Fix:

  • Verify path and pattern

2. Permission Denied

Cause:

  • SFTP access issue

Fix:

  • Check user permissions

3. Schema Mismatch

Cause:

  • File structure changed

Fix:

  • Regenerate schema

4. Large File Processing Issues

Cause:

  • Memory constraints

Fix:

  • Use file chunking or streaming

5. Duplicate File Processing

Cause:

  • File not moved after processing

Fix:

  • Always archive or delete processed files

Best Practices from Real Projects

1. Always Archive Files

Never leave processed files in inbound directory.


2. Use File Naming Standards

Example:

EMPLOYEE_YYYYMMDD.csv

3. Enable Logging

Capture:

  • File name
  • Record count
  • Errors

4. Use Staging Area for Large Files

OIC staging improves performance.


5. Implement Error Handling

  • Use Scope + Fault Handler
  • Send email notifications

6. Secure File Transfers

  • Always use SFTP (not FTP)
  • Use SSH keys instead of passwords

7. Validate Input Data

Before sending to Fusion:

  • Check null values
  • Validate formats

Summary

The Oracle Integration Cloud File Adapter is a foundational component for file-based integrations in enterprise environments. Whether you’re working on HCM data loads, ERP transactions, or SCM integrations, mastering the File Adapter is essential.

From a consultant’s perspective:

  • It simplifies file handling
  • Reduces manual effort
  • Enables scalable integrations

But success depends on:

  • Proper configuration
  • Strong validation logic
  • Robust error handling

If you understand how to design and optimize File Adapter integrations, you can handle a large portion of real-world Oracle Cloud integration requirements.


FAQs

1. What file formats does File Adapter support?

It supports CSV, XML, JSON, fixed-width, and binary formats.


2. Can File Adapter handle large files?

Yes, using streaming and chunking features in OIC Gen 3.


3. How to avoid duplicate file processing?

Move or archive files immediately after processing.


Oracle Documentation

For deeper technical reference, always review the official Oracle documentation:

https://docs.oracle.com/en/cloud/saas/index.html


Share

Leave a Reply

Your email address will not be published. Required fields are marked *