Introduction
FBDI Automation Service in Oracle Integration Cloud is one of the most practical and high-demand integration patterns used in real-time Oracle Fusion implementations. In almost every ERP or HCM project within Oracle Fusion Cloud, you will encounter bulk data loading requirements—such as supplier creation, employee data migration, or journal imports. This is where FBDI (File-Based Data Import) combined with OIC Gen 3 becomes a powerful automation solution.
In real consulting scenarios, manual FBDI uploads are rarely acceptable in production environments. Clients expect fully automated, error-resilient, and trackable integrations. This blog walks you through how to design, build, and deploy an FBDI Automation Service using OIC Gen 3 with a practical, implementation-focused approach.
What is FBDI Automation Service in OIC?
FBDI Automation Service is an integration pattern where:
- Data is transformed into Oracle-provided FBDI templates (CSV/ZIP)
- Files are uploaded to Fusion via Web Services or REST APIs
- Import jobs are triggered automatically
- Status is monitored and reported back
Instead of manual uploads through UI:
Tools → File Import and Export → Load Interface File
You automate the entire process using OIC.
Key Components Involved
| Component | Purpose |
|---|---|
| FBDI Template | Oracle-provided CSV structure |
| UCM (Content Server) | File storage in Fusion |
| ERP Integration Service | Job submission |
| OIC Integration | Orchestration layer |
| BI Reports / Logs | Status tracking |
Real-World Integration Use Cases
1. Supplier Data Integration from External Procurement System
A client uses a third-party procurement tool. Supplier data is pushed daily into Fusion.
Solution:
- OIC fetches supplier data via REST API
- Maps to Supplier FBDI template
- Uploads ZIP to UCM
- Triggers “Import Suppliers” job
2. Bulk Journal Entry Upload from Legacy Finance System
During migration or daily operations:
- Finance system sends GL data
- OIC converts it into Journal Import FBDI
- Automatically submits import job
3. Employee Data Migration from HR System
For HCM implementations:
- External HRMS sends employee data
- OIC generates HDL or FBDI
- Automates upload and import
Architecture / Technical Flow
Here’s how a typical FBDI automation works in OIC Gen 3:
- Source System sends data (REST/SFTP)
- OIC receives payload
- Data is mapped to FBDI CSV format
- OIC stages file (ZIP creation)
- Upload to UCM via ERP Adapter
- Submit ESS Job (Import Process)
- Poll for job status
- Send response or notification
Logical Flow
Prerequisites
Before building FBDI automation, ensure:
1. Fusion Setup
- Required business object enabled (e.g., Suppliers, GL)
- Access to:
- File Import and Export
- Scheduled Processes
2. FBDI Template
Download from Oracle:
- Example: Payables Suppliers Import Template
- Fill sample data to understand structure
3. OIC Gen 3 Setup
- ERP Cloud Adapter configured
- REST Adapter configured (if needed)
- Connections tested successfully
4. Required Details
| Parameter | Example |
|---|---|
| UCM Account | fin$/payables$/import$ |
| Job Name | Import Payables Invoices |
| Document Name | suppliers.zip |
Step-by-Step Build Process in OIC Gen 3
Step 1 – Create Integration
- Login to OIC Gen 3
- Navigate to:
Integrations → Create → App Driven Orchestration
Choose trigger:
- REST / Scheduled / File-based
Step 2 – Configure Trigger
Example: REST Trigger
- Define payload structure:
“SupplierName”: “ABC Corp”,
“SupplierNumber”: “SUP1001”
}
Step 3 – Data Transformation to FBDI Format
- Use Stage File Action
- Create CSV structure
Example mapping:
| Field | Value |
|---|---|
| Supplier Name | ABC Corp |
| Supplier Number | SUP1001 |
Consultant Tip:
Always validate CSV encoding (UTF-8) to avoid import failures.
Step 4 – Create ZIP File
- Use “Stage File → Zip File” option
- Add CSV into ZIP
Example:
Step 5 – Upload File to UCM
Use ERP Cloud Adapter:
- Operation: Upload File to UCM
- Required Fields:
| Field | Value |
|---|---|
| Document Account | fin$/payables$/import$ |
| File Name | suppliers.zip |
| Content Type | application/zip |
Step 6 – Submit ESS Job
Use ERP Adapter:
- Operation: Submit ESS Job
Example:
| Parameter | Value |
|---|---|
| Job Name | Import Suppliers |
| Parameter 1 | suppliers.zip |
| Parameter 2 | UCM Account |
Step 7 – Poll for Job Status
- Use “Wait” + “Loop” pattern
- Call “Get ESS Job Status”
Check:
- SUCCEEDED
- ERROR
Step 8 – Send Response
- Return success or failure
- Optional: Send email notification
Testing the Technical Component
Test Scenario
Input:
“SupplierName”: “Test Supplier”,
“SupplierNumber”: “SUP999”
}
Expected Flow
- CSV created
- ZIP uploaded
- ESS job triggered
- Supplier created in Fusion
Validation Checks
- Check UCM file upload:
Tools → File Import and Export - Check job status:
Tools → Scheduled Processes - Verify data:
Suppliers UI
Common Errors and Troubleshooting
1. File Upload Failure
Cause:
- Incorrect UCM account
Fix:
- Validate account path
2. ESS Job Fails
Cause:
- Incorrect parameters
Fix:
- Check job definition in Fusion
3. Data Import Errors
Cause:
- Invalid CSV structure
Fix:
- Validate against Oracle template
4. Encoding Issues
Cause:
- Special characters
Fix:
- Use UTF-8 format
Best Practices from Real Projects
1. Use Reusable Integrations
Create generic FBDI upload service reusable across modules.
2. Implement Logging Framework
Store:
- Request payload
- File name
- Job ID
- Status
3. Add Error Handling Layer
- Catch exceptions
- Send alerts
- Retry logic
4. Use Callback Mechanism
Instead of polling:
- Use callback service (advanced design)
5. Optimize Performance
- Batch processing
- Avoid large file sizes (>10MB per file)
6. Secure Credentials
- Use OIC Vault
- Avoid hardcoding credentials
Real Consultant Insight
In one finance implementation, the client initially used manual FBDI uploads for journal entries. This led to:
- Delays in closing periods
- Human errors
- Lack of audit trail
After implementing OIC-based FBDI automation:
- Journal upload time reduced by 80%
- Errors dropped significantly
- Full audit tracking achieved
This is why FBDI automation is considered a must-have integration pattern.
Summary
FBDI Automation Service in OIC Gen 3 is a critical integration pattern for handling bulk data loads into Oracle Fusion. It replaces manual file uploads with automated, scalable, and reliable processes.
Key takeaways:
- Combines FBDI templates + OIC orchestration
- Enables end-to-end automation
- Supports multiple modules (ERP, HCM, SCM)
- Requires strong understanding of file structure and job execution
For deeper understanding, always refer to Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. What is the difference between FBDI and HDL?
- FBDI is mainly used for ERP modules (Finance, Procurement)
- HDL is used for HCM data loading
2. Can we avoid ZIP file creation in FBDI?
No. Oracle requires files to be uploaded in ZIP format for most FBDI imports.
3. Is polling mandatory for job status?
Not always. Advanced implementations use callback services to avoid polling.