The database and WebLogic licenses that come with EBS cover EBS itself and nothing else.
Oracle E-Business Suite is licensed mainly by user, module by module, with restricted-use database and middleware licenses that cover EBS itself. Most EBS licensing gaps come from how users are counted, modules switched on without licenses, and the restricted-use technology used beyond EBS. Our E-Business Suite reviews find those gaps before Oracle’s audit does.
2037Premier Support for EBS 12.2 runs through at least this year (Oracle, March 2026)
| Component | License |
|---|---|
| EBS modules | User metrics |
| Database, WebLogic or iAS running EBS | Restricted use |
| Custom applications and schemas on them | Full use |
The restricted-use grants are narrow and easy to breach without noticing.
Oracle E-Business Suite is a suite of programs for day-to-day business: finance, procurement, manufacturing, supply chain, human resources and customer management. It is one integrated suite on a single database schema, but it is modular in licensing and implementation, so every module is licensed on its own.
Module by moduleEach module you implement needs its own licenses. Implementing an additional module without them is one of the gaps we find most.
User metricsMost modules are licensed by user metrics, such as Application User, Self-Service Application User or Custom Suite User, depending on the module and the type of access.
Read-only users countEven read-only users typically need an Application User license. Oracle’s audit position is that any user with authorized access consumes a license.
Restricted-use technologyEBS comes with restricted-use Database and middleware (WebLogic or iAS) licenses for running EBS itself.
CustomizationsThe restricted use depends on not customizing those programs. Once modifications are made, you need full-use licenses.
| Part of the EBS estate | What it needs | The gap we find |
|---|---|---|
| EBS modules in use | Licenses for each module, on its user metric | Modules implemented without licenses, or the wrong metric |
| Users with access | A license per user, read-only included | Users counted the wrong way |
| Database and WebLogic or iAS running EBS | The restricted-use licenses included with EBS | Used for anything other than EBS |
| Custom applications on the EBS WebLogic or iAS | Full-use middleware licenses | Running on the restricted-use instance |
| Options and packs on custom schemas | Full Database Enterprise Edition licenses | Partitioning, Real Application Clusters, Advanced Compression or the Diagnostics Pack in use |
How Oracle’s license types differ, restricted use included: the six Oracle licensing models.
EBS non-compliance comes from two places: how the modules are used, and how the database and application server underneath them are used.
Indirect access happens when external systems, such as portals, mobile apps, integration platforms, BI tools or customer-facing applications, read or write EBS data without their users being licensed EBS users. Oracle’s position is that each human user behind them needs a license. The interpretation is contestable, but the exposure is real if the integration is not designed for it.
Both are Oracle-authorized cloud environments, and EBS runs on them under bring-your-own-license. The rules change when it moves: vCPU counting replaces processor counting, soft partitioning behaves differently, and a ULA for technology products may or may not permit cloud. Many EBS-on-AWS deployments we audit have under-licensed compute. Design the licensing first, and deploy second.
Oracle License Management Services validates the compliance position of your Oracle deployments, identifies license violations and corrects them through license purchases where it finds a gap. A formal audit goes through six stages.
1. NoticeA formal audit notice, or correspondence about measuring your deployment.
2. DeclarationYou declare your usage in an Excel spreadsheet.
3. Data collectionOracle’s tools gather installation and usage data.
4. AnalysisOracle analyzes the data it gathered.
5. FindingsOracle tells you how the audited products are deployed and used in your network.
6. Commercial proposalIf there is a gap, Oracle’s auditors work with its sales team on a proposal to close it through a negotiated purchase.
An EBS license review finds these gaps before Oracle’s audit does. See our Oracle license review and audit advisory.
EBS is not going away soon: Oracle has extended Premier Support for E-Business Suite 12.2 through at least 2037 (Oracle, March 2026). Oracle still encourages customers to move to Oracle Fusion Cloud, and the commercial pressure to move grows each year. Many of our clients are choosing to stay on EBS and optimize costs instead.
| Option | What to weigh |
|---|---|
| Stay on EBS and optimize | Premier Support for 12.2 runs through at least 2037. Many of our clients choose this, and optimize costs instead of migrating. |
| Migrate to Oracle Fusion Cloud | A different product, with different functionality, different metrics and, for many existing EBS users, a significantly higher run-rate cost. |
| Third-party support for EBS | Providers cover tax updates, regulatory patches, custom code and 24/7 incident response. You give up new Oracle patches and version upgrades, which suits customers on a stable release. |
Before the decision, we model the three-year and five-year cost of staying and optimizing, migrating to Fusion and migrating to OCI. Leaving Oracle support? Read about Oracle third-party support first.
Mainly on user metrics, such as Application User, Self-Service Application User or Custom Suite User, depending on the module and the type of access. EBS comes with restricted-use Database and middleware licenses for running EBS itself. Many compliance issues come from using those restricted-use components beyond what the license permits.
Oracle’s licensing team runs it in six stages, from the notice and your declaration to its findings and a commercial proposal. EBS audits focus on how users are counted module by module, modules switched on without licenses, and custom code on the restricted-use database and middleware.
Matching what you pay for to what you use: users checked module by module against the access actually granted, unlicensed modules switched off, custom code kept off the restricted-use technology, and a decision on staying on EBS, moving to Fusion or changing how you support it. EBS cost reduction comes from those steps, before the next renewal or audit.
Typically yes. Oracle’s audit position is that any user with authorized access consumes a license, whether they read or write. Some self-service and limited-function access can use lower-cost metrics, but the rules are narrow. We audit the user population module by module.
Custom applications running on the WebLogic or iAS instance included with EBS need full-use middleware licenses. Custom database schemas using full Database features, such as Partitioning, Real Application Clusters, Advanced Compression or the Diagnostics Pack, need full Database Enterprise Edition licenses.
External systems, such as portals, mobile apps, integration platforms, BI tools and customer-facing applications, reading or writing EBS data without their users being licensed EBS users. Oracle’s position is that each human user behind them needs a license. It is contestable, but the exposure is real if the integration is not designed for it.
Yes. Both are Oracle-authorized cloud environments, and EBS runs on them under bring-your-own-license. The licensing changes: vCPU counting replaces processor counting, soft partitioning behaves differently, and a ULA for technology products may or may not permit cloud. Design the licensing first, and deploy second.
Oracle has extended Premier Support for E-Business Suite 12.2 through at least 2037 (Oracle, March 2026). Oracle is encouraging customers to move to Oracle Fusion Cloud, but EBS is not going away in the near term.
Not always, and rarely on Oracle’s timeline. Fusion Cloud is a different product with different functionality, different metrics and, for many existing EBS users, a significantly higher run-rate cost. We model the three-year and five-year cost of staying and optimizing, migrating to Fusion and migrating to OCI before the decision is made.
Yes, for many EBS customers. Providers cover tax updates, regulatory patches, custom-code support and 24/7 incident response. The trade-off is no new Oracle patches or version upgrades, which suits customers already on a stable release with no major upgrade planned.
User populations module by module, licensing metrics checked against the access actually granted, the restricted-use Database and middleware components, customizations that breach restricted use, the cost of staying versus migrating, and the optimized future state. The output is a defensible compliance position and a clear cost reduction roadmap.
No. Rythium is independent and does not resell licenses or support, or earn income from Oracle or any support provider.
Tell us which release you run and what you are planning. We will tell you where an EBS estate like yours usually falls out of compliance, and what a review would cover.
Cookies on rythium.com
We use essential cookies to make this site work, and additional cookies to measure visits and our ads. You can reject the additional ones or choose which to keep. Privacy Policy