File Transfer Integration in OIC

Share

Introduction

File Transfer Integration in OIC is one of the most common integration patterns used in enterprise Oracle Fusion implementations. In many real-world Oracle Cloud projects, systems still exchange large volumes of data using files rather than APIs. Payroll files, supplier master data, bank statements, HR records, and financial transactions often arrive as CSV, XML, or ZIP files.

Oracle Integration Cloud (OIC Gen 3) provides a robust File Server and File Transfer Adapter that allows organizations to securely exchange files with external systems and internal applications such as Oracle Fusion HCM, ERP, and SCM.

In a typical implementation, files may be:

  • Uploaded by a third-party system

  • Picked up automatically from an SFTP server

  • Processed and transformed in OIC

  • Loaded into Oracle Fusion using HDL, FBDI, or REST APIs

Understanding how File Transfer Integration in OIC works is essential for integration consultants, especially when building data pipelines between legacy systems and Oracle Cloud applications.

This article explains the architecture, setup, implementation steps, and real project scenarios for file-based integrations using Oracle Integration Cloud Gen 3.


What is File Transfer Integration in OIC?

File Transfer Integration in Oracle Integration Cloud refers to the process of exchanging files between external systems and Oracle applications through OIC using secure protocols such as SFTP or OIC File Server.

OIC supports multiple file integration patterns:

Integration PatternDescription
Scheduled File PollingOIC checks a directory periodically for new files
Event-Based File TriggerIntegration starts immediately when a file arrives
File Upload via OIC File ServerExternal systems upload files directly
File GenerationOIC generates outbound files for other systems
File TransformationConvert CSV/XML to another format

Common file types used:

  • CSV

  • XML

  • JSON

  • ZIP archives

  • Fixed width files

OIC provides native adapters to manage file operations securely.

Main adapters involved:

  • FTP Adapter

  • Stage File Action

  • File Server (Gen 3 capability)


Key Features of File Transfer Integration in OIC

Secure File Exchange

OIC supports secure file transfer using:

  • SFTP

  • SSH encryption

  • Private key authentication

  • Password authentication

This ensures secure integration with external vendors, banks, and internal enterprise systems.


File Server Capability in OIC Gen 3

Oracle Integration Cloud Gen 3 introduces OIC File Server, which allows external applications to upload files directly into OIC.

Benefits:

  • Eliminates dependency on external SFTP servers

  • Centralized file management

  • Automatic triggering of integrations


Built-In File Processing Capabilities

OIC can process files using the Stage File action.

Capabilities include:

  • Reading large files

  • Splitting files into chunks

  • Parsing CSV or XML

  • Writing files

This helps process large enterprise datasets efficiently.


Integration with Fusion Applications

Files received via OIC can be sent to:

  • Oracle Fusion HCM (HDL files)

  • Oracle ERP (FBDI files)

  • Oracle SCM imports

  • External REST APIs

This enables automated enterprise data pipelines.


Real-World Integration Use Cases

Use Case 1 — Employee Data Import into Oracle Fusion HCM

A company maintains employee records in a legacy HR system.

Process flow:

  1. Legacy system generates Employee.csv

  2. File is uploaded to OIC File Server

  3. OIC integration reads the file

  4. Data is converted into HDL format

  5. HDL file is submitted to Oracle Fusion HCM

Result:

  • Automated employee creation

  • No manual data entry


Use Case 2 — Bank Statement Processing in Oracle ERP

Banks send daily statement files.

Integration flow:

  1. Bank uploads statement file via SFTP

  2. OIC scheduled integration checks the folder

  3. File is parsed

  4. Transactions are sent to Oracle ERP Cash Management

Result:

  • Automatic bank reconciliation


Use Case 3 — Supplier Data Synchronization

Suppliers send product catalogs daily.

Process:

  1. Supplier uploads CSV file

  2. OIC reads file

  3. Data transformed to Oracle format

  4. Data sent via REST API to Oracle SCM

Result:

  • Automated supplier product updates


Architecture of File Transfer Integration in OIC

Typical architecture includes the following components:

 
External System
|
| (Upload File)
|
SFTP Server / OIC File Server
|
| (Trigger Integration)
|
Oracle Integration Cloud
|
| (Stage File Processing)
|
Transformation / Mapping
|
|
Oracle Fusion Application
(HCM / ERP / SCM)
 

Main components involved:

ComponentPurpose
File ServerReceive files
FTP AdapterConnect to external SFTP
Stage File ActionProcess file contents
Integration FlowBusiness logic
Oracle AdapterSend data to Fusion

Prerequisites

Before building file transfer integrations in OIC, ensure the following prerequisites are configured.

1 OIC Gen 3 Instance

A working Oracle Integration Cloud instance.


2 Connectivity to SFTP Server

You must have:

  • Host name

  • Port

  • Username

  • Authentication method


3 File Format Definition

