Replace Oracle Discoverer with Power BI

Oracle Discoverer to Power BI migration, starting from the SQL behind each workbook

Replacing Oracle Discoverer with Power BI? We read your End User Layer, extract the query behind every worksheet people still open, and rebuild it on one governed Power BI model — with E-Business Suite security redesigned as row-level security and every number reconciled against the Discoverer original.

Scope approved before any hours are used · Hours never expire

  • Microsoft-certified
  • Prepaid hours that never expire
  • US-based senior engineers
  • One business area at a time
  • You own everything
Oracle Discoverer data model Sales Date Product Region Customer

Sample Oracle Discoverer reporting model. Illustrative data, not a client’s numbers

Why teams are moving now

A reporting tool that stopped getting patches in 2017

Discoverer is older than most of the reporting estates we migrate. Under Oracle's Lifetime Support Policy, Premier Support for Discoverer 11gR1 ended in June 2014 and Extended Support ended on 30 June 2017; the product now sits in Sustaining Support, and Oracle has said no new patches — including for E-Business Suite's Discoverer-based content — are created after that date. Existing patches and documentation stay available, so nothing switches off. What changes is that every browser, Java, database, or EBS upgrade becomes a question about whether Discoverer will still run afterwards.

The good news is that a Discoverer estate is unusually honest about itself. Every worksheet ultimately resolves to SQL generated from the End User Layer, and that SQL can be extracted. An Oracle Discoverer to Power BI migration is therefore less about reverse-engineering a black box and more about deciding which of those queries still matter, what they really mean, and who is allowed to see the rows they return.

What the rebuild covers

  • EUL read, business area by business area
  • Workbook & worksheet inventory
  • Worksheet SQL extraction
  • Folders → star schema
  • Calculations & conditions → DAX
  • EBS security → RLS
  • List reports → paginated reports
  • Reconciliation & cutover

Try us risk-free for 4 hours

Start with a block of prepaid Flex hours and, if you're unhappy within the first 4 hours, we refund you in full — no questions asked. Inventorying one business area and the workbooks that use it makes a good first task: it tells you the real size of the job before you commit a budget to it.

Start with one business area, risk-free →

How we approach it

From the End User Layer outward

Discoverer let every author assemble their own query from folders and items. Power BI works best when those choices are settled once, in a shared model. Most of the migration is making that shift deliberately.

The EUL, read folder by folder

Business areas, simple and complex folders, custom SQL folders, items, joins, calculated items, conditions and hierarchies all live in End User Layer tables in the database. We document them before a single visual is drawn.

SQL extracted per worksheet

The query behind each worksheet — with its conditions, parameters and joins resolved — is captured by hand for small estates or with an extraction tool for large ones. It becomes the specification the rebuilt report is tested against.

Usage decides the scope

Discoverer estates accumulate personal copies of the same workbook. Ownership, sharing and, where it was collected, the EUL's query statistics tell us which worksheets still run, so retired content is never rebuilt.

Hundreds of queries, one model

Where twenty worksheets each join the same EBS tables a slightly different way, we consolidate them into one fact table at a stated grain with shared dimensions, and the differences become named DAX measures instead of copy-pasted SQL.

Security redesigned, not assumed

Business Area access and EBS responsibilities do not translate directly into Power BI. We map who sees which ledgers, operating units or cost centres today, then rebuild that as row-level security and test it person by person.

List reports stay list reports

Many Discoverer worksheets are long tables exported straight to Excel. Those become paginated reports or a well-built table visual, not a dashboard nobody asked for, so the people who live in them keep their workflow.

What is actually inside a Discoverer estate?

Discoverer has two halves. The End User Layer is a metadata schema stored in the database: it groups tables and views into business areas, exposes them as folders and items with friendly names, defines the joins between folders, and holds calculated items, conditions, item classes and hierarchies. Workbooks sit on top of it: each workbook contains worksheets that pick items from one or more folders, apply conditions and parameters, and lay the result out as a table or crosstab. When a worksheet runs, Discoverer generates SQL from those choices and sends it to the database.

That shape drives the migration. There is no separate semantic server to replicate, but there is also no single governed model — the real business logic is scattered across custom folders full of hand-written SQL, calculated items defined in individual workbooks, and conditions that each author set slightly differently. Consolidating that into one model is where most of the value of the move comes from.

