By Konstantin Zhernevskiy, Senior Data Architect, Data Intensity

Oracle gives you several ways to report on Fusion Cloud Applications data, and teams often mix them up. OTBI reads live transactional data. FDI is a prebuilt analytics warehouse. OAC is the general analytics platform, and OAC paired with ADW is the fully custom path. They overlap a lot, which is exactly why the choice gets confusing. Here is a side-by-side look at where each one fits, including how the data flows, what you can customize, the AI features, and what it costs.

Where they come from

Oracle’s analytics platform grew out of Oracle Business Intelligence Enterprise Edition (OBIEE). OBIEE became Oracle Analytics Server (OAS) on-premises and Oracle Analytics Cloud (OAC) in the cloud [1]. OTBI is the OBIEE engine embedded inside Fusion Apps, riding the same Answers foundation [2].

The cleanest way to see the difference is by components:

• OBIEE = Analytics (analyses and dashboards) + BI Publisher (pixel-perfect output).
• OAC = Analytics + BI Publisher + Data Visualization (DV), the modern drag-and-drop layer.
• OTBI = the embedded OBIEE engine in Fusion, exposing Analytics, BI Publisher, and prebuilt subject areas.

How the data reaches the user

This is the heart of it. Each option takes a different route from Fusion to the report on screen.

OTBI connects to live Fusion transactional data through prebuilt subject areas, so the data is always current with no ETL layer [2]. It inherits Fusion’s security automatically, so setup is fast and users see only the rows they are allowed to see. It is included with Fusion at no extra license cost [2]. The trade-offs are real: you cannot customize the semantic model beyond flexfields, it is not built for heavy historical queries or large extracts (the Excel cap is 25,000 rows for analyses), and because it queries the live database, large reports can affect ERP performance [2].

FDI (Fusion Data Intelligence, formerly Fusion Analytics Warehouse, now also branded Oracle Fusion AI Data Platform) is the successor to the old BI Applications for EBS. Oracle-managed pipelines extract Fusion data into a prebuilt model in Autonomous Data Warehouse, surfaced through an OAC instance [3]. Because the data is replicated and curated, FDI handles what OTBI cannot: historical trends, cross-pillar analytics, aggregation, external-data blending, and machine learning. Loading data once means FDI does not tax ERP performance [2]. It refreshes daily, as often as every 4 hours for selected areas, or on demand [4]. Its model is extensible, and the prebuilt library is large and growing: Oracle’s public Fusion Analytics Content Explorer now surfaces more than 4,000 prebuilt metrics across HR, finance, supply chain, and customer experience [5], which is why FDI deploys in weeks rather than the many months a comparable custom build takes [3]. On AI, FDI includes prebuilt ML models and the Oracle Analytics AI Assistant for natural-language exploration [3]. OTBI has no equivalent.

FDI is prebuilt end to end. Oracle owns and maintains every stage, from the source pipelines through the warehouse model and semantic layer to the finished KPIs, dashboards, and reports.

OAC alone has no Fusion content. There is no prebuilt semantic model and no prebuilt dashboards out of the box; you build your own model and visuals, or you point OAC at FDI’s model [1]. You also build the data preparation yourself.

OAC + ADW is the fully custom path. You provision an Autonomous Data Warehouse, build your own extraction (usually via BI Cloud Connector, BICC), model the data, and visualize in OAC. This gives the most control and is the right answer when FDI’s prebuilt content does not fit or you need heavy non-Fusion integration. The cost is engineering time, since you are rebuilding what FDI gives you out of the box [1].

Side by side

Dimension	OTBI	FDI	OAC (alone)	OAC + ADW
Data Visualization (DV)	Not in classic OTBI	Yes (via OAC)	Yes	Yes
Analytics (analyses/dashboards)	Yes, prebuilt	Yes, prebuilt	Build your own	Build your own
BI Publisher	Yes, prebuilt	Yes, prebuilt	Yes	Yes
Semantic model	Prebuilt, sealed	Prebuilt, extensible	None prebuilt	Build your own
Extensibility	Flexfields only	High	High	Highest
AI capabilities	None	AI Assistant, prebuilt ML	OAC AI/ML, NLQ	OAC AI/ML, NLQ
Data freshness	Real-time	Daily / 4-hour / on demand	Your pipeline	Your pipeline
ERP performance impact	Yes, live queries	No, loads once	None directly	None directly
Prebuilt content	Subject areas + reports	4,000+ metrics + dashboards	None	None
Cost	Included with Fusion	Separate subscription	Separate (user or OCPU)	OAC + ADW compute + storage

OAC Data Visualization vs Power BI

If you are already on Oracle and Fusion, OAC is the more natural fit. It has native, optimized connectivity to Oracle Database, EBS, Fusion, and EPM, a strong enterprise semantic model, solid data preparation, and built-in machine learning, and it can run on-premises as OAS for data-sovereignty needs.

