SAP BTP Licensing Strategy. Three commercial vehicles and a RISE entitlement most customers fail to audit.

SAP Business Technology Platform (BTP) is the umbrella for SAP's PaaS and integration services: Integration Suite, Build (low code), Datasphere (data warehouse), HANA Cloud, Analytics Cloud, AI Foundation, and around forty other SAP services. BTP has three distinct commercial vehicles. The Pay As You Go (PAYG) model is consumption based with no upfront commit, billed monthly against actual service usage. The Cloud Platform Enterprise Agreement (CPEA) is an annual prepaid commit at a discount (typically twenty to forty percent off PAYG depending on commit size). The BTP Enterprise Agreement (BTPEA) is the newer multi year commit replacing CPEA for larger customers, with deeper discounts and price protection. The metering unit is the Capacity Unit (CU), with each service consuming CUs at a different rate. The most common pitfall is the BTP tax baked into RISE with SAP: RISE bundles include a CPEA allocation that frequently gets forgotten and used inefficiently, costing customers fifteen to twenty five percent of total RISE value. This paper sets out actual CU consumption rates by service, the PAYG versus CPEA versus BTPEA decision logic, the integration with Integration Suite and Build, and the eleven move buyer side playbook. Read the related SAP services practice, the SAP knowledge hub, the SAP HANA Cloud negotiation, and the benchmarking practice.

What you will learn

• The three BTP commercial vehicles, mapped. PAYG (consumption, no commit), CPEA (annual prepaid commit), BTPEA (multi year commit with deeper discount and price protection).
• Capacity Unit consumption by service. Integration Suite, Build, Datasphere, HANA Cloud, Analytics Cloud, AI Foundation, Workflow Management, and Event Mesh all consume CUs at different rates. The mix determines the right commit size.
• The RISE with SAP BTP tax. Every RISE contract includes a CPEA allocation. Customers regularly fail to consume it, fail to monitor consumption, or over consume and pay overage at PAYG rates. This is the single biggest BTP saving lever for RISE customers.
• Integration Suite versus standalone integration tools. Where Integration Suite beats Mulesoft, Boomi, and Workato on the SAP estate, and where it does not.
• SAP Build low code economics. The Build Apps, Build Process Automation, and Build Code Tools metric model, and how it compares to Microsoft Power Platform on SAP integrated workflows.
• The cancellation and downsize mechanics. BTPEA is materially harder to renegotiate downward than CPEA. The trade off is the deeper discount versus the renewal flexibility.
• The SAP Datasphere overlap. Datasphere consumes BTP CUs but competes commercially against Snowflake and Databricks. When SAP is the right choice and when it is not.
• The eleven move buyer side playbook. Sequenced from RISE entitlement audit through CU consumption modeling and BTPEA versus CPEA decision, with dollar values against each move.

Table of contents

Who this is for

CIOs, Chief Data Officers, VPs of IT Procurement, SAP Center of Excellence leaders, Integration Center of Excellence leaders, and procurement leaders running SAP BTP at scale. Particularly useful for RISE with SAP customers who have BTP allocations they have not audited, customers approaching a CPEA or BTPEA renewal, and customers evaluating Integration Suite against MuleSoft or Boomi as the integration platform.