Understanding EBS Module Licensing Architecture
Oracle EBS is not a single product — it is a collection of modules, each addressing a specific business function. Some modules are available individually, others only as part of bundles. Each module has its own licence metric, which may differ from the metrics used by adjacent modules. Understanding this module-level complexity is essential for accurate compliance management.
The EBS licence structure has three key dimensions: the module (which business function is being licensed), the metric (how the licence is counted — per user, per employee, per processor, per revenue unit), and the scope (how Oracle defines what use is covered under the licence). All three dimensions must be correctly understood and managed to avoid compliance gaps.
Oracle EBS Financials Module Licensing
Oracle EBS Financials is the most widely deployed module family in the EBS suite and covers General Ledger, Accounts Payable, Accounts Receivable, Fixed Assets, Cash Management, and related sub-ledger accounting. The EBS Financials bundle is typically licensed per Application User, at approximately $4,595 per user at Oracle's list price. The minimum purchase is typically five users.
Key compliance issues in Oracle Financials licensing include: over-assignment of AP or AR responsibilities to users who only need inquiry access (which often qualifies for a Read-Only User licence at a lower price), and access to Oracle Advanced Collections or Oracle Loans — modules that sit outside the standard Financials bundle and require separate licences. Organisations that enable these modules without checking bundle coverage frequently discover gaps during audits.
Oracle iExpenses, the employee expense reporting module, is separately licensed based on the number of employees who submit expense reports — not just the finance team who approves them. This employee-count metric catches many EBS Financials customers by surprise, particularly when iExpenses is rolled out organisation-wide as an employee self-service tool.
Oracle EBS Procurement Module Licensing
Oracle Purchasing (EBS Procurement) is licensed at approximately $4,595 per Application User — the same price point as Financials. The Procurement module covers purchase orders, requisitions, supplier management, and sourcing. Oracle iProcurement, the self-service requisitioning portal, uses a different metric: it is licensed per Application User who submits requisitions through the portal, not just the procurement specialists who manage the process.
For large organisations that have deployed iProcurement broadly to allow all employees to raise purchase requests, the Application User count can grow very large very quickly. An organisation with 500 procurement users but 5,000 iProcurement requesters needs to licence all 5,500 users — a significant uplift from what the procurement team count alone would suggest.
Oracle Sourcing and Oracle Supplier Network are separately licensed advanced procurement modules that require individual licence purchases beyond the standard Purchasing bundle. These are frequently activated by procurement teams without a formal licence review, creating compliance exposure that only surfaces during an LMS audit.
Oracle EBS Human Resources Module Licensing
Oracle Human Resources (Core HR) uses the Employee metric — the total number of employees in the organisation — rather than the number of HR system users. The list price for Core HR is approximately $185 per employee. For a company with 10,000 employees, this represents $1.85 million in licence value, with an annual support charge of approximately $407,000 (22%), increasing at 8% per year.
The HR module family extends well beyond Core HR. Oracle Payroll, Oracle Learning Management, Oracle Self-Service HR (for employee self-service), Oracle Performance Management, and Oracle Recruiting are separately licensed modules, each with its own metric. Oracle Payroll is typically licensed per employee on the payroll. Oracle Self-Service HR may be licensed based on all employees who access the portal. When organisations deploy the full HR module family without careful licence planning, the cumulative per-employee cost often significantly exceeds initial budget projections.
A specific compliance challenge in HR licensing is workforce expansion. If a company licensed Core HR for 5,000 employees in 2019 and now employs 8,000, the employee-metric licences purchased in 2019 do not automatically cover the additional 3,000 employees. Oracle's auditors will compare the current employee count against the licensed quantity on the CSI and raise a claim for the shortfall.
Oracle EBS Supply Chain Module Licensing
Oracle EBS Supply Chain encompasses a broad range of modules including Inventory Management, Order Management, Shipping, Manufacturing, Advanced Supply Chain Planning, and Warehouse Management. These modules collectively manage the physical flow of goods from supplier to customer, and their licensing structure reflects this broad scope.
Oracle Inventory Management is licensed per Application User. Oracle Warehouse Management (WMS) can be licensed per processor for high-volume operations with many warehouse staff. Oracle Advanced Supply Chain Planning (ASCP) is a separately licensed module with its own pricing distinct from the basic Inventory module. Organisations that have deployed ASCP as part of their EBS supply chain optimisation frequently discover that their EBS bundle does not include ASCP, requiring a separate licence purchase.
A common audit finding in supply chain environments is the use of Oracle Work in Process (WIP) or Oracle Bills of Material (BOM) by manufacturing teams without a separate licence for the Oracle Manufacturing module family. These modules are included in the Oracle Manufacturing bundle but are outside the scope of the basic Inventory or Order Management licences. Responsibility assignments in EBS for WIP or BOM functions without the appropriate module licence creates an audit exposure.
Not sure which EBS modules are properly licensed?
Our EBS module licence reviews identify unlicensed usage and over-licensing across your entire EBS functional footprint.Oracle EBS Order Management Module Licensing
Oracle Order Management (OM) covers the order-to-cash process — order entry, order fulfilment, shipping, billing, and returns. Order Management is licensed per Application User, typically at approximately $4,595 per user. Oracle iStore, the web-based customer ordering portal, may be licensed per processor for high-volume, externally facing deployments.
A specific complexity in Order Management licensing is the relationship between OM and Oracle Configurator. Oracle Configurator — used for configuring complex, customisable products — is a separately licensed module. Organisations that use Configurator as part of their order entry process without a separate Configurator licence frequently incur audit findings. The risk is elevated because Configurator usage often scales with order volume rather than user count, meaning the exposure can be substantial even if the number of direct users is small.
Oracle EBS Projects Module Licensing
Oracle Projects — encompassing Project Costing, Project Billing, Project Management, and Project Analytics — is licensed per Application User at approximately $4,595 per user. The Projects module is commonly deployed alongside Financials for professional services organisations, government contractors, and engineering firms that need to track costs and revenue by project.
Oracle Project Resource Management, used for resource scheduling and capacity planning, is a separately licensed capability. Oracle Grants Management, used by non-profits and research institutions to manage grant-funded projects, is also separately licensed. Both are frequently deployed without a separate licence review by organisations that assume they are included in the base Projects bundle.
Oracle EBS Shared Application Technology
Beyond the functional modules, Oracle EBS includes shared technology components — Oracle Application Object Library (AOL), Oracle Workflow, Oracle Alert, Oracle XML Publisher (BI Publisher), and Oracle General Ledger sub-ledger accounting. These shared technology components are covered by the EBS application licences and do not require separate purchase.
However, organisations that deploy Oracle BI Publisher independently — outside of EBS, for non-EBS reporting — need a separate BI Publisher licence. Similarly, Oracle Workflow deployed for non-EBS processes requires a standalone licence. The shared nature of these technology components means that compliance teams must clearly document which deployments are in scope for EBS restricted-use coverage and which require additional licences.
Annual Support Costs Across the EBS Module Portfolio
The annual support cost for Oracle EBS is 22% of the net licence value, increasing at 8% per year. For a typical mid-market EBS deployment with Financials, Procurement, HR, and Supply Chain modules, annual support often represents the largest single line item in the Oracle budget — frequently exceeding $500,000 per year for mid-sized organisations and several million dollars for large enterprises.
Strategies for managing EBS module support costs include: rationalising the module footprint by eliminating licences for modules that are no longer actively used, negotiating support fee caps at renewal, exploring third-party support providers for on-premises EBS, and using Oracle's fiscal Q4 (March–May) window to negotiate commercial adjustments with maximum leverage.
Frequently Asked Questions
Do all EBS modules use the Application User metric?
No. EBS modules use a variety of metrics depending on their function. Core HR is priced per employee. Payroll is priced per employee on payroll. External-facing portals may be priced per processor. Order Management and Financials are typically per Application User. Each module must be assessed individually to determine the correct metric.
Are all EBS modules included in a single bundle licence?
No. Oracle sells various EBS bundles (e.g., EBS Financials, EBS Manufacturing) that include specific modules, but many modules are sold individually. Users who access modules outside their licensed bundle create compliance exposure. A full licence inventory review is essential to confirm bundle coverage versus individual module licences.
What is a Read-Only User licence in Oracle EBS?
Oracle provides a Read-Only User licence for certain EBS modules at a lower price than a full Application User licence. A Read-Only User can view data but cannot enter transactions. This licence category is commonly applicable to managers and executives who access EBS dashboards or reports but do not perform data entry. Correctly classifying users as Read-Only versus full Application Users is a significant licence cost optimisation opportunity.