All posts · BI Reports

Connecting Oracle Analytics Cloud to Fusion ERP

How to set up live connections between OAC and Fusion Cloud for real-time analytics — direct database connections, OTBI feeds, and the Fusion Analytics Warehouse approach.

Anurag Jangra · February 23, 2026 · 6 min read · ... views

Connection options: OAC to Fusion Cloud

Option 1: Direct OTBI connection: OAC connects to Fusion’s OTBI semantic layer, exposing all Fusion subject areas in OAC. Good for basic analytics extending OTBI capabilities.

Option 2: Direct ATP/ADW connection: Fusion Cloud has an underlying Oracle Autonomous Data Warehouse. OAC can connect directly via OCI-native connector. Provides raw access but requires understanding Fusion’s complex schema.

Option 3: Fusion Analytics Warehouse (FAW): Oracle’s pre-built analytics solution that extracts Fusion data into a purpose-built data warehouse, pre-modelled for reporting. The recommended approach for serious analytics programs.

Setting up OTBI connection

  1. In OAC: Console → Connections → Create Connection → Oracle Fusion Applications
  2. Enter your Fusion Cloud URL and credentials
  3. OAC maps Fusion’s OTBI subject areas as data sources
  4. Create analyses in OAC using these subject areas — same data as native OTBI but with OAC’s superior visualisation capabilities

Fusion Analytics Warehouse overview

FAW is a separately licensed product that:

  • Extracts data from Fusion Cloud via Oracle Data Integrator
  • Loads into Autonomous Data Warehouse on OCI
  • Provides pre-built semantic models (ERP, HCM, SCM analytics)
  • Connects to OAC with pre-built dashboards

This eliminates the need to understand Fusion’s raw schema — the FAW semantic layer presents business-friendly metrics and dimensions.

Direct DB connection considerations

If connecting OAC directly to Fusion’s database (via JDBC or TCPS):

  • You must connect to the Analytics schema, not the transactional schema
  • Row-level security from Fusion doesn’t automatically apply — you must implement it manually in OAC’s data model
  • Oracle’s standard terms restrict direct DB access to authorised purposes — confirm with Oracle Support what’s permitted under your contract

Incremental refresh strategy

For analytical queries on large Fusion datasets, avoid live queries that hit Fusion’s OLTP database with every report load. Instead:

  • Schedule incremental extracts to an ADW instance
  • Build OAC analyses on the ADW copy
  • Refresh increments nightly (for overnight close data) or hourly (for operational metrics)

Think Beyond the Implementation

Questions worth sitting with after reading this

01

Why is this architecture appropriate for this specific context — and where would it be the wrong choice?

02

What assumptions did we make that aren't stated explicitly? What happens if those assumptions are wrong?

03

What would break first if the requirements changed — volume doubled, a third system was added, or the deadline halved?

04

What alternatives did we reject, and why? Was the decision made on evidence — or habit?

AJ
Anurag Jangra
Oracle Cloud PaaS Consultant · OIC & VBCS Specialist

4.5+ years delivering enterprise Oracle Cloud integrations and VBCS applications across manufacturing, IT services, and financial sectors. OCI Certified — writes about real-world OIC, VBCS, SQL, and BI Publisher patterns from production experience.

Chat on WhatsApp