SAP BTP Extension Scenarios: Enterprise Buying Guide

SAP BTP Extension Scenarios: Enterprise Buying Guide

SAP BTP extension scenarios look straightforward on paper. SAP's account team will present you with a clean architecture diagram showing how Clean Core extensions, Side-by-Side scenarios, and the BTP platform work together to extend your S/4HANA without touching the core. What they won't show you is the total cost of ownership calculation, the CPEA consumption model, the service-level commitments, or the exit clauses that make switching expensive.

This enterprise buying guide cuts through SAP's marketing to give you the framework for evaluating, negotiating, and buying SAP BTP extension scenarios on your terms. We'll show you what each extension scenario type actually costs, when CPEA makes sense and when it's a trap, and how to negotiate contract terms that protect you against SAP's lock-in tactics.

Understanding What You're Actually Buying

Before you engage with SAP on licensing, you need to understand what BTP extension scenarios are and what they demand from the platform.

The Three Extension Scenario Types

SAP defines three primary extension scenarios. Each has different BTP consumption profiles and cost implications:

• In-App Extensions (Cloud): Custom code deployed directly inside SAP's SaaS environment using SAP's extension framework. These are low-footprint, low-cost extensions that consume minimal BTP resources. Perfect for configuration-heavy customizations. Licensing is typically consumption-based with lower CPEA floors.
• Side-by-Side Extensions: Custom applications running on BTP alongside your core SAP system, integrated via APIs and events. These consume more BTP resources—runtimes, databases, integration services—because they're independent applications. This is where CPEA consumption climbs rapidly.
• Clean Core Extensions (SAP Recommended): The SAP-approved model: minimal core system changes, maximum BTP dependency. Clean Core is the architecture SAP sells with every S/4HANA deal. It locks you into BTP for extensibility and drives long-term consumption growth.

Here's what SAP doesn't emphasize: each extension scenario type demands specific BTP services. A Side-by-Side extension might require Cloud Foundry runtimes, a PostgreSQL database, API Management, Event Mesh, Integration Suite, and Launchpad services—all metered separately and bundled into your CPEA consumption.

Services Consumed Per Scenario

Your extension architecture determines which BTP services you'll pay for. Enterprise deployments typically consume:

• Runtimes: Cloud Foundry, Kyma, ABAP—each priced separately per instance hour.
• Data Services: PostgreSQL, MongoDB, Redis (per GB provisioned, not used).
• Integration Services: API Management, Integration Suite, Event Mesh—critical for connecting extensions to core systems.
• Security & Identity: Identity Authentication, Identity Provisioning—required for SSO and user management.
• Observability: Cloud Logging, Cloud Trace, Application Performance Monitoring—overhead you'll underestimate in your initial architecture.

The trap: SAP's RFP templates and consumption projections typically assume greenfield deployments with clean architecture. Real enterprise extensions add monitoring, backup, disaster recovery, and integration overhead that multiplies consumption 2-3x over initial projections.

CPEA vs Subscription Service Plans: The Buying Decision

This is the critical decision that determines your cost trajectory over 3-5 years. SAP will push you toward CPEA. Here's why—and when they might be right.

CPEA: How SAP Locks You In

Cloud Platform Enterprise Agreement (CPEA) pricing ties your cost to consumption. You pay per credit—a bundled unit covering runtimes, storage, API calls, and services. SAP publishes a minimum CPEA floor (typically 6,000-10,000 credits/month for enterprise extensions) and you commit to that floor regardless of actual consumption.

Why SAP prefers CPEA for you: Over-consumption is built into the model. That monitoring you add? That's extra credits. The backup automation? Extra credits. A production incident requiring temporary scale-up? Your annual consumption jumps.

Real example: A global manufacturing enterprise signed a 3-year CPEA deal with an 8,000 credit/month floor. Year 2, they added a Side-by-Side analytics extension requiring additional Event Mesh subscriptions. Their consumption increased 34% year-over-year. They were locked into the floor—overpaying for lower-consumption months and still underprovisioned in high-demand periods.

