How to Ensure a Smooth Transition away from Oracle Discoverer

As a reporting tool of choice for many, how are you handling the transition away from Oracle Discoverer?

A complexity with Oracle Discoverer is that it requires extensive setup of the End User Layer to effectively engage reporting capabilities before users can create and modify reports. To ensure a smooth migration, organizations need to find the right tools that can give users the same capabilities and access they had in Discoverer, while allowing them the benefit of the recent advancements in reporting platforms.

Here are five reporting tips to ensure a smooth migration away from Discoverer:

  • Understand the reports that you have today in Oracle Discoverer. You don’t want to convert a copy of a copy of a report. Depending on how many user groups you have in Oracle Discoverer today, this may take some time to take stock of the scope of reporting. One approach to get prepared is by querying the EUL schema in EBS for the run statistics of the reports saved to the database through Discoverer.
  • Make a priority to quickly identify mission-critical reports that run the day-to-day operations. This is needed so you can convert them in the fastest way possible to get your users familiar with a new tool and to relieve the pressure of simply converting each report. This may require copying the SQL, for now, into the new tool. For a quick win, you’ll want to show progress while you implement a new solution.
  • Map your reports to new data model. After you’ve taken inventory of the reports used across the organization, open up Excel and start listing out the columns in those reports. Your objective will be to map your reports to a new data model and find any gaps that may exist in the new data model.
  • Address reporting gaps. Look for reporting gaps by extending the new data model to meet the needs of users. This exercise can save hundreds of hours of converting each report into a new tool. You only need to address the gaps by changing the data model that will support all of your reports. For example, you may have one table that is being used by 100 reports. In those 100 reports, there is a column that is missing in the new data model. You’ll only need to add that new column to the table once to support 100 reports.
  • Render reports into new tool. Once you have your new data model that supports all of your reports, the next job will be to actually render the reports into the new tool. Your mission is two-fold: replace Discoverer and the underlying data model and manage the change the users will go through with using the new tool. Instead of having your team taking on the task of rendering each report for the users, this is a good opportunity for users to get accustomed to the new tool. This is all about keeping the self-service capability they had in Discoverer intact.  This only works if you have addressed all of the gaps in the data model and provided them with more than just what is in the SQL of an individual Discoverer report.

We’ve helped our customers successfully transition from Oracle Discoverer to their BI platform of choice and increase their user satisfaction, even for the most advanced Discoverer users with Noetix.

For more on this topic, check out the webinar on-demand: How to ensure a smooth, successful transition away from Oracle Discoverer