All topics
46 / 60
Reportingbeginner

Discoverer and Legacy EBS Reporting Tools

Understand the role of Oracle Discoverer as a legacy ad hoc query tool predating OTBI in the EBS ecosystem

Discoverer was the ad hoc query tool in older EBS implementations. Oracle desupported it years ago, and it is still running in places.

Discoverer's EUL is like an older library's card catalog system that translated a complicated warehouse of unlabeled boxes (raw schema) into simple, browsable subject categories for patrons — a valid and useful system in its time, but one modern libraries (OTBI, BI Publisher) have since replaced with more capable digital catalogs.

Key Concepts

1
How it worked. An End User Layer sat over the EBS schema, presenting business-friendly folders and item names instead of tables and columns.
2
    underlying:  RA_CUSTOMER_TRX_ALL joined to HZ_PARTIES joined to ...
    the EUL:     folder "Invoices" -- Invoice Number, Customer Name,
                 Amount
3
A business user dragged items into a worksheet. Discoverer generated the SQL.
4
Which is exactly what OTBI subject areas do. Same idea, different generation:
5
    Discoverer EUL      ->  OTBI subject area
    folders and items   ->  folders, dimensions and measures
    worksheets          ->  analyses
6
So the concept transfers directly. Somebody who designed EULs understands subject areas immediately, and the reverse holds.
7
Why it is still around. Reports work, users know them, and there is no business case for rebuilding dozens of them. Migration keeps not being the priority.
8
Why that is a problem worth naming. A desupported tool receives no security patches, and it is a browser-and-Java-dependent client, so it breaks when desktops are upgraded — with no fix available.
9
The risk is not that it stops working one day. It is that a browser update breaks it on a Tuesday and nobody can do anything about it.
10
What migration looks like. Discoverer worksheets fall into two groups:
11
    formatted, repeatable, distributed   -> BI Publisher
    genuinely ad hoc exploration         -> a current ad hoc tool
12
Most worksheets in a mature installation turn out to be the first kind — a query somebody built once and now runs monthly, which is a report rather than an exploration.
13
Where this appears in an interview. Usually to gauge experience with older installations. The useful answer is that you know what it was, that the EUL concept maps onto subject areas, and that being desupported is a reason to plan rather than to panic.
14
What the interviewer is probing.1. "What was Discoverer and what happened to it?" Probing: currency. Stalls: "It is current." Moves up: an ad-hoc query tool over EBS business areas, now desupported — remaining usage is a migration backlog, not a choice.
15
2. "What do you migrate Discoverer workbooks to?" Probing: the practical path. Stalls: "Nothing." Moves up: OBIEE or OTBI for ad-hoc analysis and BI Publisher for formatted output, depending on what each workbook actually does.
16
3. "What makes the migration harder than it looks?" Probing: experience. Stalls: "Nothing." Moves up: workbooks accumulate undocumented business logic in calculated items, and nobody knows which of the hundreds are still used.
17
4. "How would you scope such a project?" Probing: the method. Stalls: "Migrate everything." Moves up: usage data first — typically a small fraction are actively run, and the rest can be retired rather than rebuilt.
Use cases:discovererlegacy-reportingeulend-user-layer