Subscription Plans: Cost Certainty

Subscription-based service plans flip the model. You buy specific services—Cloud Foundry capacity, Integration Suite seats, data storage—at fixed monthly rates. You know the cost upfront. Scaling is explicit and negotiated in advance.

When subscriptions make sense: Your extension architecture is stable and well-defined. You have predictable API consumption. Your team is mature enough to right-size resources without overprovisioning.

The catch: Subscriptions require upfront volume commitment. SAP will sell you higher minimums because there's no over-consumption revenue. You also pay for capacity you don't use if you're conservative with sizing.

How to Model Consumption Before Committing

SAP's standard consumption projections are optimistic. Follow this framework instead:

1. Enumerate all services. Don't just list application runtimes. Include every integration point, every data service, every monitoring tool, every identity provider. One missed service can add 15-20% to your actual consumption.
2. Right-size with production data. Use your actual S/4HANA load profile. Simulate integration patterns. Run pilot extensions and measure real consumption over 30 days, not 30 minutes.
3. Build in overhead. Add 30-40% for monitoring, logging, disaster recovery, and compliance requirements. Enterprise systems have tail behavior—rare events consume disproportionate resources.
4. Model peak vs baseline. Calculate minimum monthly consumption (baseline) and peak consumption (month-end reporting, tax season, year-end close). CPEA floors should align with baseline; peaks should stay within negotiated overages.
5. Project 3-year growth. How many extensions are you likely to add? Will existing extensions scale to handle more users? A 10% annual growth assumption is typical; validate that your CPEA floor can accommodate it.

The Enterprise Evaluation Framework for BTP Extension Scenarios

Before you sign, run your BTP extension project through this 6-point evaluation. Any weakness here will cost you millions over the contract lifetime.

1. Consumption Modelling (What This Actually Costs)

Demand a detailed cost breakdown from SAP. Challenge every assumption. Ask for consumption profiles from comparable deployments (anonymized). Run a proof-of-concept extension on BTP and measure real consumption. SAP's projections are typically 40-60% low.

2. Runtime Selection (Cloud Foundry vs Kyma vs ABAP)

Each runtime has different cost profiles. Cloud Foundry is consumption-per-instance-hour. Kyma is container-based, with Kubernetes overhead. ABAP is premium pricing. Your architecture should specify which runtime(s) you'll use and justify the selection against cost.

3. Integration Footprint (How Many Connection Points?)

Extensions integrate back to core systems via APIs, events, or synchronous calls. Each integration point consumes API Management, Event Mesh, or Integration Suite capacity. Map your integration architecture upfront. A complex extension might integrate 10+ systems—that's significant CPEA consumption.

4. Exit Provisions (How Much Will Switching Cost?)

This is where SAP's lock-in happens. Default contracts have no exit clause—you're committed to the full 3-5 year term at the CPEA floor, even if you migrate to a competing platform. Negotiate explicit early termination rights with proportional refunds.

5. Support Model (Who Supports Your Extensions?)

SAP offers tiered support (Standard, Premium, Mission Critical). Your extension support model affects both cost and SLA. Production extensions should run on Premium+ support—that's additional 20-30% to your BTP costs.

6. RISE Interaction (Are You Bundling With Managed S/4HANA?)

If you're on RISE with SAP, your S/4HANA license and BTP extensions are bundled. This changes your leverage in negotiations. You can't negotiate CPEA independently—SAP ties it to S/4HANA consumption. Understand these dependencies before you commit.

What SAP's Account Team Won't Tell You

SAP's incentive structure rewards closing large deals fast. You're incentivized to understand what they're not disclosing.

CPEA Over-Consumption Risk is Real and Intentional

CPEA consumption grows 15-25% year-over-year on average. SAP knows this. The platform is designed for over-consumption—every new feature, every new integration point, every operational best practice (logging, monitoring, backup) consumes more credits. Your CPEA floor today becomes your baseline next year.

