Complete Oracle EBS Application Module List — All Modules by Product Family

Oracle EBS Overview and Architecture

Oracle E-Business Suite, commonly referred to as EBS, is Oracle's flagship integrated on-premise enterprise resource planning (ERP) suite. First developed in the late 1980s as Oracle Financials, and later evolving through Oracle Applications 10.7, 11i, 12.0, 12.1, and the current Release 12.2 (R12.2), EBS has grown into one of the most comprehensive integrated enterprise application platforms in existence. At its core, EBS is a collection of tightly integrated business applications sharing a common technology stack — the Oracle Application Object Library (AOL), Oracle Workflow, and Oracle Database — that enables seamless data sharing across modules.

The EBS architecture is built on a three-tier model: a database tier running Oracle Database (typically 12c or 19c for current deployments), an application tier running Oracle Application Server components, and a client tier accessed via a web browser. All EBS modules share the same underlying database schema, which is why data from Oracle Financials, Oracle HRMS, Oracle Supply Chain, and Oracle Projects can be reported in consolidated form without requiring separate integration middleware.

Oracle's official module count for EBS varies depending on how you classify components — Oracle documentation references approximately 280 application entries including core functional modules, shared service components, localisation modules for specific countries, and obsolete products that remain in the product register for historical support purposes. For practical purposes, the functionally distinct application modules number closer to 100 across the main product families described below.

