SAP Business Technology Platform is the consumption-based platform layer that runs alongside S/4HANA: integration, extensibility, analytics, data, AI and database services. The CPEA commercial model, the consumption metering and the renewal-time reconciliation read against the underlying S/4HANA position.
SAP Business Technology Platform is the consumption-based platform layer that runs alongside S/4HANA. The platform is the BTP overlay on the RISE bundle (the embedded BTP service consumption inside the RISE contract) and the standalone BTP overlay on the on-prem track (the BTP services consumed directly against the customer's BTP commitment, outside any RISE bundle). The platform groups six service categories: integration (the Integration Suite, the Event Mesh), extensibility (SAP Build, the Cloud Application Programming Model, ABAP Cloud), analytics (SAP Analytics Cloud), data (SAP Datasphere, the data products framework), AI (the generative-AI hub, Joule, document-information-extraction services) and database (SAP HANA Cloud).
The overlay therefore runs as a parallel commercial line to the underlying S/4HANA position. The wider SAP clean core spoke reads the BTP-side extensibility framework; the wider RISE bundle anatomy spoke reads the RISE-embedded BTP allocation.
The CPEA commercial model is the Cloud Platform Enterprise Agreement: an annual prepaid credit commitment redeemable against published service rate cards. The customer commits to an annual BTP spend amount (the CPEA commitment value); the commitment funds a pool of credits; the credits consume against the published rate card for each BTP service used during the contract year.
The structure is similar to the Microsoft MACC (Microsoft Azure Consumption Commitment), the AWS EDP (Enterprise Discount Program), the Google Cloud CCA (Committed Cloud Agreement) and the OCI Universal Credits: a prepaid commitment against a flexible-consumption portfolio. The CPEA carries published volume-tier discounting against the rate card and an end-of-year expiry rule on unused credits. The wider CPEA credit design spoke reads the credit-design mechanics.
The consumption metering is service-specific. Each BTP service publishes a metering model: the Integration Suite meters per-message and per-connection; SAP Build meters per-runtime-instance and per-user; the AI services meter per-document, per-token (for generative AI) and per-API-call; HANA Cloud meters per-compute-unit and per-storage-unit; Datasphere meters per-capacity-unit; Analytics Cloud meters per-named-user and per-concurrent-session.
The metering reads against the published service rate card. The rate card is updated periodically (the buyer should rehearse the rate-card revision schedule against the contracted-rate floor in the CPEA contract). The wider SAP RISE renewal spoke reads the RISE-embedded BTP credit consumption; the wider CPEA credit design spoke reads the standalone CPEA mechanics.
The renewal-time reconciliation reads the actual consumption against the contracted commitment. The reconciliation closes against three positions. The first is the over-consumed-services position: a service consumed beyond the credit allocation closed against the rate-card price for the over-consumed volume (typically billed mid-year against an excess-consumption invoice or rolled into the next-year renewal commitment). The second is the under-consumed-services position: the credits allocated to the service that were not consumed; the unused credit balance expires at year-end under the standard CPEA expiry rule. The third is the rate-card revision position: the rate-card revisions inside the contract year and the buyer-side floor against the contracted rate.
The position-of-record at renewal is the per-service consumption catalogue, the commitment-versus-consumption reconciliation, the BTP-side renewal commitment and the rate-card position at renewal. The wider SAP RISE renewal spoke reads the RISE-embedded BTP line.
Three published BTP-side renewal levers read against the renewal-time reconciliation. The first is the commitment-rightsizing lever: the renewal commitment is set against the consumption trajectory (not against the previous-year commitment), with discount-tier mechanics applied at the published tier breakpoints. The second is the rate-card floor lever: the buyer negotiates a contracted-rate floor against the published rate card at renewal (the contracted rate cannot increase above the floor during the renewal term). The third is the service-mix lever: the renewal CPEA is structured against the expected service-mix (heavy Integration Suite consumption versus heavy AI service consumption) with service-mix-specific discount provisions.
The wider SAP RISE renewal spoke reads the RISE-embedded renewal architecture; the wider SAP BATNA spoke reads the BATNA position on the BTP-side renewal.
At the renewal moment, the buyer is in one of four published positions on the BTP question. The first is the on-track position: the consumption ran at or near the commitment; the renewal is sized against the run-rate. The second is the under-consumed position: the consumption ran below commitment; the renewal is right-sized down. The third is the over-consumed position: the consumption ran above commitment; the renewal is sized against the actual consumption with discount-tier mechanics applied. The fourth is the mid-cycle adjustment position: the renewal is scheduled for a mid-cycle adjustment to bring the commitment back in line with the consumption trajectory.
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
A senior Admodum SAP advisor will read your per-service consumption catalogue, your commitment-versus-consumption reconciliation, your rate-card floor and your renewal-time commitment rightsizing on a private call. Active renewal moments route to the Renewal Programme.