The "Free BTP Credits" Illusion in RISE

RISE includes "free" platform credits (typically 5,000-15,000 credits/year). Sounds generous. In practice, these credits evaporate on basic platform operations and security infrastructure. They're not meaningfully available for extension workloads. SAP counts them as value-add; they're consumed before your extensions even deploy.

Service Deprecation Risk

SAP has deprecated BTP services before. Cloud Platform Integration, parts of API Management, legacy runtime environments have all been sunset. When SAP deprecates a service, it doesn't refund consumption or extend timelines—you migrate or you lose access. Your contract should include service continuity commitments.

Vendor Lock-in Mechanics

BTP extensions written in SAP's proprietary languages (CAP, ABAP) are expensive to migrate to competing platforms. Integration patterns using Event Mesh or Integration Suite create tight coupling to SAP infrastructure. After 2-3 years of BTP deployment, the switching cost is 50%+ of your infrastructure budget. SAP knows this and prices accordingly in year 3-5 contract renewals.

Key Contract Terms Every Enterprise Buyer Must Negotiate

These contract modifications will save you money and protect you against SAP's standard lock-in tactics.

Minimum CPEA Floor Reductions

What to negotiate: The right to reduce your CPEA floor annually, with notice. SAP's default: you're locked into the floor for the full contract term. Better deal: annual floor adjustment windows (e.g., January 1st each year) with 60-day notice. If your extensions scale down, your floor should scale with them.

Consumption Carryover (Credits Don't Disappear)

What to negotiate: Unused CPEA credits roll over to the next month, up to a cap (e.g., 2 months of average consumption). SAP's default: credits expire monthly. This forces over-consumption to avoid waste. Carryover provisions eliminate that trap.

Service Plan Downgrades

What to negotiate: The right to downgrade from Premium Support to Standard Support without penalty, with 90-day notice. You shouldn't be locked into premium support pricing if your extension matures and doesn't require 24x7 coverage.

Exit Clauses Without Penalty

What to negotiate: Early termination right (e.g., after year 2) with no penalty if SAP changes pricing, discontinues a critical service, or increases CPEA floor by more than 20% year-over-year. This protects you against SAP's vendor lock-in strategy.

Explicit Service Continuity Commitment

What to negotiate: SAP commits to not deprecating services used in your extension architecture without 24-month notice and migration support. This prevents surprise service shutdowns that force expensive re-architecture.

How to Use Independent Advisory in Your BTP Extension Buying Process

Enterprise buyers who engage independent SAP licensing advisors before signing typically save 25-40% over the contract lifetime. Here's why.

Independent Advisors Uncover Hidden Costs

Third-party experts have seen hundreds of BTP extension deployments. They spot architecture patterns that drive consumption—redundancy, monitoring overhead, integration complexity. SAP doesn't volunteer this. Independent advisors do.

Consumption Modelling Gets Right-Sized

Instead of accepting SAP's projections, independent advisors model your actual extension architecture and validate consumption assumptions against real deployments. This prevents the 40-60% underestimation that leads to massive overages in year 2.

Negotiation Leverage

SAP's account teams are trained to recognize unsophisticated buyers. When you bring independent counsel to negotiations, SAP knows you understand the trap and will push back. This shifts leverage in your favor—SAP cuts better deals to close vs. losing you to a competitor.

We've negotiated over $3.2M in savings for a global insurance enterprise that was being positioned into a CPEA trap. The original SAP RFP projected 12,000 credits/month for their extension portfolio. We identified over-consumption risk in their integration architecture, right-sized their footprint to 7,200 credits/month baseline, negotiated consumption carryover, and locked in floor reductions for years 3-5. Three-year savings: $1.8M. Five-year savings: $3.2M. All from understanding what they were actually buying.

We offer SAP license optimisation services and RISE with SAP advisory specifically for enterprises navigating these decisions. We also provide SAP contract negotiation service when you're in the final stages of a deal.