FBDI Callback Setup in OIC

Introduction

In modern Oracle Cloud implementations, FBDI Callback in Oracle Integration Cloud is a critical pattern used to automate data load monitoring and trigger downstream processes after file-based imports complete. If you are working on large-scale ERP or HCM integrations, especially involving bulk data loads through FBDI (File-Based Data Import), setting up the prerequisites correctly is not optional—it directly impacts reliability, automation, and error handling.

From a consultant’s perspective, most integration failures around FBDI callbacks are not due to complex logic—they are due to missing prerequisites like improper ESS job configuration, callback URLs, or incorrect security policies.

In this detailed guide, we will walk through how to set up prerequisites for FBDI Callback in OIC (Gen 3) with real-world examples, implementation insights, and practical troubleshooting tips.

---

What is FBDI Callback in Oracle Integration Cloud?

FBDI Callback is a mechanism where Oracle Fusion applications send a status notification (callback) to OIC after an FBDI job completes.

Instead of polling the system repeatedly, OIC waits for a callback, making the integration:

• More efficient
• Event-driven
• Scalable

Key Components Involved

• FBDI File Upload (UCM)
• ESS Job Execution
• Callback URL (REST endpoint in OIC)
• OIC Integration to process callback

---

Real-World Integration Use Cases

Use Case 1: Bulk Employee Upload in HCM

A company uploads 10,000 employee records using HDL/FBDI. After the ESS job completes:

• Callback triggers OIC
• OIC validates status
• Sends email notification to HR team

---

Use Case 2: AP Invoice Import in ERP

Finance uploads supplier invoices using FBDI:

• System processes invoices
• Callback notifies OIC
• OIC triggers approval workflow or reconciliation

---

Use Case 3: Item Import in SCM

Product team uploads items:

• ESS job completes
• Callback triggers OIC
• OIC updates external warehouse system

---

Architecture / Technical Flow

Here is how the complete FBDI Callback flow works in real projects:

1. File is uploaded to UCM via OIC
2. ESS Job is triggered (Import Job)
3. Fusion processes data
4. After completion → Fusion triggers Callback URL
5. OIC receives callback payload
6. OIC processes success/failure response

---

Prerequisites for FBDI Callback in OIC

Before building the integration, ensure the following prerequisites are in place:

1. OIC Instance (Gen 3)

• Active OIC Gen 3 instance
• REST adapter enabled

---

2. Oracle Fusion Access

• Access to:
  • ERP / HCM / SCM
• Required roles:
  • Integration Specialist
  • Application Implementation Consultant

---

3. UCM (Universal Content Management) Access

• Required to upload FBDI files
• WebCenter Content configured

---

4. ESS Job Details

You must know:

---

5. Callback URL from OIC

• REST endpoint generated in OIC
• Should be accessible from Fusion

---

6. Security Setup

• OAuth or Basic Auth configured
• Required policies enabled

---

7. Business Event or Callback Enablement

• ESS jobs must support callback
• Callback URL must be passed during job submission

---

Step-by-Step Setup of FBDI Callback Prerequisites

Step 1 – Create REST Endpoint in OIC

Navigate to:

OIC Console → Integrations → Create Integration → App Driven Orchestration

• Select REST Adapter as trigger
• Define endpoint like:

Important Fields

• Request Payload: JSON
• Enable “Configure for Callback”

---

Step 2 – Activate Integration and Get Endpoint URL

After activation:

• Copy endpoint URL
• Example:

This URL will be used in ESS job submission.

---

Step 3 – Configure Security (Critical Step)

In real implementations, this is where most failures happen.

Option 1: Basic Authentication

• Create integration user in Fusion
• Provide credentials in callback

Option 2: OAuth (Recommended)

• Register OIC as trusted application
• Generate token endpoint

---

Step 4 – Validate Callback Reachability

Before proceeding:

• Use Postman to test endpoint
• Ensure:
  • URL is accessible
  • No firewall issues
  • SSL certificates are valid

---

Step 5 – Prepare ESS Job Submission Payload

When submitting ESS job from OIC:

You must pass callback details.

Example Payload Snippet

---

Step 6 – Enable Callback in ESS Job

Not all ESS jobs support callbacks.

Check:

• Documentation
• Job parameters

If supported:

• Pass callback URL dynamically
• Ensure correct parameter position

---

Step 7 – Configure UCM Upload

Upload FBDI file before triggering job:

Navigation:
Navigator → Tools → File Import and Export

OR via OIC:

• Use ERP Cloud Adapter
• Upload to UCM account

---

Testing the FBDI Callback Setup

Step 1 – Upload Sample File

Example:

• Invoice FBDI file
• Employee data file

---

Step 2 – Trigger ESS Job

From OIC:

• Submit job with callback URL

---

Step 3 – Monitor Job Status

In Fusion:

Navigator → Tools → Scheduled Processes

---

Step 4 – Validate Callback in OIC

Check:

• Integration instance tracking
• Callback payload received

---

Expected Callback Payload

---

Validation Checklist

• Callback triggered?
• Correct status received?
• Integration processed data?

---

Common Implementation Challenges

1. Callback Not Triggered

Reason:

• ESS job does not support callback

Solution:

• Use polling as fallback

---

2. Authentication Failures

Reason:

• Invalid credentials or token

Solution:

• Reconfigure OAuth / Basic Auth

---

3. Invalid Callback URL

Reason:

• Typo or wrong endpoint

Solution:

• Always copy from activated integration

---

4. Firewall Issues

Reason:

• Fusion cannot reach OIC

Solution:

• Whitelist OIC endpoint

---

5. Incorrect Payload Handling

Reason:

• JSON structure mismatch

Solution:

• Log and validate payload schema

---

Best Practices from Real Projects

1. Always Use Asynchronous Pattern

Avoid polling unless necessary.

---

2. Maintain Logging in OIC

• Log requestId
• Log job status

---

3. Design Reusable Callback Integration

Instead of one integration per job:

• Build generic callback handler

---

4. Secure Endpoint Properly

• Prefer OAuth over Basic Auth
• Rotate credentials regularly

---

5. Implement Retry Mechanism

In case callback fails:

• Retry logic should exist

---

6. Validate ESS Job Compatibility

Before design:

• Confirm callback support

---

7. Use Naming Standards

Example:

• INT_FBDI_CALLBACK_HANDLER
• INT_AP_INVOICE_IMPORT

---

Summary

Setting up FBDI Callback prerequisites in Oracle Integration Cloud (Gen 3) is a foundational step for building scalable and event-driven integrations. From defining REST endpoints to configuring ESS job parameters and securing the callback flow, each step plays a critical role in ensuring seamless data processing.

In real-world projects, consultants who invest time in correctly configuring prerequisites avoid major production issues later. Whether you’re working on HCM, ERP, or SCM integrations, mastering this setup will significantly improve your integration design quality.

For deeper reference, always review Oracle’s official documentation:
https://docs.oracle.com/en/cloud/saas/index.html

---

FAQs

1. Can all ESS jobs support FBDI callback?

No. Only specific ESS jobs support callback functionality. Always verify in documentation before implementation.

---

2. What is better: Callback or Polling?

Callback is always preferred as it is event-driven, reduces API calls, and improves performance.

---

3. How to secure FBDI callback in OIC?

Use OAuth authentication wherever possible. Avoid exposing unsecured REST endpoints.