FBDI Callback in OIC Guide

Share

Introduction

In modern Oracle Fusion Cloud implementations, handling large data loads efficiently is a critical requirement. One of the most widely used mechanisms for bulk data import is FBDI (File-Based Data Import). However, a common challenge consultants face is tracking the status of these imports and triggering downstream processes automatically. This is where building an FBDI Callback Service in Oracle Integration Cloud (OIC Gen 3) becomes essential.

In this blog, we will walk through how to build an FBDI Callback Service in OIC, focusing on a real-world consultant approach. This includes architecture, step-by-step configuration, error handling, and best practices based on actual implementation experience.

What is FBDI Callback Service in OIC?

An FBDI Callback Service in Oracle Integration Cloud is a mechanism used to:

  • Monitor the status of FBDI jobs submitted to Oracle Fusion
  • Receive asynchronous responses once the job is completed
  • Trigger follow-up integrations or notifications

Why is this needed?

When you upload an FBDI file (e.g., for invoices, employees, suppliers), the process runs asynchronously in Fusion. Without a callback mechanism:

  • You won’t know when the job completes
  • You cannot automate downstream workflows
  • Manual monitoring becomes inefficient

The callback service solves this by enabling event-driven integration.

Real-World Integration Use Cases

1. Supplier Invoice Automation (ERP)

A finance team uploads invoices using FBDI. Once the import completes:

  • Callback triggers validation integration
  • Sends email notification to AP team
  • Updates status in external system

2. Employee Data Load (HCM)

HR uploads bulk employee records:

  • Callback checks load success/failure
  • Triggers onboarding workflow for successful hires
  • Logs rejected records for correction

3. Item Import in SCM

Product team loads items via FBDI:

  • Callback service validates item status
  • Pushes data to external warehouse system
  • Sends alerts for failed records

Architecture / Technical Flow

Here is how the FBDI Callback Service works in OIC Gen 3:

  1. FBDI file is uploaded to Oracle Fusion (via UCM or ERP Adapter)
  2. ESS Job (Enterprise Scheduler Service) is triggered
  3. Job runs asynchronously in Fusion
  4. OIC registers a callback endpoint
  5. Fusion sends job completion status to OIC callback
  6. OIC processes response and triggers next steps

Key Components

  • OIC Integration (App Driven Orchestration)
  • ERP Cloud Adapter
  • Callback Endpoint
  • ESS Job Request ID
  • Polling/Callback Mechanism

Prerequisites

Before building the FBDI callback service, ensure the following:

1. OIC Gen 3 Instance

  • Active integration instance
  • Required roles and permissions

2. ERP Cloud Adapter Connection

  • Properly configured with Fusion credentials
  • Test connection successful

3. FBDI Template

  • Correct file format (CSV + ZIP)
  • Valid data as per Fusion standards

4. UCM Account Access

  • Required for file upload

5. Knowledge of ESS Jobs

  • Understanding job names like:
    • Import Payables Invoices
    • Load Interface File for Import

Step-by-Step Build Process

Step 1 – Create Integration

Navigation:
OIC Console → Integrations → Create

  • Select: App Driven Orchestration
  • Name: FBDI_Callback_Service

Step 2 – Configure Trigger (REST Endpoint)

  • Add REST Adapter as trigger
  • Configure:
    • Method: POST
    • Payload: FBDI file details / metadata

Example Input Payload:

 
{
“fileName”: “AP_INVOICES.zip”,
“jobName”: “Import Payables Invoices”
}
 

Step 3 – Upload File to UCM

  • Use ERP Cloud Adapter
  • Operation: Upload File to UCM

Important Fields:

Field Value
Document Account fin$/payables/import$
File Name Dynamic (from input)
File Content Base64 encoded file

Step 4 – Submit ESS Job

  • Use ERP Adapter → Submit ESS Job

Key Parameters:

Parameter Example
Job Name Import Payables Invoices
Package Name /oracle/apps/ess/financials/payables/invoices

Output:

  • ESS Job Request ID (critical for callback)

Step 5 – Configure Callback Mechanism

Here is the most important step.

  • Enable “Wait for Callback” option in ERP Adapter
  • Provide:
    • Callback Integration endpoint
    • Correlation ID (ESS Job ID)

This allows OIC to wait for Fusion response asynchronously.

Step 6 – Add Callback Activity

  • Use ERP Adapter → Get ESS Job Status
  • Configure with:
    • Request ID (from Step 4)

Step 7 – Process Response

Once callback is received:

  • Parse response:
    • Status: SUCCEEDED / ERROR
    • Log details

Example Response Handling:

  • If Success:
    • Trigger downstream integration
  • If Error:
    • Send notification
    • Log error details

Step 8 – Add Notification Logic

Use:

  • Email Adapter / REST API

Example:

  • Send success email to Finance team
  • Send error report with failed records

Step 9 – Activate Integration

  • Validate integration
  • Activate
  • Test with sample payload

Testing the Technical Component

Test Scenario

Upload a sample FBDI file for invoices.

Expected Flow

  1. File uploaded successfully
  2. ESS job triggered
  3. Callback received
  4. Status processed

Validation Checks

  • Check ESS Job status in Fusion:
    • Navigator → Tools → Scheduled Processes
  • Verify OIC logs:
    • Tracking → Instances

Expected Results

Scenario Expected Result
Valid File Job Success
Invalid Data Error status
Wrong Format Job Failure

Common Errors and Troubleshooting

1. Callback Not Triggered

Cause:

  • Incorrect endpoint URL

Solution:

  • Verify OIC callback URL

2. ESS Job Stuck in Running State

Cause:

  • Data issues or system delay

Solution:

  • Check logs in Fusion Scheduled Processes

3. File Upload Failure

Cause:

  • Incorrect UCM account

Solution:

  • Validate document account path

4. Authentication Issues

Cause:

  • Invalid ERP credentials

Solution:

  • Reconfigure ERP adapter connection

Best Practices

1. Use Correlation IDs Properly

Always map ESS Job ID correctly to track callback responses.

2. Implement Error Handling Framework

  • Use fault handlers in OIC
  • Log errors in external system

3. Avoid Hardcoding Values

  • Use lookups for:
    • Job names
    • UCM accounts

4. Monitor Integrations

  • Enable tracking
  • Use meaningful instance names

5. Optimize File Size

  • Split large files
  • Avoid performance bottlenecks

6. Secure Callback Endpoint

  • Use authentication policies
  • Restrict access

Real Consultant Tip

In a production project, we implemented an FBDI callback for invoice processing. Initially, the team used polling instead of callback, which caused:

  • Delays in processing
  • Increased API calls
  • Performance issues

After switching to callback:

  • Processing time reduced by 40%
  • Real-time updates improved user experience

Summary

Building an FBDI Callback Service in OIC Gen 3 is a critical skill for Oracle Fusion consultants working on integrations. It enables:

  • Real-time monitoring of FBDI jobs
  • Automation of downstream processes
  • Improved system performance and reliability

By following the structured approach outlined above, you can design scalable and robust integrations that align with real-world enterprise requirements.

For more detailed technical reference, you can explore Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. What is the difference between polling and callback in OIC?

Polling continuously checks job status, while callback waits for Fusion to send response automatically. Callback is more efficient and real-time.

2. Can we use FBDI callback for all modules?

Yes, it can be used across ERP, HCM, and SCM wherever ESS jobs are involved.

3. What happens if callback fails?

OIC integration may timeout or fail. It is recommended to implement fallback logic like retry or manual monitoring.


Share

Leave a Reply

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