In most estates we see, the EUL sits on Oracle E-Business Suite, and many folders are built on EBS views rather than base tables. That matters twice: once for the data model, because the views carry joins and filters that have to be understood rather than copied, and again for security, because some EBS views only return the right rows when the session has been set up by an EBS login.

How do Discoverer objects map to Power BI?

This is the working map the plan is built from. Every line gets an owner and a decision before rebuild work begins, so nothing surprising appears halfway through the first business area.

Oracle Discoverer artefacts and their Power BI equivalents
Oracle Discoverer Power BI equivalent What changes in practice
End User Layer (EUL) Power BI semantic model Metadata stops living in database tables only an administrator can edit and becomes a documented, refreshable model
Business area One semantic model, or a set of display folders within it The business area becomes the migration unit and usually the workspace boundary
Simple folder (one table or view) A Power Query table, or a view in a staging database Friendly item names survive as column names and descriptions
Complex folder (items from several folders) Relationships between fact and dimension tables The join is declared once in the model instead of being re-resolved for each worksheet
Custom folder (hand-written SQL) A native query, or better, a named view in the warehouse Buried SQL is reviewed, owned and tested rather than carried across unread
Folder joins Model relationships with explicit cardinality Fan-out joins that quietly double-counted in Discoverer are found and fixed
Calculated item DAX measure, or a Power Query column One definition of each calculation instead of a copy per workbook
Condition Report, page or visual filter Mandatory conditions that kept queries small become model or source-query filters
Parameter Slicer, or a parameter on a paginated report Users filter a loaded model rather than re-running a prompted query
Item and date hierarchies Model hierarchies and a proper date table Drill paths are rebuilt; fiscal calendars become explicit columns
Summary folders Import-mode model, or user-defined aggregations Usually unnecessary once data is imported; kept only where volume demands it
Workbook Power BI report Several near-duplicate workbooks are often merged into one report
Worksheet (table or crosstab) Report page with a table or matrix visual, or a paginated report Exploratory sheets go interactive; print-and-export sheets go paginated
Page items Slicers The same filtering habit, applied without re-running the query
Discoverer Plus (authoring) Power BI Desktop Authors build on the shared model instead of assembling their own joins
Discoverer Viewer (consumption) Power BI Service: workspaces and apps Readers get a browser and mobile experience with no Java dependency
Discoverer Administrator Model ownership in Power BI Desktop plus workspace administration Metadata changes go through a versioned model, not direct EUL edits
Business Area access for users and responsibilities Workspace roles and app audiences Redesigned from a documented access matrix; it is not migrated directly
EBS responsibility and operating-unit data security Row-level security from a user-to-value security table Rebuilt and tested per user, because the EBS login context does not exist in Power BI
Scheduled workbooks Scheduled refresh and subscriptions Refresh runs once for the model; delivery is planned per audience

Want your own End User Layer mapped like this? Tell us which business area your team relies on most.

Book a free demo →

The folder and join rows carry most of the modelling risk, which is why we design against Microsoft's star schema guidance (opens in new tab) rather than recreating one table per folder. The measure work that follows is the data modeling and DAX half of the job. Microsoft's Power BI migration guidance (opens in new tab) follows the same order we do: assess and prioritise the existing content before rebuilding any of it.

How is the SQL behind each workbook extracted?

Every Discoverer worksheet resolves to a SQL statement, and capturing it is the most reliable specification a migration can have. For a modest estate it can be done by hand, worksheet by worksheet, from the authoring tools. For a large one, extraction tools read the EUL and workbook definitions in bulk; the consultancy ennVee, for example, has published a Discoverer to Power BI case study for a US municipal government (opens in new tab) in which its tool extracted the SQL behind 99 workbooks and 112 worksheets from a much larger pool of reports identified during assessment.

That example also shows the point of the inventory: the reports worth rebuilding were a small share of what existed. Extracted SQL tells us what each surviving worksheet asks the database for. It does not tell us whether the logic is right, so each query is read for its grain, its joins, and any hard-coded values before it becomes part of the model. Where a custom folder's SQL is genuinely the clearest expression of the rule, it can run as a native database query (opens in new tab) in Power Query, though we usually prefer a named view the database team owns.

Connectivity needs a check up front. Microsoft's Oracle database connector documentation (opens in new tab) lists its supported Oracle Database versions and the on-premises data gateway it needs for scheduled refresh. Older EBS databases that fall outside that list are better served by landing the required tables in a supported staging database first.

How is E-Business Suite security rebuilt?

