Introduction: Why Most Enterprises Make This Decision Badly
Enterprise Support feels safe. You have 24x7 access to SAP Response Centers, Named User tiers, MaxAttention engineers on speed dial. But for most large enterprises running stable S/4HANA landscapes or mature ECC systems, you're paying 40-60% of your license value annually to SAP for support you don't fully consume.
The inverse problem exists too: teams switch to PCNS without understanding their patch management obligations, or they negotiate away critical protections that surface two years into the contract.
The solution is a structured, phase-based evaluation process that forces you to map what you actually use, benchmark realistic alternatives, and negotiate from a position of informed leverage. This checklist and action plan gives you that framework.
Phase 1: Current State Assessment Checklist
Before you talk to SAP about tiers or pricing, you need to baseline your current consumption and cost. Most enterprises skip this. Don't. Use this checklist to document your baseline.
Map every ECC, S/4HANA, BW, Ariba, SuccessFactors, Analytics Cloud instance. Note which systems are targeted for migration, decommission, or major upgrade within 3-5 years. This determines support tier risk.
Pull monthly VDM reports for the last 12 months. Calculate average concurrent usage, peak usage, and trend direction. If you're paying Named User support but running 60% utilization, you're overpaying.
Extract ticket data from your SAP support portal: count P1/P2/P3/P4 tickets year-to-date, average resolution time, percentage resolved by third-party maintenance vs. SAP. If you're averaging 2-3 P1s per year, you're a candidate for PCNS.
If migration is 18-24 months away, Enterprise Support SLA expectations may shift. SAP will use migration planning to push you toward long-term Enterprise renewal. Lock in the decision before migration kicks off.
Pull actual contract language on response times, patch obligations, escalation procedures, and tier flexibility. Many contracts contain hidden conditions that lock you into Enterprise Support or restrict PCNS transitions.
Divide annual support spend by total Named User/Developer license value. Typical Enterprise Support: 22-28% of license value. PCNS: 9-14%. If you're above 25%, you're paying premium pricing.
Document how long it takes to apply patches in test, UAT, and production. PCNS requires faster patch windows (typically 30-60 days for critical patches). If your current cycle is 6+ months, Enterprise Support may be necessary.
Know who you're negotiating with at SAP. Track contract renewal dates—you have maximum leverage 90 days before renewal. Identify internal stakeholders (CTO, CFO, Basis team) who must align on any decision.
Phase 2: PCNS Eligibility Assessment
Not every enterprise is a fit for PCNS. This phase clarifies whether your landscape, maturity, and operational readiness support a move away from Enterprise Support. If you fail multiple items here, reconsider.
Some Enterprise Support contracts include multi-year commitments with early termination fees. Verify you can change tiers at renewal, or identify termination costs. This is a deal-breaker question.
PCNS works best on stable, mature systems. If your ECC system experiences unplanned outages more than 1-2x per year, or if your S/4HANA migration is less than 12 months old, Enterprise Support reduces operational risk.
PCNS means your team owns patch scheduling, testing, and rollback. If your Basis team is understaffed or stretched thin, Enterprise Support's extended patch windows provide necessary buffer.
PCNS works best with Rimini Street, Kontis, or Accenture support in parallel. Map existing relationships, pricing, and SLAs. Gapless support transitions require this alignment before you downgrade from Enterprise.
Enterprise Support provides 4-hour response for critical issues. PCNS typically 8-24 hours. If your RTO is measured in minutes, not hours, Enterprise Support is justified.
If ECC or older S/4HANA versions are nearing end-of-support, Enterprise Support pricing reflects that urgency. PCNS may not be available in final support years. Map out roadmap and PCNS availability windows.
Phase 3: Negotiation Preparation Checklist
You now know your baseline, your eligibility, and your constraints. This phase gets you ready to negotiate. Never walk into a conversation with SAP without this homework done.
Get quotes from Rimini Street, Kontis, Accenture, and other third-party vendors for your specific systems. Get SAP PCNS pricing in writing. You need 3-5 competitive data points to credibly argue your case to SAP.
Pull data: if you've used Named User support 3 times in 12 months but paid for premium access, document that. If MaxAttention incidents are below contractual thresholds, that's leverage. Quantify the waste.
Know your company's cost reduction mandate. If IT costs are targeted for 15% reduction, that's your anchor. SAP knows budget pressure exists; prepare talking points that align support decisions with business goals.
Package your Phase 1 baseline into a 1-2 page deck: VDM trends, ticket distribution, system roadmap, cost-per-system. This shifts conversation from SAP's standard playbook to your actual operational reality.
Have legal review your contract before you negotiate. Identify clauses that protect you (escape hatches, tier flexibility, price cap language). Know your walk-away point.
Reach out 120 days before renewal, not 30. Propose a structured evaluation: "We want to assess support tiers as part of our overall cost optimization." This signals seriousness and gives both sides room to prepare.
Phase 4: Transition Risk and Service Continuity Checklist
You've decided to move forward with PCNS or negotiated a hybrid approach. Now you must plan the operational transition to eliminate support gaps and ensure no critical services fall through the cracks.
List every service you use: incident response, patch management, architectural guidance, performance tuning, upgrade support. Map each service to a PCNS or third-party replacement. Don't assume PCNS covers everything.
Create a runbook: patch release schedule, testing requirements, approval workflows, rollback criteria. PCNS removes SAP accountability for patch delays; your team now owns this. Automate where possible.
Identify where you'll get architectural advice, performance optimization, or specialized support (indirect access, analytics, security). Lock in relationships and pricing before Enterprise Support ends.
PCNS SLAs differ from Enterprise. Update on-call procedures, escalation trees, and incident classification rules to match new support timelines. Train your support team on PCNS response expectations.
Business units need to understand support changes. Explain that PCNS doesn't mean "less support"—it means faster internal response and different escalation procedures. Manage expectations explicitly.
Plan a 30-60 day overlap where Enterprise Support and PCNS/third-party support run in parallel. Use this window to verify third-party support is responsive and your team is confident in new procedures.
Calculate total year-one cost (Enterprise overlap + PCNS setup + third-party support). Compare to baseline Enterprise cost. Most enterprises break even in 12-18 months and save 30-40% annually long-term.
Phase 5: Post-Transition Verification Checklist
30 days after you've transitioned from Enterprise Support, run this checklist. You're looking for early warning signs that support quality or operational readiness is degrading.
Submit a test ticket to your new PCNS or third-party vendor. Measure response time and quality. If they're slow or evasive, escalate immediately. You have a window to reconsider before full transition.
Run a non-critical patch cycle under the new process. Measure testing time, approval cycle, and deployment window. Identify bottlenecks and update the runbook before a critical patch drops.
Track P1/P2 incidents for 90 days post-transition. Look for patterns: Did system stability drop? Are specific areas more incident-prone? If incidents increased >20%, revisit support tier decision.
Run 2-3 support interactions where your team leads diagnosis and third-party vendor follows. This confirms your team has baseline knowledge to own problems independently.
Compare your Phase 3 cost projection to actual invoices. If costs are tracking higher than expected, investigate overage fees or hidden charges. Make sure you're realizing the financial benefit you negotiated.
Set calendar reminders to review support performance twice in the first year. PCNS works better after you've run 2-3 patch cycles and your team has full muscle memory. Make refinements as you learn.
When to Involve Independent Advisors
SAP controls the information asymmetry in support negotiations. Your account manager owns the relationship, the pricing levers, and the standard playbook. Independent advisors rebalance that dynamic.
Timing: Engage an independent advisor 90-120 days before contract renewal, not during the heat of negotiation. Advisors need time to audit your landscape, model alternatives, and build leverage quietly.
What advisors bring:
- Benchmarking data from 50+ enterprise support transitions—they know what realistic pricing looks like for your landscape
- Buyer-side contract language that protects you: escape hatches, price caps, performance commitments
- Credibility with SAP procurement. SAP knows advisors have negotiated 100+ contracts; your internal arguments carry less weight
- Emotional buffer between your team and SAP. Advisors can say "no" and walk away; internal teams often capitulate under pressure
- 20-30% cost reduction leverage. Most enterprises negotiate 5-8% discounts; advisors consistently achieve 20-30% through structured benchmarking and alternative scenarios
Why buyer-side independence matters: An advisor paid by SAP (reseller, consulting partner) has incentive to recommend Enterprise Support to justify higher service fees. A buyer-side advisor's only customer is you. That alignment matters.
SAP support cost reduction advisors specialize in this exact scenario. Most charge fixed project fees, not percentage of savings, so there's no misalignment.
FAQ: Enterprise Support vs PCNS Decisions
Rarely without penalty. Most SAP support contracts are annual with multi-year commitments. You can request a tier change at renewal, but mid-contract changes usually trigger early termination fees equal to the remaining contract value. Verify your contract language—some include explicit tier-change clauses that allow downgrades without penalty. This is a critical negotiation point: lock in tier flexibility before renewal.
It can, but with added risk. New S/4HANA systems are still stabilizing; you're more likely to hit unexpected issues. Most advisors recommend Enterprise Support through month 18-24, then transition to PCNS once the system is production-proven. Exception: If you have experienced SAP implementation partners or Rimini Street support already embedded, PCNS is viable earlier. Tier your approach: Enterprise for first 12 months, then reassess.
Enterprise Support typically runs 22-28% of license value annually. PCNS runs 9-14%. Third-party maintenance (Rimini Street, Kontis) adds another 7-12%. So a fully-laden PCNS + third-party support scenario costs 16-26% of license value—a 25-50% reduction from Enterprise. Savings are smaller if you need multiple third-party vendors covering different system areas, but rarely exceed Enterprise costs. Model your specific landscape; don't assume average savings apply to you.
SAP typically guarantees patch availability for PCNS customers, but response times and escalation procedures change. SAP's "extended support" model allows PCNS for systems in mid-to-late support lifecycle, but you must confirm patch availability in writing as part of your transition. Some legacy systems nearing end-of-support may restrict PCNS entirely. Verify patch roadmap with SAP before you sign a PCNS contract.
Ready to Evaluate Your Support Tier Decision?
Walk through this five-phase checklist with an independent advisor. Most enterprises save 30-40% annually by optimizing support tiers—and keeping your systems fully protected. Get a benchmark assessment and identify your tier optimization window.
Book a Free Consultation