Power BI usually wins on the visualization experience, ease of use, self-service breadth, community size, and price, especially for shops already on Microsoft 365. Many enterprises run both: Power BI for broad departmental self-service, OAC for Oracle-centric operational and advanced analytics.

One licensing trap to watch: Oracle’s FDI administration docs state that if you extract, integrate, or share FDI data to any external system, you must be licensed by the employee metric for that module [6]. Pushing Fusion-sourced data into Power BI can therefore move you onto the whole-employee-base metric and raise cost sharply. Run a proof of concept with real data and users before committing.

What it costs

These products run on different meters, so treat the figures below as orientation, not quotes. OAC and ADW figures are Oracle list prices from the Oracle Cloud Price List and the Oracle Analytics Cloud pricing page, retrieved June 2026. FDI list pricing is not published publicly.

• OTBI: included with Fusion at no extra license cost [2].
• FDI: separately licensed, and Oracle does not publish its list price. It is quote-based through Oracle Sales, with published prerequisites (a minimum user count and a multi-year term) and the ADW and OAC underneath bundled into the subscription. To budget FDI, get a quote from your Oracle account team rather than relying on third-party figures [3].
• OAC: Enterprise is $80 per named user per month or $2.1506 per OCPU per hour; Professional is $16 per user per month or $1.0753 per OCPU per hour; BYOL is $0.3226 per OCPU per hour [7]. The OCPU meter bills for uptime, not logins, so idle instances still cost money. Minimum shape is 2 OCPUs [7].
• ADW: about $0.336 per ECPU per hour (serverless, license included), 2-ECPU minimum, plus storage; BYOL applies if you hold Oracle Database licenses [8].

Three quick scenarios (monthly, Oracle list, USD):

10 users. OTBI: $0 extra. FDI: quote-based, not publicly listed. OAC Enterprise: 10 x $80 = $800, plus any ADW. OAC + ADW: $800 plus a 2-ECPU warehouse running 24x7 at about $490, so roughly $1,290 plus storage.

100 users. OTBI: $0 extra. FDI: quote-based, not publicly listed. OAC Enterprise: 100 x $80 = $8,000 plus ADW. OAC + ADW: $8,000 plus a larger warehouse (say 8 ECPU always-on at about $1,960), so roughly $10,000 plus storage.

1 CPU-equivalent. OTBI and FDI are not sold by CPU. OAC Enterprise: 1 OCPU always-on is about $1,570 per month, Professional about $785, BYOL about $235 (the 2-OCPU minimum roughly doubles a true minimum instance). ADW: 2 ECPU always-on is about $490 plus storage.

The headline: OTBI is “free” because you already bought Fusion. FDI is a separately negotiated subscription, but that single price bundles the warehouse, the OAC instance, the pipelines, and 4,000+ prebuilt metrics. OAC and OAC + ADW have transparent list prices and look cheaper per user, but they require you to build and run everything, and their meters bill for uptime, so stop schedules and auto-scaling are your main cost levers.

Sidebar: OAC + ADW vs FDI, does it save money?

Every Fusion shop eventually asks this. If FDI just bundles ADW, OAC, pipelines, and content, can I build the same thing on OAC + ADW for less?

Part of the answer is that only one side has a public price. OAC and ADW are on Oracle’s price list, so the build side is easy to pin down: OAC Enterprise at $80 per user per month [7] plus a mostly fixed ADW compute cost that scales with workload and concurrency, not seats [8]. FDI is a negotiated quote, so put your own per-user FDI number next to the figures below.

Users	OAC + ADW (Oracle list)	FDI
10	~$800 (OAC) + ~$490 (2 ECPU ADW) = ~$1,290/mo	your Oracle quote x 10 users
100	~$8,000 (OAC) + ~$1,500 (4 to 8 ECPU ADW) = ~$9,500/mo	your Oracle quote x 100 users

(ADW figures assume an always-on warehouse; auto-scaling and stop schedules lower them, and BYOL cuts both OAC and ADW further if you already hold Oracle Database licenses.)

The pattern to notice: FDI is purely per user, so its cost climbs with every seat, while the OAC + ADW warehouse cost stays roughly flat as users grow. So the more users you have, the more the math tilts toward building your own. But the subscription is not the whole bill. Three things eat into the saving:

1. Build and maintenance labor. FDI ships the pipelines, the model, and 4,000+ metrics and dashboards. With OAC + ADW you build all of that yourself: BICC extraction, the data model, every dashboard, plus upkeep when Fusion changes. That is a real one-time project plus ongoing effort. At small user counts the subscription saving can take a year or more to recover the build; at large user counts it recovers quickly. Scale decides whether the build pays off.