This is the part of a Discoverer migration that should never be assumed. In an EBS-mode EUL, users sign in with an EBS username and responsibility, Business Area access is granted to those users and responsibilities, and many EBS views filter rows using the operating unit or ledger context the responsibility sets up at login. Power BI has none of that machinery, and ennVee's own write-up on migrating from Discoverer to Power BI (opens in new tab) notes that Business Area access security cannot be migrated directly.

So we treat security as a design task. First we document what each responsibility actually allows — which operating units, ledgers, inventory organisations or cost centres — and confirm it with the system owner. That becomes a security table of users and the values they may see, and a row-level security (opens in new tab) role filters the model against the signed-in user. Content-level access becomes workspace roles and app audiences. Views that depend on the EBS session context are queried through an account and filter we have verified, because run outside that context they can return no rows or rows nobody should see.

How is this different from an OBIEE migration?

Discoverer and OBIEE are different Oracle products, and the projects differ accordingly. Discoverer's metadata is the EUL inside the database and its logic is spread across folders, custom SQL and workbooks; the work is consolidation. OBIEE centralises its logic in a repository and a BI Server, so the work there is reading that repository — covered on our OBIEE to Power BI migration page. Some Oracle estates run both; when they do, we scope them as related but separate workstreams.

What does the first phase cost?

We scope the first phase as one business area and the workbooks people still use — typically a single department such as payables, procurement or general ledger. That is small enough to scope in hours before work starts, and it is typically sized to a Growth ($4,600) or Power ($8,000) block depending on how much consolidation and security work the area needs. The pilot and the work after it run on prepaid Flex hours that never expire — Starter ($2,500), Growth ($4,600), or Power ($8,000), with hourly work from $100/hour — so the next business area is a scoped task, not a new negotiation.

Cost follows the shape of the EUL more than the count of workbooks. Forty worksheets reading one well-built folder are a smaller job than ten worksheets on custom SQL folders with operating-unit security. You get an estimate in hours per deliverable, approve only what you want built, and unused hours stay banked. See Flex pricing.

How long does it take?

Individual reports typically ship within 3–5 business days of approval once the model is standing, and the migration is a sequence of those tasks rather than one big-bang cutover. The model and the security table come first, because every report after them gets cheaper. We recommend running Discoverer alongside Power BI for one full period close so users can compare both outputs on live data before the business area is switched off.

Who this is for

Finance, operations and IT teams on Oracle E-Business Suite whose day-to-day reporting still runs through Discoverer: an EUL only one administrator understands, Java and browser workarounds to keep Viewer running, an EBS or database upgrade blocked by reporting, or a backlog of Excel exports re-keyed every month. Published examples range widely in size: IT Convergence describes moving an aircraft parts supplier from Discoverer to Power BI (opens in new tab) — eleven Finance and Procurement reports — while the municipal example above began from thousands. It is a poor fit if you want every worksheet copied unchanged with no decisions made; that recreates the sprawl in a new tool.

Start with one Discoverer business area and the workbooks people still open, scoped in hours first.

Scope my Discoverer pilot →

What you get

  • A documented read of the business area in the EUL
  • A workbook inventory with rebuild, merge or retire calls
  • Extracted SQL for every surviving worksheet
  • A star-schema semantic model with named DAX measures
  • An access matrix and tested row-level security
  • Reconciliation against the Discoverer originals
  • Handover docs and a user walkthrough
1

business area per phase

3–5

business days per report

You

own everything

Start with one department, not the whole EUL. Comparing routes off several legacy tools? The migration to Power BI hub covers them side by side.

Migration scoping

Four questions that shape your scope estimate

These are the first things we ask before quoting hours for a move to Power BI. Answer what you know; “Not sure” is a fine answer.

How many reports need to move?

The report inventory tells you the true size of the job.

How many data sources feed those reports?

Sources shape the data model we rebuild: its tables, relationships and measures.

Do some people need to see only their own rows (row-level security)?

Who sees which rows is part of the logic we rebuild, not an afterthought.

Which month does your current license renew?

If the renewal is close, it sets the timeline.

Use these answers in my request →

Scope approved before any hours are used · Hours never expire

How it works

