Fusion DB Connect™
No ticket to file and no one-off report to build. Query Oracle Fusion Cloud with real SQL, from the tools your team already uses, under their own Fusion login, read-only, every time.
| LEDGER_ID | NAME | CURRENCY_CODE |
|---|---|---|
| 300000046975971 | Canada Primary Ledger | CAD |
| 300000046975980 | UK Primary Ledger | GBP |
| 300000046975962 | US Primary Ledger | USD |
Oracle Fusion holds the data. Getting it out is the part that takes two weeks.
Without it
With Fusion DB Connect
How it works
Windows or macOS, on the desktop of whoever needs it. Nothing is deployed into your Fusion pods beyond a single query processor in the BI Publisher catalog.
Connect with your own Oracle Fusion credentials. There is no shared service account and no stored password. Your roles and data security come with you.
Write SQL against the Fusion application schema and get rows back. SELECT * FROM GL_LEDGERS is a query, not a project.
Architecture
Oracle does not permit direct database connections to Fusion Cloud, and Fusion DB Connect does not claim otherwise. Queries travel Oracle’s supported BI Publisher path, so it complies with published facilities and your license agreement.
SQL*Developer, Notepad++, the command line, DBeaver, DataGrip or your own Java code. Fusion DB Connect is a standard JDBC 4.0 driver, so each one treats a Fusion pod like any other schema.
A generic query processor installed in your own BI Publisher catalog. It runs each query as the person asking, and your administrators decide which role may invoke it.
Production, test and every development pod in your Oracle Account. ERP, HCM and Supply Chain data, with data security and VPD applied to every row.
It grants convenience, not access. Every row Fusion DB Connect returns is a row that user could already have pulled from a BI Publisher report. They just skip the two-week build.
Where you can use it
Fusion DB Connect meets your team where they already work. There is no new interface to learn and no reporting platform to adopt.
Ships with the driver. Type querytool in any SQL session, or run it from the command line: object browser, editor, result grid and CSV export.
The tool your team already has open. Add Fusion DB Connect as a JDBC data source and query a pod like any other schema.
Select the SQL in your editor, run it, and the results come straight back. No context switch, no export step.
A headless CLI over the same governed connection, for scripted extracts, scheduled jobs and reconciliation runs.
JSR 221 / JDBC 4.0 compliant, so DBeaver, DataGrip and your own code all work without a special integration.
Call Oracle Fusion REST services on a connected pod without leaving your session. Type service from any SQL tool.
Security and architecture
Here is exactly what installing a query processor in your BI Publisher catalog means, and what it does not.
Queries execute under the calling user’s own Oracle Fusion security context, never a service account. Data security and VPD apply to every row. No privilege escalation is possible.
SQL access is read-only, enforced by Oracle on the BI Publisher path. That is not a promise about our software. It is a property of the platform your own team can verify.
The query processor sits in your BI Publisher catalog and can be restricted to a role your administrators grant, and revoke, in a tool you already run.
The artifact doesn’t grant access. It grants convenience. Every row it returns is a row that user could already have pulled from a BI Publisher report.
What you get
Discovery
Oracle Fusion has more than 25,000 tables, and the ones that matter are rarely the ones the documentation names. With a real connection your team can expand the tree, read the columns, check the date-tracked _F tables and see the keys for themselves.
Clear boundaries
Your security team will want these in writing, so here they are.
Oracle does not allow one to Fusion Cloud. Fusion DB Connect uses the supported BI Publisher path and says so.
No shared service account and no stored password. Every query runs as the person asking, with their roles and data security.
SQL access is read-only, and Oracle enforces it on the BI Publisher path, not our software.
It is a driver. Your team keeps the tools it already knows, and nothing new has to be adopted or administered.
The Fusion DB Connect Driver is incredibly valuable as it enables us to efficiently access data, significantly reducing manual effort. This allows our team to focus on more strategic tasks.
Miguel MendozaAutomation Engineer, CDI Products, a Michelin Group company
Plans
Every plan connects to every pod in an Oracle Account, and every query runs under the user’s own Fusion security.
$0
200 rows per query, one Oracle Account and all its pods. No card, no expiry.
$10/user/month
Unlimited rows, saved connections and read-only REST queries for one Oracle Account.
$24/user/month
Unlimited Oracle Accounts, two desktops, JWT authentication and full REST access.
from $15/seat/month
Professional for your team, with centrally managed connections, a named contact and an SLA.
Download
Free plan, 200 rows per query, no credit card. Registration takes an email address.
The free plan returns 200 rows per query against one Oracle Account and every pod it has. No credit card, no trial clock.
Windows and macOS · JSR 221 / JDBC 4.0 compliant · one registered named user per license
