SAP Licensing Guide: Everything IT and Procurement Leaders Need to Know

1. Introduction: The SAP Licensing Landscape in 2026

SAP represents one of the most significant and most mismanaged cost drivers in enterprise IT. The average mid-market SAP environment costs between 15 and 45 million dollars annually across licensing, maintenance, hosting, and professional services. Procurement and IT leaders face a critical challenge: SAP's licensing model is intentionally complex, deliberately opaque, and structured to extract maximum value from customers who lack domain expertise.

This guide exists because the information asymmetry between SAP and its customers is profound. SAP's sales teams understand the licensing model in forensic detail. Most procurement leaders, IT operations teams, and even many consultants operate with incomplete mental models that systematically underestimate costs and overestimate the value delivered by SAP's cloud positioning.

The stakes are substantial. SAP licensing audit findings routinely identify 5 to 25 million dollars in uncompensated usage. The compliance obligation often takes customers by surprise because they fundamentally misunderstood their licence classification, their user population measurement, or the scope of features included in a given SKU.

This guide provides the complete taxonomy and strategic context that IT and procurement leaders require to manage SAP licensing with confidence, negotiate renewals effectively, and defend against audit exposure. We cover the full breadth of SAP's licensing portfolio: Named User licence types, Package and Engine licences, Digital Access and the DDLC metric, deployment models spanning on-premise, private cloud, and public cloud, the strategic implications of S/4HANA migration, the true contents of RISE with SAP contracts, BTP credit mechanics, SuccessFactors pricing, and the audit mechanics that SAP uses to construct and enforce compliance obligations.

2. SAP Licence Types: A Complete Taxonomy

SAP's licensing model is built on two broad categories: Named User licences and Package or Engine licences. Understanding the distinction between these categories is foundational to any meaningful licensing discussion.

Named User Licences: The Four Categories

SAP's Named User licence types are stratified by the scope of functionality available to each user. The licence type assigned to a user determines the monthly subscription cost and the features that user can access within SAP applications.

Professional Users represent the highest tier of Named User licensing. A Professional User can access the full breadth of an SAP application's functionality including core transactional capabilities, reporting, analytics, and administrative features. Professional Users are licensed at approximately 12 to 18 dollars per month depending on the application, the contract term, the deployment model, and the volume of users. Professional Users drive the highest licensing cost for most organisations and should be the primary focus of licensing optimisation effort.

Functional Users occupy the middle tier. Functional Users can access a defined subset of application functionality—typically transactional processes within a specific module or business process area—but lack access to analytical features, administrative functions, or cross-module capabilities. Functional Users are licensed at approximately 6 to 12 dollars per month. The distinction between a Professional User and a Functional User is often where licensing disputes begin, because the boundary between "defined functional scope" and "full application access" is subjective and contested.

Productivity Users represent a low-cost tier for users who need access to reporting, analytics, or read-only views of transactional data without the ability to create or modify transactions. Productivity Users are licensed at approximately 2 to 6 dollars per month. The Productivity User category is frequently misapplied—organisations license Productivity Users for individuals who actually need Functional or Professional capability, leading to audit findings and true-up obligations.

Developer Users are specifically licensed for system development, testing, and technical integration work. Developer Users can access sandboxed environments and development systems but are restricted from production use. Developer Users are typically licensed at a flat annual rate of 1,500 to 4,000 dollars per person depending on the platform and the scope of licensed functionality. Developer licence miscalculation is common—many organisations extend Developer licences to individuals who should not hold them, or fail to recognize that genuine development work requires Developer licensing.

Package and Engine Licences

Package and Engine licences represent an alternative licensing model for scenarios where Named User licensing is impractical or where transactional volume rather than user headcount drives the licensing baseline.

Package licences entitle an organisation to run a defined business process or module for an unlimited number of users for a flat fee. For example, a Package licence might cover "Travel Management" for unlimited users, or "Recruitment" for an unlimited population. Package licences are typically quoted as a one-time purchase plus annual maintenance, ranging from 75,000 to 250,000 dollars depending on the module. Package licences are valuable for organisations that have high user churn, seasonal or temporary user populations, or where user measurement is problematic.

Engine licences are consumption-based and priced on the volume of transactions processed. SAP Gateway Engine, for example, is licensed based on the number of application-to-application integrations or API calls processed monthly. Engine licences are useful for organisations with volatile or unpredictable consumption patterns, but require disciplined log management and consumption monitoring to avoid unexpected overages.

