Oracle Fusion to Power BI: ETL & reporting challenges?

[BI_is_Fun]

I’m fairly new to working with Oracle Fusion as a data source and would love to learn from others who’ve integrated it with Power BI.

If you’ve extracted Fusion data (via OTBI, BIP, or other methods) into a warehouse for Power BI reporting:

What are the top problems you have faced with Oracle Fusion, particularly in reporting and in ETLing data to your Data Warehouse?

I’m looking for real-world lessons learned both on the data extraction side and on the Power BI reporting side. Any insights would be greatly appreciated!

[v-pgoloju]

Hi @BI_is_Fun,

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[v-pgoloju]

Hi @BI_is_Fun,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @Thomaslleblanc  for prompt and helpful responses.

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[v-pgoloju]

Hi @BI_is_Fun,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @Thomaslleblanc  for prompt and helpful response.

Oracle Fusion doesn’t allow direct database or SQL access, so all data must be pulled through OTBI, BI Publisher, BICC, or APIs and this is the root of most challenges. OTBI works only for small, ad hoc analysis, BIP is better for batch extracts but can be slow and fragile, and APIs need extra engineering for pagination, limits, and incremental loads. Fusion data is highly transactional and effective dated, not reporting ready, so it must be reshaped into a clean star schema in a data warehouse before using Power BI. Incremental loads and history tracking are tricky, often requiring snapshot tables. For reporting, Import mode performs far better than DirectQuery, and security usually needs a separate mapping table. Overall, Fusion works well for operations, but successful Power BI reporting depends on strong ETL, simplified models, and realistic refresh expectations.

Thaks & Regards,

Prasanna kumar

[Thomaslleblanc]

No direct database access
Fusion data resides behind APIs—no SQL connection to the app DB. You must source data via OTBI, BI Publisher, BI Cloud Connector (BICC), or REST/SOAP APIs
https://www.orbitanalytics.com/blog/oracle-fusion-to-data-warehouse-challenges-options/