The short answer: Oracle E-Business Suite is licensed mainly by user, module by module, with restricted-use database and middleware licenses that cover EBS itself and nothing else. Most EBS compliance gaps come from how users are counted, modules switched on without licenses, and the restricted-use technology being used beyond EBS. An EBS license review finds those gaps before Oracle’s audit does.
Why E-Business Suite licensing is hard to control
Uncontrolled license usage poses a significant financial risk for Oracle E-Business Suite organizations. Maintaining control requires deep insights into user activity across all the multiple instances of the deployed EBS application.
The challenge is that complexity reigns supreme. With potentially thousands of users, functions, processes, and intricate role-based permissions, managing license compliance becomes an uphill battle.
Non-compliance in E-Business Suite licensing arises from the use of the different EBS modules, and from the use of the underlying database and application server (iAS or WebLogic).
What is Oracle E-Business Suite?
Oracle E-Business Suite is a suite of software programs that organizations use to manage day-to-day business activities, such as finance, procurement, manufacturing, supply chain, human resources and customer management.
Oracle E-Business Suite Architecture
- Architecturally an integrated suite yet modular in licensing & implementation
- Is designed around a single database schema (data structure)
- Ensures information used across the company is normalized.
- Ensures that a company uses common definitions for products, people, and processes across the organization.
- Enables user experience to be common across the organization when using the software application.
How an Oracle audit of E-Business Suite runs
Oracle License Management Services is the established authority on Oracle licensing policy. Their job is to validate the compliance position of your Oracle deployments, identify license violations and correct them by purchase of licenses where necessary.
A formal Oracle LMS Audit goes through the following stages:
- A formal notice for an audit or a correspondence discussing the measurement of your deployment.
- A declaration of usage by the customer through the update of an MS Excel spreadsheet.
- Deploy tools to gather installation and usage data.
- Analysis of the gathered usage data.
- Inform you regarding the deployment & usage of audited products in your network.
- In case of non-compliance, collaborate with the sales team internally within Oracle to submit a commercial proposal that will correct the license gap through a negotiated purchase.
E-Business Suite license compliance issues
There are two kinds of license compliance issues related to E-Business Suite:
- Issues related to over-usage or wrong usage of EBS modules.
- Issues related to using Oracle Technology products with E-Business Suite.
Usage compliance issues
- Using more users than were bought.
- Counting Application Users the wrong way
- Cloning production systems into test and development
- End-dating of users.
- Implementing additional modules
- Using wrong metrics
- Incorrect normalization of roles and responsibilities
Technology licensing issues
- Using the restricted-use database and middleware licenses that come with EBS for anything other than EBS itself.
- Running custom applications on the EBS WebLogic or iAS instance, which needs full-use middleware licenses.
- Using Database options and packs, such as Partitioning, Real Application Clusters, Advanced Compression or the Diagnostics Pack, on custom schemas without full Database Enterprise Edition licenses.
- Moving EBS to AWS or Azure without recounting licenses under the cloud rules.
Frequently Asked Questions
How is Oracle E-Business Suite licensed?
EBS is licensed primarily on user metrics (such as Application User, Self-Service Application User or Custom Suite User) depending on the module and access type. EBS comes with restricted-use Database and middleware licenses for running EBS itself. Many compliance issues arise when those restricted-use components are used without following licensing permissions.
Will Oracle continue to support E-Business Suite, and for how long?
Oracle has extended Premier Support for E-Business Suite 12.2 through at least 2037 (Oracle, March 2026). EBS is not going away in the near term. That said, Oracle is actively encouraging customers to migrate to Oracle Fusion Cloud, and the commercial pressure to move increases each year. Many of our clients are choosing to stay on EBS and optimize costs instead.
Should we migrate from EBS to Oracle Fusion Cloud?
Not always, and rarely on Oracle’s timeline. Fusion Cloud is a different product with different functionality, different metrics, and significantly higher run-rate cost for many existing EBS users. We model the 3-year and 5-year TCO of stay-and-optimize versus migrate-to-Fusion versus migrate-to-OCI for every client before the decision is made.
What EBS customizations trigger additional licensing?
Custom applications running on the EBS-included WebLogic or iAS instance trigger full-use middleware licenses. Custom database schemas using full Database features (Partitioning, RAC, Advanced Compression, Diagnostics Pack) trigger full Database EE licensing. The restricted-use grants are narrow and easy to breach inadvertently.
How do we count read-only and reporting users in EBS?
Even read-only users typically require an Application User license. Oracle’s audit position is that any user with authorized access, regardless of read versus write, consumes a license. 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.
What is indirect access in EBS, and when does it become a licensing issue?
Indirect access happens when external systems (portals, mobile apps, integration platforms, BI tools, customer-facing applications) read or write EBS data without the end-users being licensed EBS users. Oracle’s position is that each underlying human user requires a license. The interpretation is contestable, but exposure is real if not designed correctly.
Can we run E-Business Suite on AWS or Azure?
Yes. Both are Oracle-authorized cloud environments and EBS runs on them under BYOL. But the licensing rules change: vCPU counting replaces processor counting, soft partitioning behaves differently, and ULA technology products contracts may or may not permit cloud. Many EBS-on-AWS deployments we audit have under-licensed compute. Design the licensing first, deploy second.
Is third-party support viable for E-Business Suite?
Very viable. Third-party EBS support has matured into a credible market, with providers covering 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 the many EBS customers who are already on a stable release and don’t plan major upgrades.
What is the typical scope of Rythium's EBS license review?
We review user populations module by module, validate licensing metrics against the access actually granted, audit the restricted-use Database and middleware components, identify customizations that breach restricted use, model TCO of stay-versus-migrate options, and document the optimized future state. The output is a defensible compliance position and a clear cost reduction roadmap.
An audit letter, a renewal quote or a ULA end date on your desk? We check what Oracle, Microsoft, IBM or Broadcom is claiming, work out what you owe under your contract, defend against audits, and negotiate the rest down.