2. Time to value. FDI deploys in weeks. A custom OAC + ADW build is months. If you need analytics now, that delay has a cost of its own.

3. The licensing trap. This is the one that can flip the answer. If the data in your ADW is extracted from Fusion, Oracle’s employee-metric licensing can apply, and OAC may then be licensed by total employee count rather than named users [6]. That can erase the per-user saving entirely. If your ADW data is not Fusion-sourced, this largely goes away. Confirm the metric with Oracle in writing before you architect around it.

Verdict. For a small, Fusion-only deployment that wants fast, low-maintenance analytics, FDI usually wins on total cost, because you skip the build and sidestep the metric question. For a larger deployment, or one that already runs ADW or blends a lot of non-Fusion data, OAC + ADW can save a great deal, as long as you have the team to build and run it and you have cleared the employee-metric question. Run the real numbers with your negotiated FDI quote and your own build estimate.

Which one, when

Keep OTBI for real-time, single-subject operational and statutory reporting. It is free, secure by default, and already in your Fusion subscription. Just keep reports modest in size to protect ERP performance.

Add FDI when you need history, cross-pillar analytics, aggregation, external blending, or AI, and you want prebuilt content fast. A good signal: if your team spends real time exporting OTBI to Excel and merging across modules, FDI will usually pay for itself.

Choose OAC alone when you already have a model or warehouse and just need a visualization and semantic layer, or when you want to extend FDI.

Choose OAC + ADW when your landscape is bigger than Fusion, with many users and many systems to bring together, and you are ready to invest the time and resources to design a custom solution, wait through a longer build, and support it afterward. This is the path for organizations that want full ownership of the warehouse and model and have the engineering capacity to build, run, and maintain the pipelines over the long term.

The most important point: FDI is not a replacement for OTBI. They complement each other, and most Fusion shops should run both. OTBI gives you “now.” FDI gives you “deep.”

---

References

1. Oracle, Oracle Analytics product pages (Oracle Analytics Server and Oracle Analytics Cloud), on the OBIEE to OAS/OAC lineage and on building your own model in OAC. https://www.oracle.com/business-analytics/ Retrieved June 2026.
2. Oracle A-Team, “Choosing the Right Reporting Framework in Fusion Cloud Applications,” 2025. Covers OTBI reading live transactional data, ERP performance impact, and embedded reporting (OTBI, BI Publisher) being included with Fusion Cloud Applications. https://www.ateam-oracle.com/choosing-the-right-reporting-framework-in-fusion-cloud-applications Retrieved June 2026.
3. Oracle, Fusion Data Intelligence product page (product overview, prebuilt pipelines, fast deployment, prebuilt ML models, and the Oracle Analytics AI Assistant). https://www.oracle.com/fusion-data-intelligence/ Retrieved June 2026.
4. Oracle, “Administering Oracle Fusion Data Intelligence: Schedule Frequent Refreshes of Data” (daily, every-4-hour, and on-demand refresh). https://docs.oracle.com/en-us/iaas/analytics-for-applications/doc/schedule-frequent-refreshes-data.html Retrieved June 2026.
5. Oracle, Fusion Analytics Content Explorer (browsable public library of prebuilt metrics, dashboards, and subject areas; more than 4,000 metrics). https://oac-public.com/ui/dv/ui/home.jsp?pageid=visualAnalyzer&reportmode=full&reportpath=%2F%40Catalog%2Fshared%2FFeatured%20Samples%2FFusion%20Analytics%20Content%20Explorer Retrieved June 2026.
6. Oracle, “Administering Oracle Fusion Data Intelligence: About Licensing” (employee-metric requirement when data is used with third-party tools or exported downstream). https://docs.oracle.com/en-us/iaas/analytics-for-applications/doc/licensing.html Retrieved June 2026.
7. Oracle, Oracle Analytics Cloud pricing (Enterprise $80/user/month or $2.1506/OCPU/hr; Professional $16/user/month or $1.0753/OCPU/hr; BYOL $0.3226/OCPU/hr; 2-OCPU minimum). https://www.oracle.com/business-analytics/pricing/ Retrieved June 2026.
8. Oracle, Oracle Autonomous Data Warehouse (serverless) ECPU pricing and 2-ECPU minimum, plus storage; BYOL for holders of Oracle Database licenses. Oracle Cloud Price List. https://www.oracle.com/cloud/price-list/ Retrieved June 2026.

Pricing note: Oracle does not publish Fusion Data Intelligence list pricing on a public page; budget it from an Oracle Sales quote rather than third-party figures. OAC and ADW figures above are Oracle list prices and vary with edition, auto-scaling, storage, region, discounts, and named-user minimums. Product naming is in flux: FDI was Fusion Analytics Warehouse and is now also branded Oracle Fusion AI Data Platform.