Blitz Report Custom Reports Converter  Help

The Blitz Report Custom Reports Converter is a self-service Blitz Upload that lists every concurrent program on your Oracle EBS instance — RDF reports, BI Publisher reports, and other data-extract programs — together with usage statistics. You tick the ones you want migrated to Blitz Report and upload the file. The converter then collects each selected program’s source artifacts (the RDF binary, BI Publisher data definition and RTF templates, package DDL, and custom dependencies) into a single zip file you send to Enginatics for conversion.

When to use it

• You want to migrate your custom Oracle EBS reports to Blitz Report.
• You want to inventory your conversion candidates quickly, without exporting each one by hand.
• You want Enginatics to perform the conversion for you.

Before you start

• Blitz Report 3.3.5 or later installed on your instance.
• The “Blitz Report Custom Reports Converter” upload visible under your responsibility.
• A 1–5 character Customer Abbreviation agreed with Enginatics (e.g. ACME). It is used to namespace your programs on the Enginatics analysis instance so they don’t collide with other customers’ programs.
• Your Custom Object Prefix, if your custom objects don’t follow the Oracle-recommended XX prefix. The default is XX.

Step 1 — Open the converter

From the Blitz Report launcher, open Blitz Report Custom Reports Converter.

Step 2 — Set the parameters

Enter your Customer Abbreviation and, if needed, adjust the optional filters. The Custom Object Prefix defaults to XX.

Step 3 — Download the template

Click Run / Download. Blitz Report generates an Excel template with one row per candidate concurrent program, including Application, Program, Short Name, Program Type, Executable, Method, Output Format, Run Count, Distinct Users, and the first/last run dates — everything you need to decide which programs are worth migrating.

Step 4 — Mark “Convert Program = Yes”

Set Convert Program = Yes on each program you want migrated. The Customer Abbreviation and Custom Object Prefix are pre-filled on every row.

Step 5 — Save and upload

Upload the file with the standard Blitz Upload (Validate and Save). The upload request runs and waits for the gather to complete so the result file can report per-program status. As a rough guide: ~3–5 seconds per BI Publisher program, ~5–15 seconds per RDF program, ~1–2 seconds per data-extract program. A batch of 10 programs typically completes in under a minute.

Step 6 — Two outputs to look for

In your concurrent request list, two requests complete:

1. The upload itself — produces the result Excel file, with a per-row Status, your Convert Program selection, and a Gather Status (e.g. “7 file(s) written”).
2. The gather — its output is the zip named CONV_<ABBREV>_<batch>_<timestamp>.zip.

Step 7 — Send the zip to Enginatics

Download the zip from the gather request output and send it to Enginatics (or attach it to your support ticket). That’s the end of the customer-side work — we take it from there.

What’s inside the zip

CONV_ACME_5923949_20260519_132951.zip
├── manifest.txt              ← customer abbreviation, prefix, batch id, gather date, program list
├── gather_summary.txt        ← per-program gather status
├── import_reports.sh         ← auto-generated installer Enginatics runs
└── <PROGRAM_SHORT_NAME>/      ← one folder per converted program
     ├── <SHORT>.ldt           ← concurrent program definition
     ├── <SHORT>_ds.ldt        ← BI Publisher data source (BIP only)
     ├── <SHORT>_tpl.ldt       ← BI Publisher template registrations (BIP only)
     ├── *.rtf                  ← BIP template content (BIP only)
     ├── <EXEC_FILE>.rdf       ← Oracle Reports binary (RDF only)
     ├── <EXEC_FILE>_rdf.xml   ← rwconverter XML (RDF only)
     └── <owner>.<object>.<type>.sql   ← DDL of every custom dependency

Common questions

What is “Customer Abbreviation” for?
When Enginatics receives your zip, your programs are installed on our analysis instance namespaced with your abbreviation, so multiple customers’ programs never collide. We agree the abbreviation with you upfront.

Why “Custom Object Prefix”? My custom packages don’t start with XX.
Oracle recommends prefixing custom objects with XX, but not everyone follows it. This tells the converter what prefix to look for when collecting your custom dependencies. If your custom code uses CUST_, enter CUST. If you’ve mixed prefixes, run two passes with different prefixes.

Why does the upload run for a little while?
It waits for the gather to finish so the result file can show per-program status. Batches with many RDF reports take a few minutes; smaller batches complete in under a minute.

What if I select a report by mistake?
Run the upload again with a corrected selection. Each run produces its own zip — just send us the right one.

How does Enginatics use the zip?
We install your custom programs and their dependencies on our analysis instance, then run our automated converter to produce Blitz Reports, validate and test them, and tune their performance. You receive the resulting Blitz Reports back.

Troubleshooting