1. What Is Oracle E-Business Suite?
Oracle E-Business Suite (EBS) is a comprehensive on-premises enterprise resource planning (ERP) platform covering finance, supply chain, HR, procurement, manufacturing, and more. It remains a legacy Oracle product that many global enterprises still rely on for mission-critical business processes, even as Oracle pushes customers toward its Fusion Cloud applications.
Licensing for Oracle EBS is notoriously complex and costly, utilising a named-user model known as the Application User licence. Every individual who is authorised to access an EBS module needs a licence for that module — even if they only view data occasionally. Oracle's standard policy doesn't differentiate between heavy transactional users and light report-only users when counting licences, which means companies often face over-licensing when they give full licences to users who only run reports.
To address this, Oracle offers a specialised EBS Read-Only User Licence for certain applications — a cost-effective alternative that ITAM professionals can leverage to optimise licensing spend.
For the complete EBS licensing overview, see Oracle E-Business Suite Licensing Guide — 2026 Edition.
2. What Is an EBS Read-Only User Licence?
An Oracle EBS Read-Only User Licence is a licensing option that grants a named user view-only access to specific Oracle E-Business Suite modules. In practical terms, a user with a read-only licence can log in to the EBS application, view data, run inquiries, and generate reports, but cannot create or modify transactions.
This is ideal for roles such as executives reviewing dashboards, auditors checking configurations, finance controllers analysing reports, or analysts who require information from the system but are not responsible for day-to-day data entry.
| Characteristic | Detail |
|---|---|
| Access scope | Queries, reports, inquiries, and lookups only. No inserts, updates, or deletes. |
| Enforcement | Contractually defined. System administrators enforce via "inquiry" or reporting responsibilities in EBS. |
| Pricing | Significantly lower than a full-use Application User licence for the same module (typically 40–60% less). |
| Formal licence | Still a named-user licence. Every read-only user must be licensed — there is no free usage. |
| Availability | On-premises EBS only. Oracle's SaaS cloud ERP uses a different subscription model. |
| Minimum users | At least one full-use Application User licence is required per module before read-only users can be added. |
3. Full-Use vs Read-Only Application User
Understanding the distinction between these two licence types is fundamental to EBS cost optimisation. At least one user must have full rights (and a full licence) for each module in use, while additional users can be assigned read-only licences if their roles permit.
| Dimension | Full-Use Application User | Read-Only Application User |
|---|---|---|
| Functionality | Complete: create, edit, delete transactions and data within the EBS module | View only: navigate screens, look up records, run standard/ad hoc reports. No transactions or changes. |
| Intended roles | Operational staff: AP clerks entering invoices, buyers creating POs, HR managers processing payroll | Insight roles: executives, auditors, analysts, finance controllers, compliance officers |
| Cost | Full list price per module (most expensive tier) | Significantly discounted — typically 40–60% less than full-use |
| Licence requirement | Named user: one licence per individual per module | Named user: one licence per individual per module (same model, lower price) |
| Minimum requirement | At least one full-use licence required per module | Can only be added after at least one full-use licence exists for the module |
| Audit risk | Low (if user counts are accurate) | Medium-high: Oracle will check that read-only users genuinely perform no transactions |
For a detailed comparison of EBS user types, see Application User Licensing for Oracle EBS.
4. Who Qualifies for a Read-Only Licence?
Not every EBS user can be placed on a read-only licence. The key criterion is that the individual must genuinely only view data — they cannot perform any create, update, or delete operations in the module.
| Role Example | Typical EBS Activity | Licence Type Needed |
|---|---|---|
| AP Clerk | Creates and processes invoices daily | Full-Use |
| Procurement Buyer | Creates purchase orders, manages suppliers | Full-Use |
| HR Administrator | Maintains employee records, processes payroll | Full-Use |
| Finance Controller | Reviews reports, analyses GL balances (no journal entries) | Read-Only ✅ |
| Executive / VP | Views dashboards, runs executive summaries | Read-Only ✅ |
| Internal Auditor | Checks configurations, reviews transaction logs | Read-Only ✅ |
| Business Analyst | Runs ad hoc queries, generates reports for analysis | Read-Only ✅ |
| Manager (approver) | Approves invoices or POs within EBS | Full-Use (approval = transaction) |
For the full module-by-module breakdown, see Licensing Oracle EBS Modules & Suites.
Are You Over-Licensing Your EBS Users?
Many enterprises pay full-use licence prices for hundreds of users who only view data. Our independent Oracle advisers can conduct a read-only user assessment, identify optimisation opportunities, and help you reduce EBS licensing costs by 30–50%. Fixed-fee engagements. No ties to Oracle.
5. Cost Savings and Pricing
The read-only user licence is priced significantly lower than a full-use Application User licence for the same module. While exact pricing varies by module, contract terms, and negotiated discounts, the savings are substantial — especially in large environments with many reporting-only users.
| Scenario | Full-Use Licence Cost | Read-Only Licence Cost | Savings per User | Users Eligible | Annual Savings |
|---|---|---|---|---|---|
| Financials module (GL, AP, AR) | $4,350/user | $1,740/user | $2,610 | 80 | $208,800 |
| Procurement module | $3,000/user | $1,200/user | $1,800 | 30 | $54,000 |
| Supply Chain module | $4,000/user | $1,600/user | $2,400 | 25 | $60,000 |
| Total illustrative savings | 135 | $322,800/year | |||
Illustrative figures based on typical Oracle list pricing. Actual costs depend on contract terms, volume discounts, and negotiated rates.
A mid-sized financial services company had 500 Oracle EBS Financials users, all on full-use Application User licences. An internal review revealed that 180 of those users were finance controllers, regional managers, and analysts who only ran reports and viewed balances — they never created journal entries, invoices, or payments. By reclassifying those 180 users to read-only licences, the company reduced its annual EBS licensing cost by approximately $470,000 while remaining fully compliant. The reclassification was documented and validated before the next Oracle audit cycle.
Additional Pricing Considerations
Minimum quantities: Read-only licences often have low minimums (even 1), so you can purchase exactly what you need. However, the module itself may require a minimum number of total users — any combination of full and read-only can satisfy that threshold.
Support fees: Annual support (typically ~22% of licence cost) applies to read-only licences just as it does to full-use licences. The savings compound because support is calculated on the lower licence price.
Negotiation leverage: List prices are typically negotiable in enterprise agreements. However, Oracle may be less inclined to heavily discount legacy on-premises products while pushing cloud subscriptions. For negotiation strategies, see Oracle Contract Negotiation Service.
6. Compliance Requirements and Audit Risks
Read-only licences introduce specific compliance risks that ITAM professionals must manage carefully. Oracle's audit teams (License Management Services / GLAS) know exactly how to identify read-only licence misuse.
| Audit Risk | What Oracle Checks | Consequence |
|---|---|---|
| Transaction activity by read-only users | Oracle's LMS scripts can trace which users performed create/update/delete actions in each module | Reclassification to full-use licence + price difference + retroactive support fees |
| Responsibility misassignment | Users with read-only licences assigned responsibilities that include transactional forms | Even if the user never used the transactional forms, Oracle may argue the access itself requires a full licence |
| Unlicensed read-only users | Users with EBS accounts who have no licence at all (neither full nor read-only) | Oracle defaults to full-use Professional User pricing for any unlicensed account |
| Approver misclassification | Users on read-only licences who approve workflows (invoices, POs, expense reports) | Approval = transaction. Full-use licence required. |
| Custom forms accessing transactional data | Custom screens or reports that inadvertently allow data modification | Users accessing those custom forms may need full-use licences |
For a comprehensive compliance checklist, see Oracle Licensing Guide for CIOs and Procurement Teams.
7. Enforcing Read-Only Access in EBS
The key to successful read-only licensing is technical enforcement — you must configure EBS so that read-only users genuinely cannot perform transactions, regardless of intent.
Assign Inquiry-Only Responsibilities
In Oracle EBS, access is controlled through responsibilities. Assign read-only users only "inquiry" or "reporting" responsibilities that restrict them to view-only forms. Never assign a responsibility that includes transactional forms.
Audit Responsibility Menus
Review the menu trees attached to each responsibility. Ensure no transactional forms (create, update, approve) are included. Custom responsibilities are especially risky — verify them manually.
Lock Down Form Functions
Use Oracle's function security to exclude specific form functions. Even if a menu path exists, function-level exclusions can prevent the user from opening transactional screens.
Validate and Document
Run periodic validation queries: check that read-only users have zero insert/update/delete activity in audit tables. Document everything — this is your proof if Oracle audits you.
Need help configuring read-only access for compliance? We can help.
Oracle Licence Management →8. Cloud Transition Considerations
If your organisation is planning to migrate from Oracle EBS to Oracle Fusion Cloud ERP, the read-only licence model has important implications.
| Consideration | Impact |
|---|---|
| No licence portability | EBS read-only licences (and full-use licences) do not transfer to Oracle Fusion Cloud. Cloud uses a separate subscription model. You will need new cloud subscriptions. |
| Don't over-buy on-prem | If a cloud transition is on the horizon, avoid purchasing additional EBS read-only licences that will become obsolete. Consider short-term optimisation instead. |
| Dual-run licensing | During migration, you may run both EBS and Cloud simultaneously. Both environments require licensing — read-only users on EBS still need their licences during the overlap period. |
| Support credit programs | Oracle's Customer 2 Cloud and similar programs may offer support fee credits when transitioning to cloud. Factor in your read-only licence support fees when calculating potential credits. |
| EBS 12.2 support through 2030s | Oracle continues to sell and support EBS licences (including read-only) for on-premises customers. Premier support for EBS 12.2 is committed through at least 2032. |
For cloud transition planning, see Oracle EBS to Cloud Transition: Licensing Impact and CIO Playbook: Transition from Oracle On-Premise to Fusion Cloud.
Navigating an Oracle EBS Audit?
If Oracle has initiated an audit — or you suspect one is coming — our independent advisers can validate your read-only licence classifications, challenge incorrect audit findings, and negotiate on your behalf. We work exclusively for customers, never for Oracle.
9. Best Practices and Optimisation Strategies
- Conduct a user access review. Pull a complete list of all active EBS users and their assigned responsibilities. Identify every user who only has inquiry/reporting responsibilities — these are your read-only licence candidates. Cross-reference with actual transaction logs to confirm they've performed no transactional activity.
- Enforce read-only access technically, not just contractually. Don't rely on users "promising" not to create transactions. Configure EBS responsibilities so read-only users technically cannot access transactional forms. Use function security exclusions as an additional safeguard.
- Audit responsibility assignments quarterly. Role changes, new projects, and temporary assignments can cause responsibility creep. A user who was read-only last quarter may have been given a transactional responsibility by a well-meaning admin. Catch it early. See Oracle EBS Licensing Basics.
- Document everything. Maintain a register of all read-only users: their names, modules, assigned responsibilities, and the date of last validation. In an Oracle audit, your documentation is your defence. If you can show Oracle a clean, well-maintained register with supporting evidence, you significantly strengthen your position.
- Reclassify in both directions. If a read-only user's role changes to include transactions, upgrade their licence to full-use immediately. Conversely, if a full-use user transitions to a reporting-only role, downgrade them to read-only. Both directions save money or prevent compliance exposure.
- Factor in module-level licensing. Remember that EBS licensing is per module per user. A single person using three modules in read-only mode needs three read-only licences. Ensure your optimisation covers all modules, not just the most expensive one. See Complete Oracle EBS Application Module List.
- Don't forget support cost savings. Annual support (~22% of licence cost) applies to read-only licences at the lower price. When modelling savings, include the compounding support fee reduction — over 3–5 years, this can be as significant as the initial licence savings.
- Engage independent expertise for large-scale reclassification. If you have 500+ EBS users to review, an independent Oracle licensing adviser can accelerate the process, validate your classifications, and prepare audit-ready documentation. The advisory fee is typically a fraction of the licence savings achieved.
💡 The Two-Tier Model: Full-Use + Read-Only
The most cost-effective EBS licensing strategy uses a two-tier approach: full-use Application User licences for operational staff who perform transactions, and read-only licences for everyone else who only needs visibility. This granular matching of licence spend to user needs can generate hundreds of thousands of dollars in annual savings in large environments — without any reduction in functionality or data access for the users who need it.