Ricoh Europe Oracle Licensing Advisory

Oracle at Enterprise Scale: The Ricoh Europe Profile

Ricoh Europe is one of the continent's most significant enterprise technology businesses — a subsidiary of Ricoh Company Ltd, the Japanese multinational with revenues exceeding $13 billion — operating across document management, workplace services, digital transformation, and managed IT solutions. Like many large European manufacturers and technology services companies of its generation, Ricoh built a significant portion of its enterprise IT backbone on Oracle: multiple instances of Oracle E-Business Suite (EBS) for financials, supply chain, and operations, alongside Oracle Database underpinning core transactional systems.

That footprint is representative of a pattern we see consistently across European enterprise clients. Oracle EBS deployments that began in the 2000s have become deeply embedded. The applications work well enough. The data structures are complex. The migration cost and disruption risk are real. And in the meantime, Oracle support fees compound at 8% per year — quietly and reliably expanding the annual bill regardless of whether the organisation is adding features, users, or value.

The question facing CIOs and CFOs at organisations like Ricoh Europe is not simply "should we stay with Oracle?" It is: "Do we actually understand what we are paying for, what we are entitled to, and what our options are?" Most organisations, when we begin a licensing advisory engagement, discover the answer to all three parts of that question is no.

Why Oracle EBS Licensing Is Structurally Complex

Oracle E-Business Suite uses a dual-metric licensing model that combines user-based and module-based licensing. Every EBS deployment involves both dimensions simultaneously, and the rules governing each are specific enough that misunderstandings are the norm rather than the exception — even inside organisations that have been running EBS for a decade or more.

The Named User Plus metric

Under Named User Plus (NUP) licensing, every individual authorised to access any EBS module must hold a licence — regardless of how frequently, or even whether, they actually log in. Oracle's position is clear: access rights in the system constitute a licensing obligation. A user who was provisioned three years ago, changed roles, and has not logged in since still counts if their account remains active and they retain a system responsibility that grants EBS access.

In large, distributed organisations — particularly those that have experienced acquisitions, restructuring, or headcount reductions — this creates a significant compliance gap. Provisioning tends to be additive over time; de-provisioning is rarely as disciplined. When Oracle conducts a License Management Services (LMS) review, they request a full user access list per module. If the number of users with access in the system exceeds the number of NUP licences held, that is a finding — and Oracle prices the shortfall at full list price.

Module-by-module licensing

EBS modules are licensed individually. Financials, Supply Chain, Manufacturing, HR, Payroll, Procurement, and Project Management each carry their own licensing requirement. The fact that an organisation purchased the EBS suite historically does not mean they are entitled to use all modules — the specific modules covered in each contract must be verified against actual deployment. Organisations frequently discover that functional teams have enabled modules or configurations that were never explicitly licensed, often because an implementation partner activated them during an upgrade or customisation project without flagging the licensing implication.

Manufacturing and supply chain modules carry particular complexity. Bill of Materials, Work in Process, and Advanced Supply Chain Planning are individually licensed within the broader suite framework, and their activation often follows operational rather than commercial logic — meaning IT teams deploy what the business needs without checking the licence position first.

Processor licensing for Oracle Database

Alongside EBS, most deployments of Ricoh's complexity run Oracle Database — and Database licensing carries its own set of risks. Where Database is licensed on a Processor metric (rather than Named User Plus), the licence count is determined by the number of physical CPU cores, multiplied by a core factor defined in Oracle's processor core factor table. In virtualised environments — whether VMware, Hyper-V, or cloud — Oracle's rules on what constitutes a "partition" and whether licence minimums apply across the full physical host versus individual VMs are a persistent source of compliance exposure.

Oracle's position on virtualisation is intentionally restrictive. Unless the deployment uses Oracle VM or Oracle's own partitioning technology, Oracle may require licences covering the entire physical server, not just the VMs where Oracle Database runs. Organisations that have migrated to modern virtualisation infrastructure without rechecking their Oracle Database licence position often carry significant latent exposure.

The Support Cost Problem and the 8% Escalator

Oracle's standard support model charges 22% of net licence fees per year. That figure is fixed in the contract and increases by 8% per year. It does not matter whether the customer is using all of the features Oracle is packaging. It does not matter whether Oracle has delivered meaningful innovation to that product line. The 8% applies regardless — and because the base is compounding, the cumulative impact over a five-year period is substantial.

