Client Profile
The client is a multinational pharmaceutical corporation and one of the world's largest producers of prescription medicines and vaccines. With operations across more than 90 countries and revenues exceeding $60 billion annually, the organisation maintains a substantial Oracle technology estate including Oracle E-Business Suite, Oracle Database, and a range of Oracle Database Options deployed across global finance, supply chain, manufacturing, and clinical operations.
The Oracle E-Business Suite deployment was originally implemented to support global financial consolidation and supply chain management, with a broad suite of EBS modules licensed to support anticipated operational requirements across a large number of jurisdictions. Over time, operational scope changes, business unit restructuring, and the partial migration of certain functions to cloud applications had reduced the active deployment of several EBS modules — but the licence and support obligations had not been adjusted to reflect the reduced scope.
The Challenge
The client's internal licence management review identified that a number of Oracle E-Business Suite modules — including Oracle Projects, Oracle Advanced Supply Chain Planning, and several Human Capital Management modules — had been licensed at a user count that significantly exceeded active deployment. In some cases, modules had been licensed for planned rollouts in jurisdictions where the rollout had subsequently been cancelled. In others, modules had been deployed, then superseded by cloud applications, without the Oracle EBS licences being formally terminated.
The estimated over-licencing was material: the internal review suggested that approximately 35% of the Oracle application support obligation — approximately $700,000 annually — was attributable to modules or user counts that did not correspond to active deployment. However, the internal team lacked the contractual expertise to execute termination safely, and Oracle's commercial team had responded to initial informal enquiries about support reduction by indicating that any licence reduction would require a full Oracle audit of the EBS estate before Oracle would agree to revise the support schedule.
The prospect of an Oracle audit was unacceptable to the client. The global pharmaceutical sector is subject to extensive regulatory scrutiny, and an Oracle licence audit during an active regulatory inspection period carried reputational and operational risk that outweighed the financial benefit of a poorly structured licence reduction. The client needed an approach that achieved the commercial objective without triggering Oracle's audit mechanism.
The Approach
Redress Compliance's first action was to conduct a proactive deployment analysis — identical in scope and methodology to the analysis Oracle would conduct in a formal audit, but conducted by the client before any Oracle engagement. This proactive analysis served two purposes: first, to establish the accurate deployment baseline that would underpin the commercial negotiation; second, to identify any compliance risks in the retained deployment that needed to be addressed before Oracle became involved in a formal process.
The proactive analysis confirmed the internal estimate substantially. Oracle Projects and Advanced Supply Chain Planning were licensed at user counts significantly above active deployment, with the excess attributable to planned rollouts that had not proceeded. The HCM module over-licencing reflected the partial migration to a cloud HCM platform, with the Oracle EBS HCM licences having been retained rather than terminated when the cloud platform went live.
Critically, the proactive analysis also identified one area of potential under-licencing — a recently deployed Oracle Database integration with the clinical operations platform that had not been factored into the original licence calculation. This finding was disclosed to Oracle as part of the commercial negotiation, which served two purposes: it established the client's credibility as a good-faith negotiating partner, and it eliminated the risk that Oracle's own audit would subsequently identify this issue and use it to contest the terms of any agreed reduction.
The commercial negotiation with Oracle was structured around a net position: the client proposed to terminate the over-licenced application modules and increase the Database licence position to reflect the clinical operations deployment, with Oracle accepting the net position as a clean resolution of the licence position. Oracle's commercial team — having initially insisted on a formal audit — accepted the net position in light of the quality of the client's deployment evidence and the constructive framing of the engagement.
The Outcome
The agreed revised support schedule reduced the Oracle application support obligation by $700,000 annually — a 35% reduction from the pre-engagement baseline. Applied over three years, with Oracle's standard 5% annual support escalation factored in, cumulative savings totalled $2.1M. The Oracle Database increase partially offset the application saving, but the net Oracle spend trajectory was materially improved versus the pre-engagement position.
No Oracle audit was conducted. Oracle's written confirmation of the revised support schedule — provided as part of the commercial resolution — serves as documentation that the client's Oracle position has been reviewed and agreed, which provides audit protection going forward. Oracle's ability to contest the current licence position in a future audit is substantially limited by the existence of this agreed documentation.
The proactive disclosure of the Database under-licencing, rather than creating a problem, created a positive commercial dynamic. Oracle's commercial team noted the client's transparency as a factor in accepting the proposed resolution structure. This outcome is consistent with our broader advisory experience: clients who engage Oracle proactively, with evidence and a constructive commercial proposal, consistently achieve better outcomes than those who attempt to execute licence reductions without Oracle engagement.
Key Takeaways
The pharmaceutical sector's regulatory sensitivity creates specific dynamics in Oracle licence management. The risk of an Oracle audit triggering operational disruption during an active inspection period is a genuine constraint that shapes the commercial strategy available to organisations in this sector. The proactive audit approach — conducting the client's own audit before Oracle does — is the most effective way to eliminate this risk while simultaneously building the evidence base for commercial negotiation.
Net position negotiation — offering Oracle a disclosure of under-licencing in exchange for acceptance of over-licencing reductions — is commercially effective but requires precise analysis. The under-licenced position must be identified with confidence, the licence calculation must be accurate, and the commercial proposal must be framed as a good-faith resolution rather than an adversarial demand. This approach is only viable with specialist advisory support.
The $2.1M saving in this case was not large relative to the client's overall Oracle spend. But the principle generalises: any organisation with a mature Oracle EBS deployment that has undergone significant operational change has a high probability of carrying material shelfware. The cost of the analysis is typically recovered in the first year of savings by a significant multiple.
Independent proactive deployment analysis and commercial negotiation. Buyer-side only. We build the evidence base and manage the Oracle engagement.