3. Digital Access and the DDLC Model

Digital Access is SAP's most litigated and most misunderstood licence type. Digital Access was introduced in 2018 as a replacement for the older "Indirect Access" licensing model. The distinction is material: Indirect Access applied to users who accessed SAP systems through non-SAP applications or middleware. Digital Access applies to any usage of SAP data, functionality, or reports through any non-primary interface—and the definition is expansive.

DDLC: Document Driven Licence Charge is the mechanism SAP uses to quantify Digital Access exposure. DDLC measures the extent to which SAP data is accessed or reported through non-primary channels and translates that access into an equivalent number of Named User licences required to cover the usage.

The DDLC methodology works as follows: SAP audits your system logs and identifies all transactions or queries that accessed SAP data without using SAP's primary user interface. This includes reports generated through custom applications, data extracted through APIs, queries from BI tools, exports to Excel, mobile app usage, and any other non-standard access pattern. SAP then calculates the volume and frequency of these transactions, maps them to an equivalent user population, and presents a licensing claim for the "missing" Named User licences that should have covered this access.

The DDLC calculation is deliberately generous to SAP. The methodology assumes that all Digital Access represents genuine business usage that required Named User licensing. In practice, many Digital Access use cases—automated batch reports, system-to-system integration data feeds, read-only dashboards, or legacy application data extracts—could be covered under exemptions or alternative licensing mechanisms that SAP rarely volunteers or actively discusses.

DDLC disputes are common because the scope of Digital Access is ambiguous and the measurement methodology is opaque. A typical scenario: an organisation extracts SAP financial data into a data warehouse for reporting purposes. SAP's audit concludes that this extraction represents Digital Access to multiple finance modules and charges for 15 to 25 additional Named User licences. The customer argues that the extraction is a one-time batch process not requiring per-user licensing. The dispute often settles somewhere between these positions, but the initial claim is typically inflated.

The Digital Access Adoption Programme (DAAP) is SAP's amnesty programme for customers with pre-existing Digital Access exposure. DAAP offers discounted pricing for customers to "regularise" their Digital Access usage through a one-time payment or trade-in of equivalent licence value. For organisations with significant Digital Access exposure, DAAP can offer meaningful savings compared to the ongoing true-up obligations that otherwise accumulate.

4. SAP Deployment Models: On-Premise, Private Cloud, Public Cloud

SAP offers three deployment models: on-premise, private cloud (RISE with SAP), and public cloud (S/4HANA Cloud Public Edition). The deployment model selected has profound implications for licensing costs, maintenance obligations, and flexibility.

On-Premise Deployment

On-premise SAP deployments run on customer-controlled infrastructure, either in the customer's own data centre or in a co-located facility. On-premise licensing follows the traditional model: customers purchase perpetual licences and pay annual maintenance at approximately 22 percent of net licence value.

On-premise deployments require active system administration, operational infrastructure, routine patching and upgrades, and dedicated infrastructure cost. The "hidden" costs of on-premise are substantial—infrastructure, storage, backup, recovery, security patching, and system administration typically run 40 to 60 percent above the published licence and maintenance cost.

On-premise remains the deployment model for approximately 70 percent of installed SAP instances, primarily because customer organisations have large existing investments in on-premise infrastructure, because migration to cloud introduces operational risk, and because for very large user populations, on-premise can be more cost-effective than cloud when total cost of ownership is calculated holistically.

RISE with SAP: Private Cloud

RISE with SAP is SAP's managed private cloud offering. RISE contracts are subscription-based, bundling infrastructure, platform services, applications, support, and a defined level of implementation and optimisation services into a single monthly fee.

RISE is fundamentally different from on-premise licensing. Instead of purchasing perpetual licences, customers subscribe to Named User capacity on a monthly basis. Instead of paying annual maintenance, infrastructure, and support costs separately, RISE bundles everything into a single contract line.

RISE contracts are typically quoted based on Named User capacity and average annual contract values range from 10 to 30 million dollars for mid-market deployments. The pricing model is opaque—SAP calculates RISE pricing using proprietary internal methodologies that typically result in RISE being 20 to 40 percent more expensive than the equivalent on-premise licensing plus infrastructure plus support costs.

