SAP Enterprise Support vs PCNS: Cost Reduction Strategies

Before you reduce or change support tiers, you must know what you actually consume. Most organisations have never conducted a forensic analysis of their SAP support utilisation. The result is that SAP controls the narrative on "what level of support you need" — when in fact you have concrete usage data that should drive the decision.

What to measure:

• VDM (Virtual Diagnostic Manager) sessions. Count how many technical diagnostic sessions your team actually runs per quarter. Most enterprises consume 10–30% of their theoretical allocation. If you're paying for 100 sessions annually and consuming 20, you're funding unused capacity.
• Engineering support tickets. Track how many tickets you open with SAP per year, by severity level. Compare this to your service level agreements (SLAs). If your tickets are consistently non-critical and non-urgent, enterprise support's premium response times are wasted spend.
• SAP Launchpad and solution manager access. Count unique login events, patch download activity, and system maintenance tasks. This shows whether your team is actually using the tools that justify enterprise support cost.
• Knowledge base usage. Count how many of your tickets are self-resolved through SAP's knowledge base vs. requiring engineer intervention. High self-resolution rates suggest your team could operate effectively on PCNS or hybrid support.

Document this data over a 6–12 month period. Present it to your SAP account team before renewal. This transforms the negotiation from "we want to pay less" (which SAP dismisses) to "we want to optimise our spend based on actual consumption data" (which SAP respects because it's defensible).

PCNS (Platform Connection Support) is SAP's lower-cost support tier. It costs 17% of licence fees vs. 22% for Enterprise Support — a 5% absolute reduction, roughly 23% of your support spend. The qualification criteria are specific:

• Your SAP system must be stable (no major upgrades or migrations planned for 18+ months).
• Your technical team must have intermediate-to-advanced SAP experience; SAP won't provide as much hand-holding.
• You cannot be in an active SAP Safeguarding Engagement or compliance remediation with SAP.
• Your system must run on supported SAP releases (current or one release back).

If you meet these criteria, the PCNS case is straightforward: you don't need the higher-cost SLAs or the premium engineer availability of Enterprise Support. You need reliable access to SAP's knowledge base, patch management, and emergency support for critical issues. PCNS delivers that at 17%.

What you give up: Guaranteed 2-hour response for critical issues (vs. 4 hours on PCNS), priority engineer assignments, and proactive system monitoring. If your audit shows you rarely trigger critical-severity tickets, these aren't real losses — they're theoretical services you never used.

How to make the case: Present your utilisation audit alongside the PCNS qualification checklist. SAP will have risk concerns; address them with evidence. For example: "We have no planned major upgrades through 2027. Our technical team has 6+ years of SAP operations experience. Our last 12 months show zero critical-severity tickets and average time-to-resolution of 8 hours, all below our current SLA. We are PCNS-eligible and request transition at the next renewal."

PCNS qualification typically saves £250K–£800K annually depending on your licence base, with zero system impact if you've properly audited your needs.

SAP's published support rates (22% for Enterprise, 17% for PCNS, 12% for Application Management Services) are not fixed. They are negotiation starting points. At contract renewal, with competitive leverage, you can discount these rates by 10–25% depending on your contract size and timing.

The mechanics: SAP's standard language says "support is set at 22% of licence fees." This means if your licence base is £10M, support is £2.2M annually. But "licence fees" is ambiguous — it can mean list price (before discount) or net invoice price (after discount). If you negotiated a 40% discount on licences, your net is £6M, and support at 22% of net is £1.32M, not £2.2M.

That £880K difference is not accidental — it's standard SAP contract language. You recover it through contract negotiation.

The negotiation approach:

1. Time your move. Begin the conversation 90 days before your renewal (your notice-to-renew window). SAP's sales incentive kicks in at this point; they want to lock in your renewal.
2. Present third-party maintenance costs as a real option. Rimini Street and Spinnaker Support provide full support coverage at 8–12% of licence fees. This is a legitimate alternative, and SAP knows it. Position your negotiation as: "We're evaluating third-party maintenance. We prefer to stay with SAP, but we need pricing that reflects the market — 12–15% rather than 22%."
3. Anchor to your utilisation data. Don't ask for a discount in the abstract. Show SAP: "Our support consumption data shows we use 30% of available VDM sessions and trigger no critical-severity tickets. We're requesting support pricing be indexed to a 15% rate reflecting our actual utilisation profile."
4. Lock in multi-year terms. A three-year commitment to a lower support rate is more valuable to SAP than a one-year renewal. Use this: "If we can agree on a fixed 15% support rate for three years, we'll commit now and avoid a competitive process."

In practice, a well-prepared organisation negotiates 15–18% support rates at renewal, vs. the published 22%. For a £10M licence base, that's £400K–£700K annual savings.

This is the single highest-impact cost reduction strategy. Support fees are calculated as a percentage of licence fees. If you reduce your licence base by 30%, your support fees fall 30% automatically, with no negotiation required.

How to identify excess licensing:

• Dormant user discovery. Pull a 180-day login audit on your SAP user base. Identify users who have not logged in for 6 months. If they're still licensed as Named User Professional (the most expensive type), you're paying £4K–£8K annually per dormant user in licence fees alone.
• User reclassification. Run a forensic review of user transactions and module access. Many users licensed as "Professional" only access a subset of modules — they should be reclassified to Limited Professional or Employee, at 30–60% of Professional cost.
• Role-based access analysis. Compare your actual role structure to your user licensing. Customer service teams don't need Professional user licenses if they only query invoice data. Finance teams reclassified from Professional to Finance Employee save 50% per user.

Implementation: Conduct a forensic right-sizing engagement 6 months before your renewal. Deactivate dormant users, reclassify active users to lower-cost types, and implement governance to prevent re-growth. The result is a lower baseline licence count for your next contract.

Financial example: An enterprise with 2,000 licensed SAP users discovers:

• 180 dormant users still licensed at Professional (£750/user/year) = £135K wasted annually
• 320 users reclassifiable from Professional to Limited Professional (50% cost difference) = £480 × 320 × 1 = £153.6K annual savings
• Total licence base reduction = £288.6K annually

At 22% support rate, that translates to an additional £63.5K annual support fee reduction. Combined: £352K saved on the next renewal, purely from right-sizing.

The third-party maintenance market offers genuine alternatives to SAP Enterprise Support. Rimini Street (public company, £1B+ revenue) and Spinnaker Support (private, focused on mid-market) both provide full production support coverage at 8–12% of licence fees — roughly half the cost of Enterprise Support.

What you get from third-party maintenance:

• 24/7 technical support with certified SAP engineers.
• Emergency patch delivery (in many cases faster than SAP).
• Configuration and performance optimization advice.
• No forced upgrades — your release roadmap is yours to control.

What you lose:

• SAP's proprietary diagnostic tools (USMM, STAR) are not available — diagnostics rely on industry-standard monitoring.
• Certain embedded services (e.g., SAP Solution Manager as a managed service) require SAP support and cannot be sourced from third parties.
• SAP audit compliance language may be stricter with third-party support; this requires contract review.

A third-party maintenance transition is appropriate if:

• Your system is mature and stable (no major upgrades planned for 3+ years).
• You have in-house or contractor SAP expertise (third-party vendors are not SAP hand-holders for inexperienced teams).
• You want release autonomy (to stay on ECC6 longer, or delay S/4HANA migration).

Risks: SAP will position third-party maintenance as risky and lower-quality. This is marketing; it's not factually accurate for large, stable vendor providers. However, do vet your third-party provider's SLA terms, engineer qualifications, and case studies from comparable enterprise deployments.

For a £10M licence base at 22% (Enterprise Support = £2.2M/year), switching to third-party maintenance at 10% saves £1.2M annually. The trade-off is reduced hand-holding; the savings are real and substantial.

A hybrid model combines SAP support (for core systems requiring SAP SLAs) with third-party support (for non-critical or stable systems). This is often the most pragmatic path for enterprises with mixed system portfolios.

Example hybrid structure:

• Production ERP: SAP PCNS at 17% (critical system, justifies SAP SLAs and emergency support).
• Analytics (BI/DW): Third-party support at 10% (stable, mature, predictable workload).
• Learning/Development systems: Non-supported (internal IT manages, no external vendor support).

This reduces your blended support cost from 22% to 12–14% while retaining SAP support for the systems that genuinely need it. The operational complexity is minimal if you choose providers carefully and establish clear escalation paths.