How Oracle EBS Licensing Works: The Foundation
Oracle E-Business Suite (EBS) is a comprehensive enterprise resource planning suite that covers financials, procurement, human resources, supply chain, manufacturing, order management, customer relationship management, and more. Each of these functional areas is a separately licensed component — and each may use a different licence metric.
The fundamental principle of EBS licensing is that you licence specific modules for specific users or deployment configurations, and your licence entitlement determines who can access what. Oracle's audits focus on whether your actual user population and usage patterns match the licences you hold. Getting this alignment right — neither over-licensed nor under-licensed — is the goal of good EBS licence management.
The Application User Metric: How It Works and How Oracle Counts
The most widely used licence metric for Oracle EBS is the Application User metric. An Application User is any individual who is authorised to access the licensed EBS application, regardless of whether they are currently using it. Authorisation is typically defined by the assignment of an EBS responsibility — if a user account has an active responsibility for an EBS module, that user is counted for that module's licence.
Oracle's counting methodology has several implications that EBS administrators and compliance teams frequently misunderstand:
- Access, not usage, determines the count. A user who has not logged into EBS for 18 months but still has active responsibilities is counted as a licensed user. Oracle does not reduce the licence obligation based on inactivity unless the user account is formally deactivated.
- Shared accounts are counted per real person. Some organisations use generic or shared EBS user accounts (e.g., "accounts_payable_user"). Oracle counts each individual who uses such an account as a separate licensed user. This is one of the most frequently discovered audit findings in EBS environments.
- Every active responsibility creates a licence obligation. If a user has responsibilities in three different EBS modules, all three modules must be separately licensed for that user — unless the modules are included in a bundle that covers all three.
- Read-only access is not exempt. Oracle defines a "Read-Only User" for some EBS modules as a separate, lower-cost licence category. However, even read-only access to a licensed module requires a licence — typically at a lower price point than a full Application User, but not free.
The Processor Metric for EBS
Some EBS modules and configurations are licensed by processor rather than by named user. Processor licensing is typically used for externally facing EBS deployments — for example, an Oracle iStore deployment serving external customers, or an EBS portal with a large number of anonymous or external users. Under processor licensing, an organisation licences the EBS servers by CPU (using Oracle's Core Factor Table) and can then support an unlimited number of users.
Processor licensing can be economically advantageous for high-volume, externally facing EBS deployments. For internal-use EBS deployments with a defined user population, Application User licensing is almost always the appropriate metric. Organisations that choose processor licensing for internal EBS deployments often find that they are over-paying relative to the user-count alternative.
Enterprise Metrics: Employees, Revenue, and Order Volume
Several Oracle EBS modules use enterprise-level metrics rather than per-user or per-processor counts. The most common enterprise metrics in EBS are:
- Employees: Oracle Human Resources modules are typically licensed based on the total number of employees in the organisation, not the number of HR system users. This is a significant distinction — a company with 10,000 employees using Oracle HR needs 10,000 employee licences regardless of how many HR staff actually use the system.
- Revenue: Some Oracle EBS finance-related modules have historically been licensed based on annual company revenue, creating an automatic escalation mechanism tied to business growth.
- Order volume: Oracle Order Management can be licensed based on the number of orders processed annually, which can create non-linear cost growth as transaction volumes increase.
Enterprise metrics are often overlooked in compliance reviews because they do not appear in the standard user access reports that EBS administrators typically review. An organisation that has grown significantly since its EBS purchase may be out of compliance on employee-metric modules even if its Application User count appears correct.
EBS Bundling: What Is and Is Not Included
Oracle sells EBS modules both individually and in bundles. The most common EBS bundle is the Oracle E-Business Suite Financials — a package that includes Accounts Payable, Accounts Receivable, General Ledger, Fixed Assets, Cash Management, and Purchasing in a single bundled licence. Buying the bundle is typically less expensive than buying each module separately.
The compliance risk with bundled licences is that customers often do not have a complete inventory of which modules are included in their bundle versus which require separate licences. When users access EBS functionality that is not covered by their bundle — for example, using Oracle Projects in an environment licensed only for EBS Financials — a compliance gap exists.
Oracle's LMS collection scripts identify module usage through the EBS application audit trails and responsibility assignment records. If a user has an active responsibility for a module that is not included in the licensed bundle, Oracle's auditors will classify this as unlicensed use.
EBS Support Costs: The 22% Annual Fee and 8% Annual Increase
Oracle EBS support — officially called Software Update Licence and Support (SULS) — is priced at 22% of the net licence value. This covers access to Oracle's support portal, patch downloads, version updates, and technical assistance. The 22% fee applies to the perpetual licence value established at the time of purchase and increases at 8% per year at each renewal.
The compounding effect of the 8% annual increase is substantial. An EBS support contract that was $1 million per year in 2018 would cost approximately $1.71 million per year in 2026 — an increase of over 70% in eight years. For large EBS deployments with multi-million-dollar annual support bills, the 8% escalation is often the single largest driver of IT budget growth year over year.
Managing EBS support costs requires a multi-pronged strategy: negotiating support fee caps at renewal, exploring third-party support providers for EBS on-premises, rationalising the EBS licence footprint by eliminating licences for unused modules, and timing any Oracle commercial engagement (including cloud migration discussions) to maximise negotiating leverage.
Is your EBS licence position optimised?
Our advisors have helped organisations reduce Oracle EBS licensing costs by 20–40% through licence rationalisation, metric optimisation, and renewal negotiation.Legacy EBS Licence Metrics: Concurrent Users and Professional Users
Organisations that purchased Oracle EBS before approximately 2010 may hold licences under legacy metrics that are no longer sold. The most common legacy metrics are Concurrent User licences (a pool of simultaneous users) and Professional User licences (an older named-user model). These legacy licences remain valid and can be used on current EBS versions. However, if additional licences are needed, Oracle requires new purchases under current metrics — the older concurrent or professional user models are no longer available for incremental purchases.
Managing a mixed metric environment — some legacy concurrent users, some newer Application Users — requires careful attention during audits to ensure that each user group is mapped to the correct metric and that the totals align with the licence entitlements on the CSI (Customer Support Identifier) record.
Strategies to Optimise Your EBS Licence Position
EBS licence optimisation is one of the highest-return activities available to Oracle customers. The four most impactful strategies are:
- Conduct a user responsibility audit. Identify every active EBS user account and the responsibilities assigned to it. Remove inactive users, eliminate unnecessary responsibility assignments, and ensure that user counts match current licence entitlements. This is the fastest path to reducing the EBS licence footprint.
- Review enterprise metric compliance. Verify that employee counts, revenue figures, or order volumes used for enterprise-metric modules still align with your current licence quantities. Address gaps proactively rather than having them discovered during an audit.
- Challenge bundling assumptions. Review your EBS licence order history to understand exactly which modules are included in your bundles versus individually licensed. If users are accessing modules outside their licensed scope, either restrict access or procure the appropriate licences.
- Negotiate support fee caps at renewal. The 8% annual support increase is contractual but negotiable at renewal, particularly for customers with renewal leverage. Multi-year price caps, cloud migration credits, and alternative support structures are all available to customers who negotiate rather than simply renewing.
Frequently Asked Questions
Does Oracle count users who have not logged in recently?
Yes. Oracle counts any user with active EBS responsibilities as a licensed user, regardless of their last login date. The only way to exclude a user from the licence count is to formally deactivate their account and remove their responsibilities.
Are EBS read-only users cheaper to licence?
Oracle provides a Read-Only User licence for certain EBS modules at a lower price point than a full Application User licence. However, read-only users are not free — they require their own licence category. Verifying that your read-only users are correctly licensed under the appropriate lower-cost metric is a common source of licence cost savings.
Can I switch from Application User to Processor licensing?
Licence metric changes in Oracle EBS require a commercial agreement with Oracle — you cannot simply switch metrics unilaterally. However, if processor licensing would result in a lower total cost for your configuration, this is worth exploring in a renewal or renegotiation context.
What is Oracle's CSI and why does it matter for EBS licensing?
Oracle's Customer Support Identifier (CSI) is the official record of your Oracle licences. During an audit, Oracle reconciles the actual EBS deployment against the CSI. Discrepancies between what is deployed and what is on the CSI — in either direction — create audit exposure. Maintaining an accurate, up-to-date CSI that reflects your actual licence position is a fundamental compliance requirement.