Critical RISE Inclusion and Exclusion Boundaries: RISE with SAP explicitly includes the application software, a defined level of cloud infrastructure, baseline support, and a limited amount of professional services (typically 100 to 200 hours annually depending on the contract). RISE does NOT typically include: third-party application integrations, custom development beyond the contracted services, advanced analytics capabilities (such as SAP Analytics Cloud or embedded analytics), SuccessFactors implementation or optimisation, significant business process transformation, or change management services. Customers frequently discover that their desired capabilities are outside the RISE contract boundary after signing, requiring expensive add-on engagements.

S/4HANA Cloud Public Edition

S/4HANA Cloud Public Edition is SAP's fully managed public cloud offering. This is a multi-tenant environment where SAP manages all infrastructure, platform updates, and patching. Customers access the application through SaaS-style subscriptions, with pricing based on Named User capacity.

S/4HANA Cloud Public Edition pricing is substantially lower than RISE—typical mid-market deployments cost 40 to 60 percent less than equivalent RISE contracts. The trade-off is that customisation options are constrained. Customers cannot install custom code, cannot heavily customise standard business processes, and must accept frequent updates and feature changes controlled by SAP rather than the customer organisation.

S/4HANA Cloud Public Edition is rapidly becoming SAP's strategic deployment direction for new customers and migrations. SAP is deemphasising on-premise and RISE for net new business, positioning cloud as the standard path forward.

5. SAP ECC, ERP, and the S/4HANA Migration Imperative

SAP ECC (ERP Central Component) is the classic SAP enterprise resource planning system that has dominated enterprise deployments for 25 years. In 2015, SAP released SAP S/4HANA as the "next generation" ERP platform, built on SAP's HANA in-memory database architecture.

SAP ECC Mainstream Support Ending: SAP's stated position is that ECC mainstream support ended on December 31, 2025 (note: SAP's fiscal year ends December 31). However, SAP has extended ECC support through 2027 through an extended support programme. Most organisations currently running ECC have until late 2027 to complete migration to S/4HANA or a non-SAP alternative, or face premium support fees and escalating maintenance costs.

The S/4HANA migration is more than a technical upgrade—it changes the licensing baseline fundamentally. SAP's licensing model for S/4HANA is more granular, more modules-based, and frequently results in higher licence counts and costs than the equivalent ECC deployment. Organisations migrating from ECC to S/4HANA frequently encounter licensing "re-baselining" where SAP requires a new licence baseline measurement for the S/4HANA environment, often resulting in audit findings and true-up obligations of 10 to 30 percent of current spend.

The S/4HANA transition is where many procurement leaders first encounter serious licensing disputes. The migration creates an opportunity for SAP to reassess licensing, and SAP systematically uses this reassessment to increase licence counts and costs. Organisations planning S/4HANA migrations should plan licensing reviews and baseline measurements as part of the migration programme, not as an afterthought.

6. RISE with SAP and SAP Cloud ERP Private Edition

RISE with SAP is the umbrella programme covering both dedicated private cloud (SAP Cloud ERP Private Edition) and managed infrastructure services. The programme includes implementation services, optimisation consulting, and a defined level of ongoing support.

A typical RISE contract structure includes: S/4HANA Cloud Private Edition or on-premise S/4HANA running on SAP-managed infrastructure, a subscription for a defined number of Named Users, a baseline allocation of professional services (typically 100 to 200 hours), maintenance and support through SAP Premium Support, cloud infrastructure provisioning and management, and compliance and security baseline features.

RISE contracts are extraordinarily complex. The contract document typically runs 50 to 100 pages and includes detailed service level agreements, escalation procedures, limitation of liability provisions, and numerous exclusions and exceptions. Organisations signing RISE contracts without independent legal and technical review frequently discover misalignments between their expectations and the contract's actual terms.

RISE Pricing Methodology: SAP quotes RISE pricing using a methodology that typically includes: a per-Named-User monthly subscription fee (averaging 50 to 150 dollars per user per month depending on modules), infrastructure costs based on estimated monthly usage (typically 20,000 to 100,000 dollars per month for mid-market deployments), professional services (billed separately at 180 to 250 dollars per hour if the baseline allocation is exceeded), and premium support (typically included in the base price or charged as an upcharge).

