Oracle E-Business Suite includes restricted-use database and middleware licences at no extra cost. But certain customisations, even seemingly small ones, can void that benefit and trigger full-use licensing requirements worth hundreds of thousands of dollars. This guide shows ITAM professionals how to identify, assess, and mitigate these risks.
This guide is part of the Oracle EBS Licensing Guide series. Related EBS guides include EBS Licensing Basics, Licensing Oracle EBS Modules & Suites, and EBS Licence Compliance Checklist.
Customising an Oracle E-Business Suite (EBS) environment can deliver significant business value, but it can also generate hidden licensing costs that dwarf the original development effort. Oracle includes database and middleware licences with EBS, but only for restricted use. Cross that line, and you may be required to purchase full-use licences for Oracle Database Enterprise Edition and Oracle WebLogic Server at list prices that can reach hundreds of thousands of dollars.
This article explains how customised database technology in Oracle EBS can inadvertently violate licence rules, what to look out for, and how ITAM professionals can identify and mitigate these risks in global enterprises.
Oracle EBS is bundled with essential technology components, the Oracle Database and Oracle WebLogic Server (middleware), under a restricted-use licence. When you purchase Oracle EBS application licences, you do not separately pay for a full Oracle Database or WebLogic licence to run them. Oracle provides these as part of the deal, but with strict conditions attached.
The included database and middleware licences can only be used to support the EBS applications you licensed. In practice, this is a significant cost benefit: you get the database engine and application server needed to run EBS without purchasing full-use licences upfront. However, the restriction is clear: using the database or middleware for anything beyond standard EBS is not permitted under the restricted-use grant.
Think of the included Oracle Database and middleware as EBS-only infrastructure. They are powerful tools given to you, but only to run standard EBS functionality. Any use beyond that scope, no matter how minor ("We already have an Oracle DB here, let us add another schema for a small app..."), can void the restricted-use benefit and trigger full-use licensing costs.
| Component | Included With EBS? | Restriction | Full-Use List Price |
|---|---|---|---|
| Oracle Database EE | Yes (restricted use) | EBS data only. No custom schemas or non-EBS applications. | ~$47,500/processor |
| Oracle WebLogic Server | Yes (restricted use) | EBS application tier only. No custom apps or third-party deployments. | ~$25,000-$50,000/processor |
| Oracle BI Publisher | Yes (limited) | Standard EBS reports against EBS data only. | Varies (per user or per processor) |
| Oracle Forms / Reports | Yes (restricted use) | EBS-delivered forms and reports only. | Included in WebLogic full-use licence |
Oracle's EBS licensing policy defines three levels of customisation, each with increasing licence requirements. Understanding which category your organisation's changes fall into is critical for compliance.
| Customisation Level | Examples | Licensing Impact |
|---|---|---|
| Level 1: No Modifications (out-of-the-box) | Deploy EBS as delivered with no custom code or schema changes. Use standard Oracle-provided configuration options. | No additional licences needed. Restricted-use DB and middleware cover all EBS usage. |
| Level 2: UI/Logic Extensions (reports, forms, Java code within EBS) | Creating custom reports, altering forms, adding minor Java business logic using Oracle's extension tools (OAF, Forms Personalisation). | Full middleware licence required. You must licence Oracle WebLogic for all users or processors. Database remains restricted use. |
| Level 3: Database Customisations (schema changes) | Adding new tables, custom triggers, stored procedures, or an extra schema inside the EBS database for additional functionality. | Full Oracle Database EE licence AND full middleware licence required. The "free" benefit is entirely voided. |
Even moderate customisations escalate licence needs. Simply developing a custom workflow or report can force you to purchase an Oracle middleware licence (which was otherwise free under EBS). And if you go deeper and modify the database schema itself, the cost jumps dramatically. You effectively convert your "free" EBS database into a fully licensable Oracle Database instance. Oracle treats customised database technology in EBS as if you installed a separate Oracle product, and prices it accordingly.
Level 3 cost example. An 8-core server (4 processors after Core Factor 0.5): ~$190K DB + ~$100K-$200K WebLogic + 22%/year support on both. This was $0 under restricted use.
Many enterprises enhance Oracle EBS by adding fields, tables, or triggers to tailor the system to business needs. While this can deliver functional benefits, it crosses a licensing red line when done in the EBS database itself.
Oracle's policy is explicit: if you add or modify any objects in the Oracle EBS database schema, a table, column, stored procedure, or trigger, you are no longer just using EBS. You are altering Oracle's database structure. This triggers the requirement for a full-use Oracle Database Enterprise Edition licence, along with the associated middleware licence for the application tier.
Real-world scenario: custom project management module triggers six-figure audit finding. A global enterprise developed a custom project management module, creating new tables and triggers in the EBS database to integrate with EBS Financials. The team assumed this was an efficient use of the existing system. During a routine Oracle audit, the custom tables were flagged. Oracle determined the company was using the database for custom applications beyond EBS. Audit finding: $380,000+ in unbudgeted licence costs, for a module that cost $50K to develop.
Oracle Database Enterprise Edition licences run ~$47,500 per processor at list price, and enterprises typically run EBS on multi-processor servers. An 8-core server (using Oracle's standard Core Factor of 0.5 for Intel/AMD) requires 4 processor licences: 4 x $47,500 = $190,000 just for the database. Add WebLogic full-use licensing and 22% annual support on both, and the total easily exceeds $380,000, costs that had been entirely avoided under the restricted-use grant.
| Scenario | DB Licence Cost | WebLogic Cost | Annual Support |
|---|---|---|---|
| Restricted use (no customisation) | $0 | $0 | $0 |
| After Level 3 customisation (16-core Intel server, CF 0.5 = 8 processors) | $380,000 | $200,000 | $127,600/year |
Oracle EBS relies on Oracle's middleware (Oracle WebLogic Server) to run forms, reports, and application logic. Oracle includes a limited-use licence of this middleware for EBS's own needs. But using the EBS application server for anything other than its intended purpose is another licensing landmine.
| Scenario | Risk Level | Why It Triggers Full-Use |
|---|---|---|
| Custom Java app on EBS WebLogic | High | Deploying a custom .war/.ear application on the EBS WebLogic domain means the middleware is hosting non-EBS software. |
| Third-party integration on EBS app server | High | Adding third-party applications (ETL tools, portals, connectors) to the EBS WebLogic for integration convenience. |
| BI Publisher accessing non-EBS data | Medium-High | Using EBS-included BI Publisher to pull data from non-EBS sources or heavily customised schemas beyond standard EBS data. |
| Custom web services on EBS middleware | Medium | Exposing custom REST/SOAP services from the EBS WebLogic that serve non-EBS consumers. |
| Custom reports using new DB objects | Medium | Reports built on custom tables (not standard EBS objects) may trigger both middleware and database full-use requirements. |
Real-world scenario: retailer's "stack share" strategy backfires in audit. A large retailer using Oracle EBS decided to host a custom employee portal application on the same Oracle WebLogic Server that runs EBS, reasoning it would save infrastructure costs. Oracle's auditors discovered the shared deployment. The finding: the embedded WebLogic licence is only for EBS modules, not an employee portal. The retailer had to obtain a full WebLogic Suite licence for the environment and pay licence fees retroactively. Result: $200K+ in WebLogic licensing costs. The supposed savings of consolidating apps evaporated instantly.
BI Publisher: a commonly overlooked trigger. Oracle BI Publisher is included with EBS in a limited capacity, to run standard EBS reports or slightly modified reports against the EBS schema. If you use BI Publisher on the EBS server to access any non-EBS data source or a heavily customised schema, Oracle requires a full-use BI Publisher licence. These smaller "middleware triggers" are easy to overlook but are equally subject to audit findings.
How can ITAM professionals proactively identify where customised database technology in Oracle EBS might be breaking the rules? Early identification is critical. Here is a step-by-step approach to find and address risky customisations in an enterprise EBS environment.
Inventory the EBS database schemas. Work with your DBAs to list all schemas and custom objects in the EBS Oracle Database. Compare them against a vanilla EBS installation or Oracle's documentation. Red flag: any schema or table that did not come with EBS (especially ones prefixed differently than standard EBS modules) indicates a custom extension that may trigger full-use licensing.
Scan for custom triggers and procedures. Check for custom triggers on EBS tables or stored procedures/packages that integrate with external systems. A trigger that writes to an external table or calls an external application indicates the EBS database is being used for non-EBS operations, a Level 3 customisation.
Review WebLogic deployments. Have your middleware administrator list all applications and services deployed on the Oracle WebLogic/Application Server that hosts EBS. Ensure every deployment is an Oracle-provided EBS component or officially supported add-on. Red flag: custom .ear or .war applications in the EBS domain.
Check for unlicensed modules or BI tools. Run Oracle's LMS scripts or EBS usage reports to verify whether any modules are active without licences, or if BI Publisher is accessing non-EBS data. Sometimes enabling an unlicensed EBS module or using an included tool beyond its limits also violates terms.
Interview developers and architects. Talk to the teams that built extensions or reports. It is common to find well-meaning developers who added a few tables or deployed a small integration in EBS without realising the licensing implications. Human intelligence complements your technical scans.
What Oracle's auditors check. During an audit, Oracle may request a dump of all database users/schemas on the EBS instance or inspect the WebLogic console for additional deployments. If ITAM has this information ready and has addressed any issues (either by licensing or removing the customisation), the organisation is in a far stronger position. It is always better to find and fix a potential compliance gap before Oracle does.
| # | Recommendation | Why It Matters |
|---|---|---|
| 1 | Document your EBS environment | Keep an up-to-date record of all customisations, integrations, and extensions. Enables quick compliance assessment and is invaluable during audits. |
| 2 | Educate your team | Train developers and system architects on Oracle's EBS licensing rules. Even seemingly harmless changes (adding a trigger, deploying a small app on WebLogic) can have significant consequences. |
| 3 | Segregate custom applications | Deploy any non-EBS application or database schema on separate, fully licensed Oracle platforms. Avoids commingling that voids the restricted-use benefit. |
| 4 | Leverage Oracle-provided tools | Use Oracle's LMS audit scripts regularly to check usage. Shows extra schemas or unauthorised usage, giving you time to correct course before Oracle audits. |
| 5 | Review contracts and policies | Regularly revisit your Oracle EBS licensing agreement and Oracle's official policy documents. Understanding the fine print helps enforce internal compliance. |
| 6 | Plan before you customise | Involve ITAM before green-lighting significant EBS customisations. A cost-benefit analysis that includes full-use licensing costs may change the decision entirely. |
| 7 | Consider Oracle's approval | If a customisation is critical, negotiate with Oracle for a special licence or amendment. Getting terms in writing avoids ambiguity during future audits. |
| 8 | Archive audit trails | Maintain logs and evidence of how EBS is being used. If you remove a customisation, record that action. Demonstrates historical diligence in audit. |
| 9 | Use reporting instances carefully | If you create a read-only reporting database by copying EBS data, it likely needs its own licence. Data warehouses or clones decoupled from EBS are not covered by restricted use. |
| 10 | Engage independent experts | Oracle licensing is complex. An objective review before an audit or major project can save huge fees. A small advisory cost can prevent six- or seven-figure compliance penalties. |
If those tables reside in the Oracle EBS database schema (or any schema on the EBS database instance), yes. Oracle considers this a database modification, a Level 3 customisation. According to Oracle's policy, schema changes require a full-use database licence (and potentially a full middleware licence as well). It is safer to move those tables to a separate database instance with its own licence, or verify with Oracle if an exception exists in your specific contract (which is rare). The cost difference between a separate small database and voiding the restricted-use benefit on your entire EBS environment is enormous.
Not under the EBS included licence. The EBS database that comes with your application is strictly tied to EBS usage. Even if your company owns other Oracle DB licences, those do not automatically cover using the EBS instance for other apps. You would need to explicitly licence the EBS database server for full use if you run any additional applications on it. Treat the EBS-provided database as off-limits for other purposes unless you convert it to a fully licensed environment, which means purchasing DB EE licences for all processors on that server.
Basic custom reports that use only EBS data are generally fine. Oracle provides tools like BI Publisher with EBS for that purpose. However, if you create complex reports or new BI Publisher reports that pull in external data or utilise new database objects you added, that crosses into full-use territory for BI Publisher or the database. Always ensure your reports only access allowed data sources. Even for custom reports, Oracle requires that you licence Oracle WebLogic if you have built custom Java programs or complex forms. Stick to Oracle's extension frameworks and standard EBS data to stay safe.
Oracle's Licence Management Services will issue a formal report of non-compliance. You would then be expected to purchase the necessary licences (Database EE, WebLogic Server) for the environments in question, potentially at list price, plus back-support fees for the entire period of unlicensed use. In some cases Oracle may require an immediate true-up. It can be an expensive lesson, often costing hundreds of thousands or millions of dollars in large environments. Having documentation that shows you identified and remediated issues before the audit strengthens your negotiating position significantly.
It is worth trying. If you know in advance that a project will require extending EBS significantly, you can negotiate an arrangement with Oracle. This could involve adding the necessary technical licences to your agreement at a discount, or obtaining an amendment that grants specific rights for a defined scope of customisation. Oracle is generally strict on policy, but they may work with you commercially if it means selling additional licences. Always get any such agreement in writing. An independent advisor like Redress Compliance can help benchmark pricing and negotiate favourable terms.
Oracle's processor-based licensing uses the Core Factor Table to convert physical CPU cores into licensable "processors." Intel and AMD chips typically have a core factor of 0.5, meaning two physical cores equal one processor licence. For example, a server with 16 Intel cores requires 8 processor licences (16 x 0.5). At $47,500 per processor for DB EE, that is $380,000 in database licences alone. When evaluating the cost impact of voiding your restricted-use licence, always apply the correct core factor for your hardware.
The restricted-use rules apply regardless of where EBS runs: on-premises, in OCI, or on AWS/Azure. If you run EBS on AWS EC2, the included restricted-use DB and WebLogic licences still apply, and the same customisation restrictions remain in force. Cloud migration does not reset or relax these licensing terms. Cloud deployments can make compliance more complex because Oracle's licensing in virtualised and cloud environments has additional rules around vCPU counting.