Discoverer and BI Publisher.

Oracle Discoverer and BI Publisher are reporting and document generation tools that ship alongside E-Business Suite, and that proximity creates one of the most common compliance traps in the EBS estate. The tools are licensed for restricted, embedded use within EBS, but organisations routinely extend them into standalone reporting against non EBS data, which requires full separate licensing. The gap between what is included and what is being used is exactly where Oracle audit findings concentrate, and the buyer side discipline is to understand the boundary before it becomes a bill.

1. The embedded use right.

EBS includes a restricted use licence for certain technology components, including reporting tools, that permits their use only in support of the licensed EBS application. This restricted use right lets customers run the standard EBS reports and document outputs without buying a full technology licence. It does not permit using the tools for general purpose reporting against other data sources.

The distinction matters because the restricted right is narrow. The moment the tool is used to report on data outside EBS, or to build custom reports that go beyond the application's own use, the restricted right no longer covers it and a full licence is required. Many organisations cross this line without realising it. The product context is on our Oracle E-Business Suite product page.

2. Where Discoverer exposure arises.

Oracle Discoverer was widely deployed for ad hoc reporting, and many EBS customers built extensive Discoverer environments. The exposure arises when those environments report against non EBS schemas, custom data marts, or integrated third party data. At that point the embedded right is exceeded and the use requires a standalone Business Intelligence licence.

Because Discoverer is now a legacy product, many customers have aging deployments that have drifted well beyond embedded use over the years. The buyer should map exactly what each Discoverer environment reports on, and retire or relicense any use that falls outside the EBS boundary, before an audit does it for them. We cover the audit dimension in our virtualization compliance note.

3. BI Publisher and document generation.

BI Publisher, formerly XML Publisher, generates documents and reports from EBS data and is included for that embedded purpose. As with Discoverer, the exposure arises when BI Publisher is used to produce reports from non EBS sources or as a general enterprise reporting platform. The embedded right covers the EBS use case, not enterprise wide deployment.

The common error is to treat BI Publisher as a free enterprise reporting tool because it came with EBS. It did not. The included right is restricted, and broad deployment against multiple data sources requires the full BI Publisher or Analytics licence. A buyer that has standardised on BI Publisher across the organisation should check carefully whether its use stays inside the embedded boundary.

4. How Oracle finds it in an audit.

Oracle audits of EBS estates routinely examine reporting tool use, because the tools leave traces of what they connect to. Connection strings, report definitions, and data source configurations reveal whether a tool is reporting on EBS data or on something else. An auditor that finds reports running against non EBS schemas has found a finding.

This is why the buyer should conduct its own review first, mapping every report and data source, so that it understands its position before Oracle does. A buyer that walks into an audit having already identified and resolved its reporting tool exposure removes one of the most common sources of unexpected findings. Our audit defense service conducts exactly this kind of pre-audit review.

5. Resolving exposure on the buyer's terms.

Where a review finds use beyond the embedded right, the buyer has options, and the best time to exercise them is before an audit, not during one. The use can be retired if it is no longer needed, migrated to a properly licensed platform, or relicensed through a negotiation conducted from a position of strength rather than under audit pressure.

The difference in cost between resolving exposure proactively and resolving it under an audit finding is large. An audit finding carries back support, list price assumptions, and no negotiating leverage. A proactive resolution is a normal commercial negotiation. The buyer that acts first controls the terms. See the broader strategy in our audit defense note and the database licensing deal page.

6. The migration consideration.

For buyers planning a move to Fusion Cloud, the reporting tool question changes shape. Discoverer in particular is a legacy product that will not move forward, and the migration is a natural moment to retire it and resolve any lingering exposure. The buyer should fold the reporting tool position into the broader migration negotiation rather than treating it as a separate problem.

Addressing reporting tool exposure as part of a planned migration, rather than as an audit surprise, lets the buyer roll it into a single negotiation with maximum leverage. See our Fusion Cloud migration note, the counting context in our user license counting note, and the full method in the Oracle Negotiation Playbook.

7. What disciplined buyers do.

• Understand the embedded boundary. Know exactly what the restricted use right does and does not cover.
• Map every report and data source. Identify any use that reports on non EBS data.
• Review before Oracle does. Find and resolve exposure proactively, not under audit pressure.
• Choose retire, migrate, or relicense. Resolve exposure on commercial terms while you have leverage.
• Fold it into migration. Use a Fusion move as the moment to retire legacy reporting exposure.

For the broader framework see our EBS negotiation pillar, the audit defense note, the audit defense service, the database licensing deal page, and the Oracle Audit Defense Handbook.