The pricing model creates perverse incentives. SAP wants to sell as many Named User subscriptions as possible because each additional user increases recurring revenue. Organisations benefit from minimising Named User counts and shifting to alternative licence types where possible. This fundamental misalignment drives licensing disputes and makes RISE negotiations contentious.

7. SAP BTP: Business Technology Platform Licensing

SAP BTP is a consumption-based platform-as-a-service offering that covers application integration, analytics, extensibility, and development services. BTP pricing is consumption-based rather than per-user, which creates a different set of cost management challenges than traditional licensing.

SAP BTP Credit Model: BTP usage is measured in "SAP Cloud Credits," a standardised unit of consumption. Different BTP services consume credits at different rates. For example, an integration with a specific throughput level might consume 10,000 credits monthly, while a modest analytics instance might consume 5,000 credits monthly. SAP publishes credit consumption rates for various services, but the rates are complex and the total consumption is difficult to predict without detailed sizing and testing.

BTP contracts typically include an annual commitment of cloud credits (ranging from 50,000 to 500,000 credits annually for most organisations) plus overage charges for usage exceeding the commitment. The per-credit pricing decreases with larger commitments—customers committing to larger annual amounts pay lower per-unit rates.

BTP consumption is notoriously difficult to forecast. Organisations frequently estimate BTP usage conservatively, purchase a modest commitment, and then encounter unexpected overage charges when actual usage exceeds projections. Conversely, organisations sometimes over-estimate and purchase more credits than they consume, resulting in waste.

BTP represents approximately 5 to 15 percent of total SAP spend for most organisations with active integration and analytics programmes. BTP cost management requires disciplined consumption monitoring, regular consumption forecasting, and contractual mechanisms that allow for commitment adjustments during the contract term.

8. SuccessFactors, Ariba, Concur and Other Cloud Applications

SAP's cloud application portfolio extends beyond ERP to include human capital management (SuccessFactors), procurement (Ariba), travel and expense (Concur), and other specialised applications.

SuccessFactors PEPM Pricing: SuccessFactors is priced on a per-employee-per-month (PEPM) basis. The organisation subscribes for a specific number of employees and pays a monthly fee for each. PEPM pricing typically ranges from 3 to 8 dollars per employee per month depending on the modules selected (core HR, talent management, learning, workforce planning, etc.) and the size of the employee population. A 10,000-person organisation licensing full SuccessFactors might incur 500,000 to 1,000,000 dollars annually in SuccessFactors cost alone.

SuccessFactors PEPM pricing creates cost visibility challenges. The total cost is highly sensitive to the employee population size, and organisations with headcount volatility or significant employee lifecycle events (acquisitions, divestitures) can encounter unexpected cost variations. PEPM pricing also drives perverse incentives around contractor classification—organisations sometimes avoid using SuccessFactors for contractors or extended workforce because the per-employee cost appears high, even when contractor coverage would provide business value.

Ariba and Concur: These are subscription-based cloud applications with simpler pricing models than SuccessFactors. Ariba (procurement) is typically priced based on the number of active supplier relationships or the volume of transactions processed. Concur (travel and expense) is priced per active user or per submitted expense report. These applications represent lower cost additions to the SAP portfolio but often drive unexpected costs when usage volume increases significantly.

9. The 22% Annual Maintenance Model

A foundational element of SAP licensing economics is the annual maintenance rate. SAP charges annual maintenance at approximately 22 percent of the net licence value (NLV). If an organisation purchases 10 million dollars in SAP licences, annual maintenance costs approximately 2.2 million dollars per year, indefinitely.

The 22 percent rate is compound—it applies to the current licence base at each renewal. If the licence base grows through true-ups, new modules, or migrations, the maintenance obligation grows proportionally.

Maintenance cost is a leverage point in SAP negotiations. For organisations approaching licence refreshes or migrations, structuring the deal to minimise the incremental licence base directly reduces the maintenance obligation going forward. A negotiation that results in 20 percent lower licence costs also results in 20 percent lower annual maintenance costs in perpetuity.

Third-party maintenance vendors like Rimini Street and Spinnaker Support offer SAP maintenance services at approximately 50 percent of SAP's rates. For organisations willing to accept the operational and support changes involved in switching to third-party maintenance, this represents an immediate 50 percent cost reduction in the maintenance line item. Over a 10-year period, the cumulative savings from third-party maintenance can be 15 to 25 million dollars for large SAP installations.