Understanding your EBS module footprint is essential for three reasons: accurate licence compliance (you pay per module or per user for the modules you are licensed to use), effective support cost management (Oracle's 8% annual support fee escalation applies to all licenced modules regardless of usage), and effective cloud migration planning (each EBS module must be mapped to its Fusion Cloud equivalent before any migration timeline can be validated).

Oracle Financials Modules (FIN)

Oracle Financials is the original foundation of EBS and remains the most widely deployed product family. The Financials suite provides end-to-end financial management capabilities — from general ledger and multi-currency accounting through to accounts payable, accounts receivable, cash and treasury management, and fixed assets. Most organisations running EBS have at least Oracle General Ledger and Oracle Payables or Receivables deployed, even if they run other business areas on different platforms.

Supply Chain Management Modules (SCM)

Oracle's Supply Chain Management suite within EBS covers the full lifecycle from procurement through inventory management, order fulfilment, warehouse operations, and transportation. The SCM modules are among the most complex to licence correctly because they interact heavily with Manufacturing modules and share data objects — particularly inventory items and organisations — with several other product families.

Manufacturing Modules

Oracle Manufacturing modules within EBS cover discrete, process, and configure-to-order manufacturing environments. These modules are tightly coupled with Oracle Inventory and Oracle Cost Management, and organisations that run them typically have complex licensing arrangements because the modules are deployed across multiple manufacturing organisations with distinct site configurations.

Human Capital Management / HRMS Modules

Oracle Human Resource Management System (HRMS) within EBS is a comprehensive suite that manages the full employee lifecycle from hire to retire. HRMS modules are licensed using an employee-based user metric, making them distinct from other EBS modules that use application user counts. The HRMS suite integrates tightly with Oracle Payroll, which is often the most complex module in the suite due to country-specific payroll legislation requirements.

Oracle Projects Modules

Oracle Projects within EBS provides project accounting and management capabilities used by professional services organisations, government contractors, and capital-intensive industries. The Projects modules integrate with Oracle Financials for project cost and revenue accounting, and with Oracle Time and Labor for project timecard collection.

Customer Relationship Management (CRM) Modules

Oracle CRM modules within EBS cover sales force automation, service management, marketing campaign management, and customer interaction management. While many organisations have replaced EBS CRM with Salesforce or Oracle Fusion CX, a significant installed base continues to operate Oracle EBS CRM modules for field service, depot repair, and contract management functionality that remains deeply integrated with EBS Financials and Inventory.

Public Sector and Vertical Modules

Oracle offers a set of modules specifically designed for public sector organisations including government agencies, utilities, and educational institutions. These modules extend the core EBS functionality with public-sector-specific processes such as fund accounting, grants management, and case management.

Technical and Shared Services Modules

The EBS technical stack includes a set of shared service components that support all functional modules. These are not individually licensed products — they are part of the Oracle Applications infrastructure — but understanding them is essential for DBA teams managing EBS environments, particularly for audit response where Oracle LMS queries the technology stack configuration.

EBS Licensing Mechanics: What You Need to Know

Oracle EBS modules are licensed using two primary metrics: Application User and Full Use Processor. Application User licensing counts the number of named individuals authorised to use a specific EBS module. This is the most common metric for EBS functional applications and is distinct from Oracle Database Named User Plus — Application Users are counted separately from database users. A single person accessing three different EBS modules (for example, Oracle General Ledger, Oracle Payables, and Oracle Projects) is counted as three Application Users — one for each licensed module.

Processor licensing for EBS is less common but is used by organisations with very high user counts or where accurate user counts are impractical to maintain. Under the processor model, you licence the servers running EBS by processor (using Oracle's Core Factor Table for the calculation) and receive an unlimited user right for that module on those servers. Processor licensing becomes cost-effective relative to Application User licensing when user counts exceed approximately 500 per licensed module, though the exact break-even depends on the server configuration and the specific module.

Oracle also licences some EBS modules as suites. The Oracle E-Business Suite Custom Application Suite (CAS) allows organisations to licence a custom bundle of EBS modules for a specific business unit or use case, typically at a lower per-unit cost than individual module licensing. CAS arrangements are common in ULA (Unlimited Licence Agreement) and PULA (Perpetual Unlimited Licence Agreement) contexts, where the ULA covers a defined set of EBS products for an unlimited deployment period.

Support costs for all licenced EBS modules are calculated at 22% of net licence value per year and increase by 8% annually. The matching service levels clause applies across the EBS suite — if you maintain support on any EBS module from a given product family, Oracle requires you to maintain support across all licences for that family. This is a material consideration when rationalising the EBS licence estate prior to a cloud migration.

EBS to Oracle Fusion Cloud Module Mapping

As organisations plan Oracle cloud transitions, one of the first tasks is mapping current EBS module usage to Oracle Fusion Cloud equivalents. The mapping is not always one-to-one — some EBS modules map cleanly to a single Fusion Cloud product, while others span multiple Fusion Cloud applications or have been redesigned with materially different process flows.

• Oracle GL, AP, AR, FA, CM → Oracle Fusion Financials: The core financials modules map directly to Oracle Fusion Financials Cloud. Fusion provides enhanced capabilities including AI-powered journal suggestions and automated reconciliation, but the data model and chart of accounts structure must be redesigned during migration.
• Oracle Purchasing, iProcurement, Sourcing → Oracle Fusion Procurement: Oracle Fusion Procurement covers the procure-to-pay process. EBS sourcing and procurement customisations require significant re-engineering in the Fusion environment.
• Oracle Order Management, Advanced Pricing → Oracle Fusion Order Management: Fusion Order Management includes a redesigned pricing engine. Complex pricing rules from Oracle Advanced Pricing must be rebuilt using Fusion's pricing architecture.
• Oracle HRMS, Payroll → Oracle Fusion HCM: Oracle Fusion HCM is the primary cloud destination for EBS HR and Payroll. Country-specific payroll legislation support in Fusion HCM varies by region — verify that Fusion Payroll supports your payroll requirements before committing to this migration path.
• Oracle Projects → Oracle Fusion Project Management: Oracle Fusion includes Project Management, Project Control, and Project Billing modules. The project structure and billing rules from EBS must be carefully mapped and often restructured during migration.
• Oracle Manufacturing → Oracle Fusion Manufacturing: Fusion Manufacturing supports discrete and process manufacturing. Organisations with complex EBS Manufacturing environments — particularly those with extensive WPS scheduling or shop floor management — should conduct detailed functional fit assessments before migration.
• Oracle EBS CRM → Oracle Fusion CX: Most EBS CRM functionality has been superseded by Oracle Fusion CX Cloud or Salesforce. Few organisations migrate EBS CRM directly to Fusion CX — the typical approach is to evaluate whether Fusion CX or a third-party CRM better meets current requirements.

For a full Fusion Cloud module reference and migration planning support, visit the Oracle Knowledge Hub or speak to the Redress Compliance Oracle advisory team. Our advisors have guided over 40 Oracle EBS to Fusion Cloud migration assessments and can provide an independent view of migration readiness, licensing transition strategy, and commercial negotiation approach.

Oracle EBS Support Lifecycle and Cost Trajectory

Understanding Oracle EBS support commitments is essential for any organisation managing its EBS estate. Oracle has committed to providing Premier Support for Oracle EBS Release 12.2 through December 2031, with an announced path to Sustaining Support after that date. Sustaining Support provides tax, legal, and regulatory updates on a best-efforts basis but does not include new bug fixes or new legislative updates beyond those already committed.

The financial trajectory of EBS support deserves careful management. Oracle's standard support fee is 22% of the net licence value per year, and Oracle applies an 8% annual escalation to that amount at each renewal cycle. For organisations with large EBS estates, this compounding cost increase means that support fees on a $5 million EBS licence portfolio will exceed $1.3 million annually within three years, and will continue increasing regardless of whether the underlying modules are in active use.

Three specific situations create avoidable support cost exposure for EBS customers. First, organisations that retain EBS licences for modules they have already decommissioned continue to pay 22% support on redundant assets. An internal entitlement review against actual deployment will typically identify candidates for support termination that represent 10–20% of total EBS support spend. Second, organisations in the process of migrating to Oracle Fusion Cloud may be able to negotiate a shelving rights clause, which allows EBS on-premise licences to be placed on a reduced-cost or zero-cost support arrangement during the transition. This must be negotiated proactively — Oracle does not offer it automatically. Third, organisations approaching Oracle's Q4 fiscal year-end (March–May window) have the strongest negotiating leverage to secure multi-year support pricing commitments that limit the annual 8% escalation.

Common EBS Licensing Errors to Avoid

Several recurring errors appear when organisations manage their EBS licensing without independent advice. Awareness of these patterns helps organisations avoid the most common and costly compliance exposures.

• Licensed module count errors. EBS licensing is often agreed at a product family level rather than individual module level. When organisations later expand their EBS deployment into additional modules within a licensed family, they sometimes assume this is covered — when in fact the specific modules activated must be reconciled against the original order documentation. Every module activated in EBS should be validated against entitlement, not assumed.
• Named User Plus minimum violations. Oracle's Named User Plus metric requires a minimum of 50 NUP licences per processor for most EBS application modules. Organisations with small EBS user populations in processor-licensed environments frequently fail to meet this minimum, creating an unlicensed position even where the actual user count is fully covered.
• Application User metric boundary issues. The Application User metric, commonly used for EBS modules, is defined as a named user authorised to use the applicable programmes. It applies to all users across all entities in the enterprise, not just those in a single legal entity. Organisations that deploy EBS modules selectively across some but not all subsidiaries often undercount their Application User requirement when the licence is checked against the full group footprint.
• Expired ULA certification gaps. Organisations that previously held an Oracle ULA covering EBS-related technology products — particularly Oracle Database Enterprise Edition — must have certified correctly at ULA expiry. Any EBS technology stack running on Oracle Database post-ULA expiration must be covered by the certified licence quantities, not assumed to be inherited from the ULA period.

If you are undertaking an EBS audit, preparing for a Fusion Cloud migration, or managing an EBS licence renewal negotiation, contact Redress Compliance for an independent licence review. Our team includes former Oracle LMS auditors who have worked across hundreds of EBS environments and can identify exposure and opportunity that internal teams and Oracle-aligned advisors typically miss.