Oracle Fusion Cloud connectivity from QSEoW

ArockiyaM — Wed, 24 Sep 2025 08:45:59 GMT

Hi Team,

We are using Qlik sense client managed on prem. We have a requirement to connect with Oracle Fusion Cloud.

If you have connected with Fusion cloud already, can you share some light on how you did that? which connectors you used,...?

Re: Oracle Fusion Cloud connectivity from QSEoW

atulkumar — Thu, 02 Oct 2025 16:01:15 GMT

Oracle Fusion Cloud does not allow direct database connectivity (you cannot connect directly to the Fusion SaaS DB). Instead, integrations happen through Fusion Cloud web services (SOAP/REST APIs) or through OTBI (Oracle Transactional Business Intelligence), which exposes subject areas via web services.

Typical approaches used:

REST Connector in Qlik Sense
- Use Qlik’s built-in REST Connector to call Oracle Fusion Cloud REST APIs.
- Fusion exposes secured REST endpoints for modules like HCM, Financials, SCM, etc.
- You’ll need to set up OAuth2 or Basic Auth (depending on your Fusion tenancy setup).
- Example: /fscmRestApi/resources/11.13.18.05/receivablesInvoices
- Data is pulled as JSON/XML → transformed inside Qlik.
OTBI (BI Publisher) Web Services
- If your reporting requirement is broader, Oracle Fusion OTBI can expose subject areas (pre-built analytics views).
- You can call OTBI via SOAP/BI Publisher web services and consume results in Qlik via REST Connector (SOAP can also be handled as XML).
- This is useful for large/complex reports instead of pulling raw transactional data.
Middleware / iPaaS Layer (Optional)
- Some companies put Oracle Integration Cloud (OIC), Dell Boomi, or MuleSoft in between, and Qlik connects to that via REST/ODBC.
- This simplifies security and avoids handling token refresh logic directly in Qlik.

Connectors Used in Practice:

Qlik REST Connector (most common, supported out of the box).
ODBC/JDBC via third-party drivers (CData, Progress DataDirect, etc.) → if you want SQL-like access to Fusion APIs.
SOAP/REST web services through OTBI if you already have OTBI enabled.

Key Considerations:

Authentication: Fusion Cloud usually requires OAuth2 with Refresh Tokens; you may need to script token renewal.
Data Volumes: APIs are paginated (max rows per call), so you must handle paging in Qlik scripts.
Performance: For heavy reporting, use OTBI instead of hitting transactional APIs repeatedly.

topic Oracle Fusion Cloud connectivity from QSEoW in Connectivity & Data Prep

Oracle Fusion Cloud connectivity from QSEoW

Re: Oracle Fusion Cloud connectivity from QSEoW