Why EBS Licensing Compliance Drifts — and How to Reset It
Oracle E-Business Suite licence compliance degrades over time through three structural mechanisms. First, system integrators and DBAs activate EBS modules during implementation and upgrade projects without checking whether the modules are licensed — creating a gap between what Oracle is contracted to supply and what is actually running. Second, EBS's Named User Plus metric requires counting every authorised user, not active users — and user counts grow through organisational change, acquisition, and employee additions without a concurrent licence review. Third, Oracle's GLAS team actively targets EBS deployments approaching support renewal, using audit findings to increase renewal commercial terms.
The 20 checks below address all three mechanisms. They are organised to move from the foundational contract review through module compliance, user metric accuracy, and support strategy, ending with audit preparation governance.
Work through each check in sequence. High Risk items represent conditions where non-compliance creates material financial exposure. Medium Risk items affect cost modelling and renewal negotiation position. Low Risk items are governance hygiene checks that strengthen the overall compliance posture.
01Has the original Oracle EBS licence agreement been reviewed to produce a definitive list of licensed modules — cross-referenced against Oracle's current module-to-product mapping for the EBS version deployed?High Risk
Expert NoteOracle EBS contracts reference Oracle product names that may not directly correspond to the EBS module names visible in the application. Oracle's product naming conventions have changed across contract generations (pre-2010, 2010-2018, post-2018), and a module named "Oracle Payables" in an older contract may correspond to "Oracle Accounts Payable" in current Oracle licensing terminology. An EBS licence agreement review requires mapping every contracted product against Oracle's current EBS module product catalogue to produce an authoritative list of what is licensed. This mapping exercise frequently reveals both unlicensed modules in use and licensed modules not deployed — the second category creates negotiation leverage at renewal.
02Has the EBS module activation been audited using Oracle's fnd_product_installations or equivalent query to identify every enabled module — regardless of whether it was intentionally activated?High Risk
Expert NoteOracle EBS modules are activated at the database level, not through user interface configuration, and the activation record persists regardless of whether the module is used. The query SELECT APPLICATION_SHORT_NAME, STATUS FROM FND_PRODUCT_INSTALLATIONS WHERE STATUS = 'I' reveals every installed (activated) module in the EBS instance. This is the exact query Oracle's GLAS team runs when conducting an EBS audit. Cross-reference the installed module list against the contracted module list — any installed module not in the contract is an unlicensed module. Pay particular attention to modules activated as dependencies during EBS upgrade projects: Oracle's upgrade scripts sometimes activate modules as prerequisites without explicit customer request.
03For EBS modules enabled as technical dependencies of licensed modules, has legal advice been obtained on whether Oracle requires separate licensing for dependency-activated modules that are not directly accessed by users?High Risk
Expert NoteOracle's GLAS team takes the position that any activated EBS module requires licensing, regardless of whether it was enabled intentionally or as a technical dependency. This position is commercially aggressive and contested by independent Oracle licensing specialists: a module that is technically enabled but provides no user-accessible functionality may not require licensing under a strict reading of Oracle's contract language. However, without an independent legal opinion specific to the EBS contract version and the modules in question, this risk cannot be safely assumed away. Obtain legal advice before an audit is initiated — not after Oracle has identified the module as unlicensed, at which point negotiating position is materially weaker.
04Has Oracle E-Business Suite Global Human Resources been assessed separately — as it is frequently activated as a dependency of other HR and payroll modules but requires its own Named User Plus licence?High Risk
Expert NoteOracle HRMS (Human Resources Management System) modules in EBS are structured hierarchically, with Oracle Global HR as the foundation module upon which Oracle Payroll, Oracle Time and Labour, and other HR modules depend. An enterprise that licenses Oracle Payroll without explicitly licensing Oracle Global HR may find that Oracle's GLAS team identifies Global HR as an unlicensed dependency. Oracle Global HR NUP licences are priced per user of the HR module family — for a 5,000-employee enterprise, this creates significant exposure. Review the HR module stack specifically, as this is the most frequently cited EBS compliance gap in Redress Compliance engagements.
When did you last independently validate your Oracle EBS licence position?
Redress Compliance conducts EBS module and user metric assessments — before Oracle's GLAS team does.05Has the NUP count been calculated as all users with active application user accounts — not concurrent sessions, not active users — for every licensed EBS module?High Risk
Expert NoteOracle's Named User Plus metric for EBS counts every individual with an authorised application user account, whether or not they have logged in recently. The correct NUP count for an EBS module is the number of active user accounts in FND_USER where the USER_END_DATE is null or in the future, filtered to users with access responsibility for that module. Counting based on login frequency or concurrent session peaks consistently undercounts — Oracle's GLAS team queries FND_USER directly. Run: SELECT COUNT(DISTINCT USER_NAME) FROM FND_USER WHERE NVL(END_DATE, SYSDATE+1) > SYSDATE. This is your NUP minimum for any module accessible to those users.
06Are the contracted NUP quantities for each EBS module equal to or greater than the current active FND_USER count with access responsibilities for that module?High Risk
Expert NoteNUP shortfall is the most common quantifiable EBS compliance gap. An enterprise that contracted 500 NUPs for Oracle Financials in 2015 and has grown through acquisition and organic growth to 850 active financial users is carrying a 350-NUP shortfall — at Oracle's list price of approximately £900 per NUP for Oracle Applications, this represents a £315,000 licence exposure plus ongoing support obligation. Map every EBS module against its contracted NUP quantity and current FND_USER count quarterly. NUP shortfalls that persist through an Oracle audit are resolved at Oracle's commercial terms, not at a negotiated enterprise rate.
07For EBS modules used through a single sign-on interface or portal, have all users of the portal been counted as NUPs for the underlying EBS modules they can access — even if they never directly access the EBS interface?Medium Risk
Expert NoteEBS portal and SSO deployments create NUP counting complexity: when users access EBS functionality through a portal, intranet, or middleware layer without directly logging into the EBS application, Oracle's position is that all users authorised to access EBS functionality through that interface must still be counted as NUPs. This particularly affects self-service HR portals (Oracle iRecruitment, Oracle Employee Self-Service) where hundreds or thousands of employees access limited EBS HR functionality through a portal but are not registered EBS application users. Oracle's GLAS team will identify these indirect access scenarios through integration architecture review during an audit.
08Has the Application Specific Full Use (ASFU) licensing model been assessed for EBS modules where only a limited number of users access the application through a custom interface — and has Oracle's approval of the ASFU use case been documented?Medium Risk
Expert NoteOracle Application Specific Full Use (ASFU) is a restricted licence that permits use of Oracle EBS technology (including Oracle Database) only to support specific Oracle Applications — it cannot be used for general Oracle Database use. ASFU licences are less expensive than Full Use licences but create deployment restrictions that must be enforced at the infrastructure level. Enterprises with ASFU licences who run non-EBS Oracle Database workloads on the same ASFU-licensed infrastructure are violating the ASFU restriction — a condition Oracle identifies through infrastructure topology review. Confirm that all ASFU-licensed servers run only Oracle Applications workloads, with no general Oracle Database use.
09Has the underlying Oracle Database licence for the EBS platform been validated — confirming that the EBS database licence type (Full Use or ASFU) and metric align with the actual database deployment configuration?High Risk
Expert NoteEBS runs on Oracle Database, and the Oracle Database licence supporting EBS is often ASFU-licensed at a lower price point. The ASFU restriction means the database can only support Oracle EBS workloads — it cannot be used for custom application databases, reporting databases, or any non-EBS Oracle schema. In practice, organisations routinely create additional schemas in the EBS database for custom applications, ETL processes, or reporting tools, violating the ASFU restriction and creating an unplanned Full Use licence requirement for the entire database. Audit all schemas in the EBS database against the ASFU use case definition.
10For EBS R12.2 deployments, has the Online Patching (adop) infrastructure been assessed — confirming that the two-edition database required for online patching is covered by the existing EBS licence?Medium Risk
Expert NoteOracle EBS R12.2's Online Patching feature uses Oracle Database Edition-Based Redefinition (EBR) to enable patching without application downtime. This creates two database editions (RUN and PATCH) of the EBS schema, which Oracle includes within the standard EBS R12.2 licence. However, organisations that have customised the patching infrastructure or extended EBR beyond its standard EBS use case may have licensing exposure. Additionally, the EBR feature requires Oracle Database 11.2.0.4 or later — confirming that the Oracle Database version is both supported by Oracle and covered by the EBS ASFU licence is a necessary compliance check for R12.2 deployments.
11Has a gap analysis been performed between the most recent Oracle EBS contract (including all amendments and order forms) and the current deployment — including any EBS modules acquired through acquisition of companies with existing Oracle contracts?High Risk
Expert NoteEBS contracts accumulate through multiple order forms, amendments, and renewal documents over years of deployment. A definitive gap analysis requires consolidating all order documents into a single licence register and cross-referencing it against the current FND_PRODUCT_INSTALLATIONS deployment. Acquired company EBS deployments add complexity: the acquired entity's Oracle contract is separate from the parent's contract, and Oracle may require the acquired modules to be licensed under the parent entity's contract separately. The gap analysis must treat each legal entity's Oracle contract as distinct unless Oracle has explicitly agreed to a contract consolidation.
12Have Oracle WebLogic Server licences been validated for the EBS application server tier — confirming that WebLogic is covered by the EBS licence or separately licensed, depending on the EBS version and contract?Medium Risk
Expert NoteOracle EBS R12.2 runs on Oracle WebLogic Server, which Oracle includes within the EBS Application licence for the specific EBS application tiers. However, enterprises that deploy additional WebLogic managed servers beyond the standard EBS topology — for custom applications, ESB, or SOA integrations — create a WebLogic licence requirement beyond the included EBS allocation. Oracle's GLAS team assesses WebLogic topology separately from EBS module compliance. Confirm that every WebLogic managed server in the EBS infrastructure is within the scope of the EBS-included WebLogic entitlement, and separately licence any WebLogic use beyond that scope.
13Has the Oracle EBS support status been confirmed — specifically whether the deployment is on Premier Support, Extended Support, or Sustaining Support — and has the financial impact of each option been modelled?Medium Risk
Expert NoteOracle EBS R12.1 moved to Sustaining Support in December 2021; EBS R12.2 remains on Premier Support through at least December 2031. The support tier determines the level of support Oracle is contractually required to provide: Premier Support includes new fixes, security patches, and certification for new platforms; Sustaining Support provides access to existing fixes only, with no new patches, no certification for new operating systems, and no security patches. Enterprises on EBS R12.1 under Sustaining Support face increasing security risk and should evaluate R12.2 upgrade or Cloud ERP migration as part of their support strategy review.
14Has third-party support for Oracle EBS been formally evaluated — including Rimini Street and Spinnaker Support — and has a risk assessment of moving off Oracle Premier Support been completed?Medium Risk
Expert NoteThird-party Oracle EBS support (Rimini Street, Spinnaker Support) is a well-established alternative to Oracle Premier Support that typically reduces annual support cost by 50% while maintaining system functionality. The key risks of third-party support are: no access to new Oracle patches or security updates (reliance on third-party's security process), potential Oracle audit activity following support termination, and a more complex return path to Oracle support if required. The financial case is frequently compelling — a £500,000 annual Oracle EBS support contract can be replaced by £250,000 third-party support, saving £250,000 annually — but the decision requires a structured risk assessment, not just cost comparison.
15Has the EBS R12.2 upgrade path been assessed for EBS R12.1 deployments — including the compliance clean-up required before Oracle will certify R12.2 upgrade eligibility?Low Risk
Expert NoteOrganisations upgrading from EBS R12.1 to R12.2 must resolve any known compliance gaps before Oracle's support team will certify the upgrade path. Oracle's pre-upgrade assessment (conducted as part of Oracle's upgrade support) includes a review of module licensing and user counts. An R12.2 upgrade project that surfaces compliance gaps mid-project creates both project risk (delayed go-live) and commercial risk (Oracle using the upgrade as leverage to resolve compliance findings at premium commercial terms). Commission an independent EBS licensing assessment before initiating an R12.2 upgrade project — remediation before Oracle engagement is always less expensive than remediation during Oracle engagement.
16For EBS deployments considering migration to Oracle Fusion Cloud ERP (Oracle Cloud Applications), has the transition credit and licence migration programme been evaluated — and have the commercial terms been independently reviewed?Medium Risk
Expert NoteOracle aggressively promotes migration from EBS to Oracle Fusion Cloud ERP (Oracle Fusion Applications), offering "transition credits" that apply existing Oracle EBS licence value toward Fusion Cloud ERP SaaS subscriptions. These transition programmes are commercially complex: the credits are typically calculated on Oracle's internal values, not market values, and the Fusion Cloud subscription replaces perpetual EBS licences and Oracle Database licences with ongoing subscription cost that grows with user count. Before committing to a Fusion migration, model the 5-year and 10-year total cost of the Fusion subscription against continued EBS operation (including support optimisation) to confirm the financial case is genuine rather than Oracle-constructed.
17Has an EBS licence register been maintained that documents contracted modules, NUP quantities, support contract references, and all amendments — updated within the last 12 months?Medium Risk
Expert NoteThe EBS licence register is the governance document that enables an organisation to respond to Oracle audit notification quickly and from a position of confidence. Without it, the immediate response to an Oracle GLAS notification is a scramble to locate contract documents, reconstruct the licence history, and establish the current deployment position — typically under time pressure that disadvantages the organisation. The register should document: all order forms and amendments with effective dates, licensed module list by order form, NUP quantities by module, CSI numbers, support contract identifiers, and the most recent independent compliance assessment date. Review and update this register at every Oracle support renewal.
18Has the organisation established a process for reviewing EBS user account lifecycle — including deactivating FND_USER accounts for leavers, temporary workers, and system accounts no longer in use?Medium Risk
Expert NoteEBS user account hygiene directly affects NUP licence compliance. Organisations that do not maintain an active FND_USER account lifecycle process accumulate inactive accounts that still count toward NUP requirements under Oracle's metric. A leaver whose EBS account is not end-dated continues to consume an NUP licence. A temporary worker's account that remains active post-contract adds to NUP count. Implement an automated process that end-dates FND_USER accounts within 24 hours of HR system departure records, and conduct a quarterly FND_USER audit against HR system active employee records. This process reduces NUP count, reduces licence cost, and eliminates orphaned accounts as a security risk.
19Has an EBS-specific data collection script library been established — independent of Oracle's LMS scripts — that can produce deployment and user count evidence on short notice if Oracle initiates a licence review?Medium Risk
Expert NoteWhen Oracle's GLAS team initiates an EBS audit, they request permission to run their own data collection scripts. Running Oracle's LMS scripts grants Oracle access to the database outputs under Oracle's terms, which typically grant Oracle the right to use the data in commercial discussions. Independent EBS assessment scripts — maintained by the customer or its advisers — allow the organisation to collect the same data independently, verify it against the contract, and present a pre-audited compliance position rather than reacting to Oracle's findings. Key queries include FND_PRODUCT_INSTALLATIONS (module status), FND_USER (user count), and FND_RESP_FUNCTIONS (user-to-module access mapping).
20Has an independent EBS licensing assessment — conducted by advisers with no commercial interest in Oracle's renewal outcome — been completed within the past 18 months?Low Risk
Expert NoteAn independent EBS licensing assessment is the single most effective measure for managing Oracle audit risk. It identifies and quantifies compliance gaps before Oracle does, produces a documented compliance programme that shifts the commercial dynamic when Oracle engages, and provides the factual foundation for renewal negotiation. The assessment should cover module compliance (FND_PRODUCT_INSTALLATIONS vs. contract), user metric compliance (FND_USER count vs. NUP quantities), ASFU restriction compliance, WebLogic entitlement, and Oracle Database licence status. Organisations with an independent assessment on record consistently achieve materially better renewal outcomes than those responding reactively to Oracle GLAS findings.
From Assessment to Action
The 20 checks above define a complete EBS compliance assessment framework. An organisation that works through each check — and resolves any High Risk findings before Oracle's next engagement — is in a materially stronger commercial and legal position than the majority of Oracle EBS customers. The investment in proactive compliance management is almost always recovered in the first renewal negotiation where Oracle's leverage is reduced by a documented, independently validated compliance position.
Download the Oracle EBS Assessment Guide →