For an organisation paying £2 million per year in Oracle support today, a 8% annual increase means that bill becomes £2.94 million in five years without any additional licences being purchased. Over that same period, the cumulative support expenditure exceeds £12 million. That is the baseline scenario — before any true-up demands, audit findings, or licence expansion requests from Oracle's sales team.

For organisations that have decided, like Ricoh globally, that their long-term IT strategy involves transitioning away from several Oracle products, the calculus shifts. Continuing to pay Oracle 22% annually — on top of an 8% escalator — for support on software you are planning to migrate off is a particularly poor use of capital. Third-party support providers can supply equivalent functional coverage at approximately 50% of Oracle's support cost, with no annual escalation built in.

Third-Party Support: The Economics and the Risks

Third-party Oracle support has matured significantly as a market. Providers offer SLA-backed support for Oracle EBS and Oracle Database deployments, including custom code support, security patches, and compatibility fixes. The headline saving is typically 40–50% against Oracle's annual support fee, with multi-year fixed-rate pricing that eliminates the 8% escalation problem entirely.

Ricoh's own experience with third-party support is publicly documented. The company selected Rimini Street in 2024 to provide software maintenance and security services for its Oracle EBS and Oracle Database instances as it transitions its ERP strategy — saving the organisation significant annual expenditure while maintaining operational stability through the transition period.

But third-party support is not the right answer for every organisation, and it is not without risk. The key considerations are as follows:

• Oracle's reinstatement policy: If you leave Oracle support and later need to return, Oracle publishes a reinstatement fee of 150% of the support that would have been paid during the lapsed period — effectively a back-fee plus a 50% penalty. In practice, this figure is negotiable, but the starting position is punishing.
• Regulatory and certification requirements: Some industries require vendors to maintain current support status for compliance or insurance purposes. Verify your obligations before making the switch.
• ERP migration timelines: If a move to a new ERP system is genuinely underway — with a credible timeline and programme governance — third-party support can be an excellent bridge strategy. If the migration is aspirational rather than funded, the risk profile changes.
• New functionality access: Third-party support providers do not deliver access to Oracle's new release functionality. If your EBS roadmap depends on Oracle releases, staying on Oracle support is necessary. If you are in maintenance mode, it is typically not.

Optimising Before Any Decision: The Licence Position Review

Whether the outcome of an Oracle advisory engagement is third-party support, a negotiated renewal, a licence optimisation, or preparation for exit, the first step is always the same: establish what you actually have. Most organisations begin an advisory engagement without a definitive answer to three questions — what licences do we hold, what have we deployed, and where is the gap between the two.

A structured licence position review for an EBS and Database environment at Ricoh's scale involves several workstreams running in parallel. On the contractual side, advisors review every Oracle agreement — often scattered across multiple CSI numbers, entity names, and renewal cycles — to build a consolidated view of entitlements. On the deployment side, technical data is gathered from the EBS user access tables, module configuration screens, and Database inventory scripts to establish what is actually running and who has access.

