← All articles
Enterprise Integrations & Use Cases, Getting Started Guides, Technical Tutorials

Migrate BI Publisher reports between Oracle Fusion environments

Migrate an Oracle Fusion BI Publisher report between environments by downloading its catalog archive from the source and uploading it to a reviewed destination path. Report execution is a separate operation. Test one report before expanding the transfer to other objects.

Use the current native package and separate named profiles for the source and destination. Each profile declares its Oracle origin and environment. The launcher prompts for the password and Toolkit licence instead of placing them in a command line. The setup documentation explains profile creation.

fusion-toolkit --profile erp-dev set-config \
  --environment development \
  --username YOUR_DEV_USERNAME \
  --origin https://YOUR_DEV_POD.fa.ocs.oraclecloud.com

Configure the destination independently under the required account. The example below names a test destination so the complete transfer can be checked before any production promotion.

fusion-toolkit --profile erp-test set-config \
  --environment test \
  --username YOUR_TEST_USERNAME \
  --origin https://YOUR_TEST_POD.fa.ocs.oraclecloud.com

Resolve the exact source catalog path and preserve the downloaded archive. Use an archive produced by the matching BI Publisher operation; a filename extension alone does not establish its contents or compatibility.

fusion-toolkit --profile erp-dev bi-publisher-download \
  --reportPath /Custom/SQL/ExampleReport.xdo \
  --outputFile ./ExampleReport.xdrz

Record the file checksum before moving the archive. On Linux, sha256sum ./ExampleReport.xdrz records it; on Windows, use Get-FileHash -Algorithm SHA256 ./ExampleReport.xdrz. A checksum identifies the local bytes and does not prove that a destination object already contains them.

Inspect the destination path before uploading. Preserve any existing object in a separately named archive so it can be restored if required. Confirm the intended object type and the permissions needed by the destination report.

fusion-toolkit --profile erp-test bi-publisher-upload \
  --file ./ExampleReport.xdrz \
  --targetPath /Custom/SQL/ExampleReport.xdo

Check the catalog object after the upload and run the report with known test parameters. Inspect its data-model dependency, output format and required access. A successful upload response or object-existence check does not establish that the report runs correctly.

Repeat the verified workflow for an approved production promotion only after reviewing that destination separately. Keep the source archive, its checksum and the destination verification together with the change record.

The AI Administrator catalog-transfer workflow adds reviewed plans and verification to the same business task. Use the report execution guide when you need to run a deployed report rather than move its definition.

Continue reading