Download FUSE
for Windows.

RC30 keeps Text, Number, Date, Timestamp and NULL separate from your SQL. Use Text for identifiers with leading zeros. Give inputs readable labels and descriptions, and mark required values.

List mode accepts 1–500 values per list, with at most 512 expanded binds per query. Use a parameter alone inside IN (:name) or NOT IN (:name). Larger lists may require a newer parameter model in a new approved folder; existing models are not replaced automatically.

Definitions do not save values. Named presets save values only when you explicitly choose to save them, and load only when you ask. Profiles belong to the exact SQL and connection. Treat presets as business data.

Catalog snapshots preserve original export bytes and checksums, record skipped items and limits, and support offline inspection and comparison. They use FUSE's snapshot format; they are not Oracle catalog import archives.

Copied SQL does not recreate a model's full execution context. Review its data source and parameters before running.

Snapshots and presets are local files without FUSE encryption. Review their SQL and business data before exporting or sharing, and keep appropriate backups.

Excel workbooks are created locally, with cancellation. Non-null values are text to preserve long IDs, leading zeros and exact decimal representations. Convert chosen columns in Excel when appropriate. Formula-looking values stay literal.

Analysis covers fetched data, not the whole Fusion database. Export scope is explicit: Current view, All fetched or Selected cells. Exports support up to 32 MiB of source text. Excel cells are limited to 32,767 UTF-16 units; oversized values fail with guidance rather than being silently truncated.

Up to 1 MiB of SQL text and 10,000 rows, 512 columns, or 500,000 result cells. Your Oracle environment may allow less. Export the current view, all fetched rows or selected cells. All fetched uses rows already retrieved; it does not run another query.

Each execution accepts a single SELECT or WITH statement and blocks direct data-changing SQL. Custom functions can still have side effects under your Oracle permissions. Use least-privileged access.

The query queue reviews up to 20 statements and collects their parameters separately. It runs sequentially, with up to 1,000 rows per statement and 10,000 in total. Stop prevents remaining queries from starting; an in-flight request may finish. The last completed result appears in the normal grid for analysis and export.

New HCM and Financials / SCM connections use the included V3 model. Working connections need no general model update. Typed inputs may need the separate parameter-report setup described in the portable guide.

Connect Codex or Claude through Settings > Coding tools. You approve each query request in FUSE. Permissions reset each session. Review the exact typed inputs, including list values, alongside the SQL and connection. Changing any of them requires a new approval.

Result sharing is off by default. Optional samples need your permission and may reach the coding tool's provider without automatic redaction. Samples are limited to 100 rows, 100 columns, and 64 KiB, and expire after five minutes. Clearing a sample cannot recall copies already shared.

The companion does not expose saved passwords, queries, drafts, or history. Your coding tool's separate file permissions still apply. See the privacy notice.

Look up HCM, Financials, Common, Procurement and Supply Chain objects in the bundled schema reference. Coverage varies. Check the linked Oracle documentation before using a column or join; your tenant permissions still apply.

Report tools prepare SQL, data models, report definitions, starter RTF layouts, and optional chart definitions. They do not upload or run reports. Review the files before importing them into BI Publisher.