1 Why EIS eXpress users are looking for a replacement
2 Why Blitz Report
3 What the migration converts
4 Migration process
4.1 Install Blitz Report
4.2 Run the EIS Import program
4.3 Import individual reports
4.4 Validate the migration
5 After the migration
6 Summary
Introduction
If your organization runs EIS eXpress Reporting from EIS Technologies on Oracle E-Business Suite, your reports run inside EBS, and your users are used to running them directly from their EBS environment.
Today, many of these customers need a new home for their EIS reports. Blitz Report runs inside EBS just like EIS eXpress did, and its automated import converts an entire EIS report library into Blitz Reports, with parameters, lists of values, layouts and security, in a single concurrent request.
1 Why EIS eXpress users are looking for a replacement
EIS Technologies has since rebranded as SplashBI, and its product development now focuses on the SplashBI analytics platform. SplashBI is a separate product that runs outside of Oracle EBS, with its own infrastructure, security model and user interface, so moving to it means a new platform project rather than an upgrade.
Customers who want to keep their reporting inside EBS, with EBS security, EBS responsibilities and EBS concurrent processing, are looking for an alternative built for exactly that.
2 Why Blitz Report
Blitz Report is built for Oracle EBS users and runs entirely inside the EBS environment:
- No additional infrastructure: Blitz Report is installed into the existing EBS database and application tier. There are no additional servers, agents or cloud services.
- EBS security: reports run under the user’s own EBS responsibility, with operating unit and ledger security applied, and assignments control who sees which report.
- Excel output: reports are generated directly as Excel files, with templates for column selections, pivot tables and charts, or run straight into a worksheet with the Excel Add-in.
- Speed: Blitz Report is the fastest reporting solution for Oracle EBS, even for reports with millions of rows.
- Ready-made content: the Blitz Report library provides a large number of ready-to-use EBS reports and uploads, many of which can replace migrated reports outright.
- Actively developed: Blitz Report receives new features and content with every release, see the changelog.
3 What the migration converts
The Blitz Report EIS import reads the EIS report definitions directly from the EBS database and creates one Blitz Report per EIS report:
- SQL: the report’s SQL, SQL view or database view becomes the Blitz Report SQL, so it can be maintained directly in Blitz Report instead of in a database view.
- Parameters and lists of values: EIS parameters become Blitz Report parameters, including their lists of values and dependent lists of values.
- Layouts: EIS pivots become Blitz Report templates with Excel pivot tables, and the report’s sort order is preserved.
- Security: the EIS report grants become Blitz Report assignments, so users keep access to the reports they had.
- Report triggers: EIS before and after report logic is converted, so reports that prepare data before they run keep working.
- EIS functions: calls to EIS database functions that have a standard EBS equivalent, such as operating unit and ledger security checks or lookup translations, are replaced by the standard EBS logic.
Imported reports are placed into the category ‘EIS eXpress’ and into the category of their EBS application, and each report’s description records the original EIS report ID, so every migrated report can be traced back to its source.
4 Migration process
4.1 Install Blitz Report
Download and install Blitz Report into your EBS environment. The installation detects EIS eXpress and adds the EIS import automatically.
4.2 Run the EIS Import program
Navigate to the System Administrator responsibility and run the Blitz Report EIS Import concurrent program. By default, it imports all enabled EIS reports that were executed within the last 365 days, so reports nobody uses are not migrated. The parameters restrict the import to an EIS application or a report name pattern, change the execution history window, and control whether seeded and disabled EIS reports are included. The Developer Guide describes each parameter.
The request log lists every imported, skipped and failed report. Running the program again skips reports that were already imported, unless you set Replace Existing to Yes.
4.3 Import individual reports
To import single reports, for example to try the migration on a few reports first, open the Blitz Report setup window, navigate to Tools > Import and select the type ‘EIS eXpress’. The list shows your EIS reports with their execution counts, number of users and last run date, most used reports first.
4.4 Validate the migration
Run the migrated reports with the same parameters as in EIS eXpress and compare the results. Because every report keeps its EIS report ID in its description, each Blitz Report is easy to match with its original.
5 After the migration
Once the reports are migrated, your users run them from the Blitz Report form or directly from Excel, and your developers maintain them in one place. Before reworking a migrated report, check the Blitz Report library: a ready-made report for the same purpose may already exist and can replace it.
Enginatics supports the migration and the validation of your reports. Contact us to plan your EIS eXpress replacement.
6 Summary
- Download and install Blitz Report into your EBS environment
- Run the Blitz Report EIS Import concurrent program, or import individual reports through Tools > Import
- Validate the migrated reports and retire EIS eXpress
Your EIS reports keep their SQL, parameters, lists of values, layouts and security, and they run inside EBS as before, with faster Excel output and a product that continues to evolve.