10. SAP Audit Mechanics: How SAP Measures and Enforces

SAP conducts audits to verify licence compliance and identify uncompensated usage. Understanding SAP's audit methodology and process is critical because audit findings represent the primary mechanism through which licensing disputes arise.

System Measurement and LAW

SAP's audit process typically begins with system measurement using SAP's LAW (Licence Auditing Workbench) tool. LAW is an SAP application that extracts transaction logs, usage data, and system configuration from the customer's SAP environment. LAW analyzes this data and produces reports on the user population, licence utilisation, Digital Access exposure, and potential licensing discrepancies.

LAW reports are the evidentiary foundation for SAP audit findings. The reports identify users, their licence types, their transaction patterns, their system access frequency, and systems accessed. LAW also identifies Digital Access patterns—transactions and queries that accessed SAP data through non-primary interfaces.

USMM: User System Measurement Monthly is an automated daily/monthly measurement process that runs on the SAP system and continuously monitors user population and licence utilisation. Most modern SAP systems have USMM running continuously, feeding data to SAP's backend monitoring systems. This data is the primary source for audit assertions about who is using the system, when, and how.

System Landscape Analysis

SAP's System Landscape Analysis (SLA) process reviews the customer's entire SAP ecosystem—including development systems, test systems, training systems, and production systems. SAP's position is that all systems require equivalent licensing unless explicitly exempted. Organisations often believe that development and test systems are unlicensed, but SAP's audit conclusions often assert that full licensing is required for all non-production systems as well.

The Audit Finding and Dispute Process

When SAP identifies what it believes is licensing non-compliance, SAP's Standard Audit Requirements (SAR) process is triggered. SAP provides the customer with a detailed finding report, citing specific users, transactions, systems, and the licence basis claimed by SAP to cover the usage. The customer has an opportunity to respond to the finding—either accepting the finding or providing contradictory evidence that the licensing claim is incorrect.

Audit disputes often revolve around technical questions: What constitutes Digital Access? Which systems require licensing? What is the correct user population measurement? These questions are legitimately ambiguous, and SAP's audit conclusions are not always technically defensible, but SAP often leverages the cost and complexity of formal dispute processes to negotiate settlements favoring SAP's position.

11. Indirect Access and the Pre-2018 Model

Before Digital Access was introduced in 2018, SAP used an "Indirect Access" licensing model. Indirect Access applied to users who accessed SAP systems through external applications or middleware. The distinction between Indirect Access (pre-2018) and Digital Access (post-2018) is important for organisations with legacy systems or hybrid deployments still using older licence models.

Many organisations have been successfully defending against Digital Access claims by demonstrating that their access patterns fall into exemptions or alternative measurement methodologies that SAP underemphasises during audits. However, the regulatory environment has shifted in SAP's favour—SAP has improved its measurement tools, its audit methodology has become more rigorous, and courts/arbitrators have increasingly sided with SAP's expansive interpretation of what constitutes chargeable usage.

12. SAP Licence Optimisation: Where the Savings Are

Licensing optimisation identifies and implements specific changes to the licence portfolio that reduce cost while maintaining or improving operational capability. Optimisation opportunities typically exist in five areas:

User Reclassification

Many organisations license users at higher levels than required. A user licensed as a Professional User might actually need only Functional or Productivity User access. Reviewing the actual usage of the user population and reclassifying users to the minimum required licence type can reduce licence cost by 20 to 30 percent.

Digital Access Remediation

Organisations with Digital Access exposure can often reduce the claimed liability through technical remediation: building dedicated read-only APIs rather than extracting data through standard query tools, reducing report distribution frequency, or implementing access controls that limit the scope of exposed data. These changes often reduce Digital Access exposure by 30 to 50 percent without changing operational capability.

Package Licence Substitution

Organisations with high user churn or seasonal users often benefit from shifting from Named User licensing to Package licences for specific modules. If 1,000 temporary employees use a specific module seasonally, licensing them through a Package licence rather than individual Named User licences can reduce cost by 40 to 60 percent.

Module Elimination

Many organisations are licensed for SAP modules that provide marginal business value or that duplicate functionality available in other systems. Removing licensing for unused or low-value modules can reduce cost by 10 to 25 percent with minimal operational impact.

Deployment Model Optimisation