From one business area to reports people trust

  1. 1

    Inventory the EUL and the workbooks

    We document the business area you nominate — folders, custom SQL, joins, calculated items, conditions and access grants — list the workbooks and worksheets that use it with owners and usage, and extract the SQL for the ones that survive. You approve the list and the hours estimate before work starts.

  2. 2

    Rebuild the model, then the reports

    The folders become a star schema with shared dimensions and named DAX measures, the access matrix becomes row-level security, and surviving worksheets are rebuilt highest-value first — interactive pages for analysis, paginated reports for anything printed or exported.

  3. 3

    Reconcile, cut over, support

    Each rebuilt report runs beside its Discoverer worksheet on the same parameters and period, differences are explained, then we publish, set refresh and permissions, walk your users through it, and stay available on the hours you have left for the next business area.

Fair and square

Our promises, in plain English

Scope approved before any hours are used

Every request gets a scope estimate and the hours it needs before any work begins, so you approve the cost up front. Hours are deducted only for work you sign off on.

Hours never expire

Your prepaid hours are banked immediately, with no contracts and no recurring charges. Whatever you don’t use stays on your account, with no deadline to spend it by.

You own everything, in your tenant

You receive the report files, the semantic model, the DAX and the documentation, under your own Microsoft tenant and credentials. If you move the work in-house or to another partner, nothing is held hostage.

Refund in your first 4 hours

If you’re unhappy within the first 4 hours of your block, you get a full refund, no questions asked.

Straight answers. If a task is not a good fit for prepaid Flex hours, we will tell you rather than sell you something that will not serve you.

You work directly with Edward Pinela. The consultant who scopes your request is the same person who builds your data model, writes your DAX and designs your reports: a US-based, Microsoft-certified Power BI consultant with 20+ years on the Microsoft platform. No account managers in between, and nothing passed to an offshore team. About Edward

FAQ

Questions teams ask before they commit

Only in Sustaining Support. Under Oracle's Lifetime Support Policy, Premier Support for Discoverer 11gR1 ended in June 2014 and Extended Support ended on 30 June 2017. Oracle has said no new Discoverer patches, including for E-Business Suite Discoverer content, are created after that date. Existing patches and documentation remain available.

The SQL can be extracted automatically or by hand, and that is the most useful starting point. The layout, the EUL folder logic and the security cannot be imported as-is. Each surviving worksheet is rebuilt on a Power BI model and reconciled against the original, so the extracted SQL is a specification rather than the finished report.

Not one-to-one. Business Area access granted to EBS users and responsibilities has no direct Power BI equivalent, and EBS views that rely on the operating-unit context set at login behave differently under a service account. We rebuild the rule as row-level security from a security table and test it user by user before cutover.

No. Discoverer and OBIEE are different Oracle products. Discoverer keeps its metadata in End User Layer tables inside the database and generates SQL from folders and items; OBIEE uses a separate repository file and a BI Server. Some estates run both, in which case the two are scoped as related but separate workstreams.

One business area and the workbooks that people still open, usually a single department such as payables or procurement. That is small enough to scope in hours before work starts, large enough to prove the model, the security rule and the numbers through a real period close, and it leaves the rest of the EUL running until then.

Find out how much of your EUL still matters

Tell us which business area your team relies on most and roughly how many workbooks hang off it. We'll scope the inventory and the rebuild in hours, so you can see the real project before committing to it.

Free demo · Scope approved before any hours are used · Refund in your first 4 hours

Book a free demo

See what your Oracle Discoverer reporting would take

Tell us the task. We reply within one business day, and you get a scope estimate and the hours needed before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Scope approved before any hours are used. We don’t sell your information.

Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.

  • Prepaid hours from $100/hour — and they never expire
  • Senior-led delivery — 20+ years on the Microsoft platform
  • Typical 3–5 business day turnaround
  • Full refund if you’re unhappy in your first 4 hours

Related work

This page covers Oracle Discoverer specifically. If your Oracle reporting runs on a BI Server repository and Answers dashboards instead, the OBIEE to Power BI migration page covers that estate, and Brio-era Interactive Reporting documents are covered on the Hyperion Interactive Reporting and SQR migration page. Where many Discoverer worksheets are really fixed-layout list reports, the SSRS to Power BI migration page explains how paginated reports carry that kind of output into the Power BI service. If your estate spans several tools, the broader migration to Power BI service handles them on the same prepaid model. The rebuild itself is data modeling and DAX work, and teams standing up their first workspace often pair it with Power BI consulting for licensing and governance. Every task is scoped before work begins from your prepaid block of senior-led hours, and hours are deducted only for work you approve.

Book my free demo