The gap analysis that results from combining those two datasets is the foundation of the advisory strategy. Where there is over-licensing — licences held but not deployed — there is an opportunity to reduce the support base (subject to Oracle's contractual controls on licence return, which are restrictive but not absolute). Where there is under-licensing, the team quantifies the exposure and determines whether it should be remediated through the existing renewal process, negotiated as part of a broader restructuring, or addressed by removing unnecessary access from the system before Oracle conducts any formal review.

Oracle Q4 and the Negotiation Window

Oracle's financial year ends on May 31. The quarter from March through May — Oracle's Q4 — is the single highest-pressure period in Oracle's sales calendar. Oracle sales representatives carry significant quota pressure in this period and are typically empowered to offer discounts, commercial concessions, and structural deals that are materially harder to achieve in Q1 or Q2.

Organisations that time major Oracle negotiations — renewals, restructurings, CSI consolidations, ULA entries or exits — to close in Oracle's Q4 consistently achieve better commercial outcomes than those that renew on a contract calendar dictated by their own anniversary dates. The difference is not marginal. We routinely see 15–25% better outcomes on equivalent deals when they are positioned to close between March and May.

For European organisations managing large EBS and Database estates, the practical implication is to plan 12–18 months ahead. Licensing advisory engagements, licence position reviews, and commercial strategy work take time. Starting the process in February or March of the year you want to negotiate is too late to achieve the best result.

What Independent Oracle Advisory Looks Like in Practice

Redress Compliance works with European enterprise organisations running complex Oracle estates. The advisory model is structured around several distinct service types, deployed depending on the client's immediate situation and strategic direction.

Compliance and exposure review

An independent review of the Oracle licence position — entitlements versus deployment — establishes the actual compliance position and quantifies risk before Oracle does. This is the starting point for all other advisory work. It is also the most commonly deferred investment, with organisations often discovering their exposure only when Oracle initiates its own LMS review.

Support cost reduction

Where the analysis supports it, we structure the commercial argument for reducing the Oracle support base, switching to third-party support, or negotiating a multi-year cap on the annual escalation. The 8% annual increase is not a fixed law — it is a contract term, and in the right commercial context it is negotiable.

Renewal and exit strategy

For organisations whose long-term strategy involves transitioning away from Oracle EBS, we build the exit strategy: how to extract maximum value from the remaining Oracle tenure, manage the reinstatement risk associated with dropping support, and structure the migration programme so that Oracle's commercial leverage is minimised at each stage of the transition.

ULA and PULA advisory

Where Oracle is proposing an Unlimited License Agreement (ULA) or Perpetual Unlimited License Agreement (PULA) — often framed as the solution to complexity — we evaluate whether the economics actually work in the customer's favour. ULAs are Oracle's preferred mechanism for growing the support base; whether they are the right instrument for any given organisation depends on deployment trajectory, certification timing, and the product scope Oracle is willing to include.

Practical Guidance for CIOs Managing Oracle at Scale

Based on the advisory work we conduct across large European Oracle estates, there are several principles that consistently separate organisations that manage Oracle effectively from those that do not.

Know your CSI numbers: Most large Oracle estates have multiple Customer Support Identifiers, often consolidated imperfectly after acquisitions or organisational changes. Knowing exactly what is licensed under each CSI — and ensuring your contractual structure reflects your actual entity structure — is foundational to everything else.

Treat user access hygiene as a licence compliance activity: Quarterly reviews of EBS user access, de-provisioning inactive accounts, and maintaining accurate records of which users hold which responsibilities directly reduces Named User Plus exposure. The cost of doing this is negligible; the cost of not doing it can run to seven figures in an Oracle audit.

Understand your virtualisation position for Database: If Oracle Database is running in a virtualised environment, verify that your partitioning approach is Oracle-compliant. If it is not, the exposure compounds every quarter. Remediation is easier to structure when you are not under audit pressure.

Build the Oracle relationship around data, not conversations: Oracle's sales and LMS teams are skilled at conducting conversations that extract information the customer did not intend to share. Independent advisors help organisations structure their Oracle interactions so that commercial conversations are grounded in verified data from the client's own licence position review.

Start early: The organisations that achieve the best Oracle outcomes start their advisory engagement 12–18 months before the relevant contract event — renewal, ULA certification, or migration milestone. Starting early means having choices; starting late means accepting Oracle's preferred structure.

Working with Redress Compliance

Redress Compliance is an independent enterprise software advisory firm. We hold no Oracle reseller relationship, receive no referral fees from Oracle, and operate no audit services that would compromise the independence of our advice. Our team of former Oracle LMS auditors and enterprise licensing specialists has worked with large European organisations across a range of Oracle engagement types — from pre-audit preparation and support cost reduction to ULA negotiation and third-party support transition.

We work on a fixed-fee advisory basis or, where the engagement involves measurable savings outcomes, on our pay-when-we-save contingency model — where our fee is structured as a percentage of verified savings achieved. Organisations that are uncertain about the scale of the opportunity in their Oracle estate can begin with a scoped licence position review to establish the facts before committing to a broader programme.

If your Oracle estate is at the scale and complexity of a major European enterprise — multiple EBS instances, Oracle Database across a virtualised infrastructure, annual support fees in the millions — there is almost certainly an opportunity to improve both your compliance position and your cost trajectory. The starting point is understanding where you actually stand.