For organisations considering deployment model changes (such as on-premise to cloud migrations), cost modelling should be sophisticated. Cloud deployment often appears cheaper on a per-user basis but can be more expensive in aggregate when total user population, infrastructure alternatives, and contract terms are fully considered.

13. Negotiation Strategy: Using SAP's Fiscal Year and Your Leverage

SAP's fiscal year ends on December 31. Sales organisations are incentivised to close deals before year-end to maximise FY commissions and revenue targets. This creates negotiation leverage: customers who initiate licence renewals or renegotiations in October or November have substantially more leverage than customers initiating negotiations in January.

Additional leverage points include: migrating to non-SAP alternatives (SAP fears customer attrition), consolidating multiple SAP instances or contracts into a single negotiation (larger deals receive better discounts), shifting to cloud or on-premise (changing deployment models gives the customer leverage to renegotiate pricing), and timing negotiations to coincide with S/4HANA migrations or major system upgrades (when system changes create natural renegotiation moments).

The most successful SAP negotiations combine technical licensing expertise (understanding what licence types and quantities are actually required) with business leverage (having a credible alternative path or deadline that creates urgency for SAP to move). Procurement teams that excel at SAP negotiations typically combine internal licensing expertise with external advisory support and maintain a "walk away" position that gives SAP legitimate concern about losing the customer.

14. Ten Priority Recommendations for SAP Licence Management

1. Establish a Licensing Governance Committee that meets quarterly and includes IT operations, procurement, finance, and audit representation. This committee should review licence utilisation, audit risk, optimisation opportunities, and contract renewal schedules.

2. Implement Continuous User Measurement through LAW or equivalent monitoring. Do not rely on annual or infrequent measurement. Continuous measurement identifies user population changes, supports audit defence, and enables optimisation.

3. Conduct a Baseline Licensing Assessment before any major system change (migration, upgrade, new module implementation). This baseline documents the current licensing position and creates an audit trail for the baseline change.

4. Build Digital Access Defences Proactively. Review your integration architecture and data access patterns. Where possible, implement dedicated APIs or read-only data access mechanisms to limit Digital Access exposure.

5. Understand Your Actual Usage against your licence portfolio. Many organisations are paying for licence capacity they do not use. Understanding actual usage informs both audit defence and optimisation opportunities.

6. Plan S/4HANA Migrations with Licensing as an Explicit Workstream. Migration timelines should include baseline licensing measurement, cost modelling of S/4HANA licensing, and contract renegotiation planning.

7. Leverage SAP's Fiscal Year in Negotiations. Initiate critical negotiations (renewals, migrations, large new implementations) in Q4 (October-December). This timing creates maximum pressure on SAP to move.

8. Evaluate Third-Party Maintenance Alternatives. Switching from SAP Support to Rimini Street or Spinnaker Support reduces maintenance cost by approximately 50 percent. For large SAP installations, this switch can save 10 to 20 million dollars over 10 years.

9. Document All Licensing Decisions and Assumptions. When the organisation makes a licensing decision or changes a licence classification, document the business rationale and technical basis. This documentation supports future audit defence.

10. Maintain Vendor Independence in Licensing Reviews. Do not allow SAP's account team to drive your licensing strategy or audit responses. Ensure that independent licensed advisors review all significant licensing changes and audit findings.

15. Conclusion

SAP licensing is complex, high-stakes, and deliberately opaque. The licensing landscape continues to evolve—SAP is shifting aggressively toward cloud-based subscription models (RISE and S/4HANA Cloud), away from perpetual on-premise licensing. This shift gives SAP the opportunity to re-baseline pricing and reposition its margin expansion as a result of migration rather than pricing power.

Organisations that successfully manage SAP licensing share common characteristics: they maintain independent licensing expertise rather than relying solely on SAP guidance, they understand their actual usage and cost drivers in forensic detail, they maintain disciplined governance around licence changes and optimisation, they time critical negotiations to leverage SAP's business incentives, and they maintain credible alternatives that give them walk-away leverage in negotiations.

The opportunity for procurement and IT leaders is substantial. 20 to 40 percent cost reductions are achievable through systematic licensing optimisation, disciplined user management, and strategic negotiation. The typical 15 to 45 million dollar annual SAP cost burden can be reduced by 3 to 18 million dollars through deliberate management and expert execution.