Fusion FBDI, BICC, OIC, and OTBI mapped to D365 integration and analytics

How Fusion's file-based data import, bulk extract, Oracle Integration Cloud flows, and OTBI reports map to D365's Data Management Framework, Azure Logic Apps and Data Factory, Synapse Link and Microsoft Fabric, and Power BI — and the practical rules for integration cutover.

What you will be able to do

Introduction

Fusion exposes five integration and reporting surfaces: FBDI for inbound bulk data, BICC for outbound bulk extract, OTBI for embedded operational reporting, REST APIs for real-time CRUD and action integrations, and SOAP for legacy backward compatibility.

FBDI and inbound bulk data

FBDI (File-Based Data Import) is Fusion's workhorse for bulk inbound data. Each FBDI template maps to a specific interface table and an ESS job that processes the uploaded file. FBDI templates exist for virtually every functional area: GL journals, AP invoices, suppliers, customers, items, purchase orders, projects, and assets.

BICC and outbound bulk extract

BICC (Business Intelligence Cloud Connector) extracts Fusion data through configurable Offerings and Business Objects. Administrators configure which data sets to extract, schedule the extraction, and direct output to Oracle Object Storage or another cloud store.

OIC and integration orchestration

Oracle Integration Cloud (OIC) is the most common integration middleware in Fusion implementations. OIC provides adapters for Fusion modules, Oracle databases, and third-party systems; an event-listener / trigger model; and a visual flow builder for orchestration.

OTBI and operational reporting

OTBI (Oracle Transactional Business Intelligence) exposes Fusion data through Subject Areas — pre-built dimensional models (star schemas) available for real-time reporting. A mature Fusion implementation may have 50–200 OTBI reports embedded in operational processes.

Business events and real-time integration

Both Fusion and D365 support business events — outbound notifications triggered when operational milestones occur (purchase order approved, invoice posted, payment made).

Idempotency, batching, and throughput

D365 integration patterns require three design rules applied consistently:

Knowledge check

Summary

Fusion's five integration surfaces have direct D365 parallels, but the operational model of each is different and the parallel breaks in specific places.