Define file format such as:

  • CSV schema

  • XML schema

  • Fixed width structure


4 Access to Target Oracle Application

Example:

  • Fusion HCM REST APIs

  • ERP FBDI import jobs

  • SCM web services


Step-by-Step Implementation of File Transfer Integration in OIC

The following steps explain how a consultant builds a file polling integration.


Step 1 — Create FTP Connection

Login to Oracle Integration Cloud.

Navigate to:

Home → Integrations → Connections → Create

Select adapter:

FTP Adapter

Enter connection details.

Example configuration:

FieldValue
Hostsftp.company.com
Port22
Usernameintegration_user
AuthenticationPassword / Key

Test the connection.

Click Save.


Step 2 — Create an Integration

Navigate to:

Home → Integrations → Create

Choose:

Scheduled Integration

Provide details:

FieldValue
NameEmployee_File_Integration
PatternScheduled
ScheduleEvery 5 minutes

Step 3 — Configure FTP Adapter Trigger

Add FTP Adapter as trigger.

Select operation:

Read File in Directory

Configuration:

ParameterExample
Directory/incoming/hr
File PatternEmployee*.csv
File ProcessingRead Entire File

Step 4 — Configure File Schema

Define file format.

Example CSV:

 
EmployeeID,FirstName,LastName,Department
1001,John,Smith,Finance
1002,Ana,Clark,HR
 

Import sample file to generate schema.


Step 5 — Add Stage File Action

Add Stage File activity.

Operation:

Read File

Options:

OptionValue
File FormatDelimited
DelimiterComma
Record StructureMultiple Records

This allows OIC to process each row separately.


Step 6 — Map Data

Add a Mapper step.

Map fields from CSV to target payload.

Example:

SourceTarget
EmployeeIDpersonNumber
FirstNamefirstName
LastNamelastName
DepartmentdepartmentName

Step 7 — Call Oracle Fusion API

Add REST Adapter.

Configure:

FieldValue
EndpointHCM REST API
MethodPOST
PayloadEmployee Data

Example endpoint:

 
/hcmRestApi/resources/latest/workers
 

Step 8 — Activate Integration

Click:

Activate

Now the integration runs automatically.


Testing File Transfer Integration

Testing is critical before production deployment.

Test Scenario

Upload a file:

 
Employee_Test.csv
 

Content:

 
1003,Raj,Verma,IT
1004,Anita,Sharma,Finance
 

Upload file to:

 
/incoming/hr
 

Expected Results

Integration should:

  1. Detect file

  2. Parse CSV

  3. Create employees in Oracle Fusion


Validation

Check:

  1. Integration tracking

  2. Target system records

  3. Error logs


Common Errors and Troubleshooting

File Not Detected

Cause:

Incorrect directory path.

Solution:

Verify SFTP path.


Schema Parsing Errors

Cause:

File structure mismatch.

Solution:

Ensure file matches schema exactly.


Large File Processing Issues

Cause:

Memory limits.

Solution:

Use file chunking in Stage File action.


Authentication Failures

Cause:

Invalid credentials.

Solution:

Verify key authentication or password.


Best Practices for File Transfer Integrations

Use Naming Conventions

Example:

 
Employee_20260312.csv
 

This helps identify file versions.


Archive Processed Files

Move processed files to:

 
/archive
 

This prevents duplicate processing.


Implement Error Handling

Add scope with fault handler.

Handle:

  • file errors

  • API failures

  • data validation issues


Use File Chunking for Large Files

For files larger than 10 MB:

  • Split records

  • Process batches

This improves performance.


Maintain Integration Logs

Always track:

  • file name

  • record count

  • processing status

This simplifies troubleshooting.


Summary

File Transfer Integration in OIC is a critical capability used in many Oracle Fusion implementations where systems exchange data through files instead of APIs.

Oracle Integration Cloud Gen 3 provides powerful tools such as:

  • FTP Adapter

  • Stage File processing

  • OIC File Server

  • Integration orchestration

With proper design, file-based integrations can automate large enterprise data flows including employee imports, bank statements, supplier data synchronization, and financial transactions.

Consultants implementing Oracle Fusion projects should master file-based integrations because many enterprise systems still rely heavily on file exchange patterns.

For additional technical details, refer to Oracle official documentation:

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


FAQs

1 What is File Server in OIC?

File Server is a built-in capability in OIC Gen 3 that allows external systems to upload files directly to Oracle Integration Cloud without requiring external SFTP infrastructure.


2 What file formats are supported in OIC file integrations?

OIC supports:

  • CSV

  • XML

  • JSON

  • Fixed width files

  • ZIP files

These formats can be processed using the Stage File action.


3 When should file integrations be used instead of APIs?

File integrations are commonly used when:

  • Legacy systems cannot call APIs

  • Large batch data must be processed

  • Bank or vendor systems provide file-based data feeds.


Share

Leave a Reply

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