Editorial photograph of an SAP AI and data licensing review with consumption metrics on the boardroom wall
Article · SAP · AI and Data Licensing

SAP AI and Data. The new commercial reality.

SAP reset the AI and data licensing model in July 2025. AI Units, Joule consumption, and Datasphere capacity now bill outside the classic S/4HANA user metric. Six moves cap the buyer side exposure.

Read the Article SAP Hub
3Separate consumption pools
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

What this article delivers

  • Three separate consumption pools. AI Units, Joule access, Datasphere capacity.
  • AI Units price at roughly 0.40 USD per unit at list. Volume tier discounts move it down.
  • Joule access bundles inside Premium Plus or sells as add on. Per user per month.
  • Datasphere capacity bills per block. Compute, storage, and data movement charged separately.
  • July 2025 reset separated the pools. Each pool now negotiates as its own SKU.
  • Median overpay across reviews is 22 percent. Captured at the pool boundary.
  • Top tier discount band reaches 40 percent. At committed multi year volume.

SAP reset the AI and data licensing model on July 1, 2025. AI Units, Joule access, and Datasphere consumption now bill outside the classic S/4HANA Full Use Equivalent metric. Six buyer side moves cap the exposure across the three pools.

The reset matters because the new pools sit outside the historic SAP user count. The customer that does not separate the pools at the negotiation table pays the SAP default opening across all three lines.

What changed in July 2025

The July 2025 reset moved AI and data consumption out of the classic SAP user metric and into separate consumption pools. The change matters at the negotiation table because each pool now requires its own line item, its own commit, and its own discount band.

Before July 2025

  • AI and data bundled with S/4HANA users. No separate consumption metric.
  • Joule access inside the S/4HANA Premium Plus bundle. No standalone subscription.
  • Datasphere inside the BTP services subscription. Capacity allocated by Tcode bundle.
  • No standalone discount band on AI consumption. Bundled into the SAP renewal discount.

After July 2025

  • AI Units as a separate consumption metric. Priced per unit consumed.
  • Joule access as a per user per month subscription. Inside or outside the Premium Plus bundle.
  • Datasphere capacity blocks. Compute, storage, and data movement billed separately.
  • Standalone discount bands per pool. Volume commitment per pool drives the rate.

How AI Units price

SAP AI Units are the consumption metric for embedded AI capabilities across the SAP application estate. The unit measures consumption of large language model calls, document processing, embedding generation, and inference operations. The price falls as the committed volume rises.

AI Units commitment bands

Annual commit tierList rate per AI UnitNegotiated band
Pay as you go0.40 USDNo discount
100K Units per year0.36 USD4 to 8 percent
500K Units per year0.32 USD10 to 16 percent
2M Units per year0.28 USD18 to 26 percent
10M plus Units per year0.24 USD26 to 40 percent

What consumes AI Units

  • Joule conversational AI calls. Each Joule prompt and response cycle consumes a defined unit count.
  • Document AI processing. Invoice, contract, and PO document recognition.
  • Embedding generation for search. Semantic search across SAP data.
  • Predictive forecasting models. S/4HANA cash flow, demand, and risk forecasts.
  • Generative content workflows. Auto generated content inside HCM, CX, and procurement modules.

Joule access cost

Joule is the SAP conversational AI assistant. Joule access bills separately from the AI Units that the Joule conversations consume. The customer pays both for the access seat and for the units consumed.

Joule access patterns

  • Inside S/4HANA Cloud Premium Plus. Joule access bundled in. AI Units consumption still meters.
  • Inside SuccessFactors HCM Premium. Joule for HR bundled. AI Units consumption still meters.
  • Standalone Joule subscription. 12 to 18 USD per user per month list, depending on persona.
  • Joule Studio for builder personas. 25 to 35 USD per builder per month for the development environment.
SAP Datasphere consumption dashboard showing AI Units and Joule usage trends
Three pools. Three meters. The defense is to commit per pool, not as a single bundle.

Datasphere capacity

SAP Datasphere is the cloud data warehouse and data fabric service. The Datasphere capacity bills on three separate blocks. Compute, storage, and data movement each meter independently against the customer commitment.

The three Datasphere blocks

  • Compute Units. The processing capacity allocated to queries, transformations, and replications. Sized in defined CU tiers.
  • Storage capacity. The persisted data volume in TB. List price approximately 30 USD per TB per month at list.
  • Data movement. The volume of data ingested or extracted across the service boundary. Per TB metered.

Six buyer side moves

The buyer side captures the most value when the three pools negotiate separately and the commitment lands at the right volume tier for each pool. Six moves recur across the SAP AI advisory engagements.

Move 1. Forecast consumption per pool

The forecast is the foundation of the commit. The customer that commits on a guess overpays. The defense is to model the AI Units consumption across the top five SAP use cases, the Joule access seats per persona, and the Datasphere capacity per workload.

Move 2. Separate the pool negotiations

The seller side prefers to bundle the three pools into a single commitment. The buyer side captures more by negotiating each pool against its own discount band. The negotiation calendar runs the three pools in parallel rather than as a stacked bundle.

Move 3. Commit at the right tier

The discount band steps occur at defined volume thresholds. The customer that commits just below a threshold misses the next band. The defense is to model the consumption at threshold ratios and to commit at the next band when the forecast supports it.

Move 4. Protect the carry over

The AI Units commitment expires at the end of each subscription year. The customer that under consumes loses the unused units. The defense is to negotiate a 30 percent carry over clause that protects up to 30 percent of the unused commitment.

Move 5. Cap the renewal uplift

The SAP default carries a 7 to 9 percent annual renewal uplift on subscription services. The buyer side captures a 0 to 3 percent cap on the AI and data pools at signing. The cap protects the unit price across the commitment term.

Move 6. Time the negotiation around the SAP fiscal calendar

SAP runs a December 31 calendar year fiscal end. The seller side carries fiscal year quotas tied to that date. The Q4 timing for SAP runs October through December rather than April through June.

Pool comparison

PoolMetricList anchorTop tier band
AI UnitsPer unit consumed0.40 USD26 to 40 percent
Joule accessPer user per month12 to 18 USD14 to 24 percent
Datasphere computePer Compute Unit per monthTier specific20 to 35 percent
Datasphere storagePer TB per month30 USD15 to 25 percent
Datasphere movementPer TB ingested or extractedTier specific10 to 18 percent

What to do next

The SAP AI and data checklist runs the three pools in parallel.

  1. Pull every SAP AI, Joule, and Datasphere consumption record. 12 months of history.
  2. Forecast the consumption per pool. Top five use cases per pool across 24 months.
  3. Score the discount band thresholds. Volume tier at the forecast plus 20 percent.
  4. Separate the negotiation lines. Three commitments, three discount bands.
  5. Negotiate the carry over and the cap. 30 percent carry over and 0 to 3 percent uplift.
  6. Time the negotiation around the SAP fiscal calendar. October through December for maximum leverage.
  7. Document the audit defense file. Pool boundaries, consumption mapping, and entitlement records.
  8. Run the negotiation through Vendor Shield. Independent buyer side review at each pool decision.

Frequently asked questions

What changed in the SAP AI and data commercial model on July 1, 2025?

SAP separated AI Units, Joule access, and Datasphere consumption from the classic S/4HANA user metric. The three pools now bill against their own commitment lines with their own discount bands. The change moved the AI and data conversation out of the renewal bundle and into a per pool negotiation.

The customer that does not separate the pools at the negotiation table pays the SAP default opening across all three lines. The buyer side captures 18 to 40 percent on the AI Units pool alone when the commitment lands at the right volume tier.

How does SAP price AI Units?

SAP AI Units list at approximately 0.40 USD per unit at pay as you go. The volume commitment bands move the rate down to 0.24 USD at the 10M plus units per year tier. The discount band corresponds to 26 to 40 percent below the pay as you go list at that tier.

The unit is consumed by Joule conversations, document AI processing, embedding generation, predictive forecasting, and generative content workflows. Each operation has a defined unit count that varies by complexity and token volume.

Does Joule access include the AI Units it consumes?

No. Joule access bills as a per user per month subscription. The AI Units consumed by Joule prompts meter against a separate commitment. The customer who buys Joule access without modeling the unit consumption faces an unexpected meter bill.

The defense is to forecast the Joule consumption per user, model the unit count per Joule interaction, and commit on the AI Units pool to cover the forecast. The pool commitment protects the unit price across the term.

How does Datasphere bill capacity?

SAP Datasphere bills three separate blocks. Compute Units for query and transformation processing, storage capacity per TB per month, and data movement per TB ingested or extracted. Each block has its own commitment line and its own discount band.

The customer that commits on storage alone and underestimates the compute requirement faces a meter bill on compute. The defense is to model the three blocks together and to commit at the right ratio across the three lines.

What is the typical overpay on a poorly negotiated SAP AI commit?

Across 40 SAP AI advisory engagements, the median overpay against the optimized commit was 22 percent. The range was 12 percent at the low end and 38 percent at the high end. The overpay typically lands in the AI Units pool where the volume tier discount band is widest.

The two recurring failure modes are bundling the three pools into a single commitment and committing just below a volume tier threshold. The defense is to negotiate the three pools separately and to commit at the threshold ratios.

Can the customer carry over unused AI Units to the next year?

The SAP default does not include a carry over clause on AI Units. The buyer side captures a 30 percent carry over at signing on negotiated commits at the 500K units per year tier and above. The clause protects the unused commitment up to the negotiated cap.

The defense is to model the consumption ramp across the term. A new AI implementation typically consumes less in year one than in year two. The carry over protects the year one under consumption when the year two ramp lands.

How does Redress engage on SAP AI and data licensing?

Redress runs SAP AI advisory inside the Vendor Shield subscription, the Renewal Program, and the dedicated SAP service line. The work covers the consumption forecast, the pool separation, the volume tier modeling, the negotiation, and the audit defense.

Typical engagements deliver 18 to 40 percent discount across the three pools with the carry over and uplift protections negotiated.

How Redress engages

Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the SAP Hub, and the Software Spend Assessment.

Read the related case studies, the benchmarking service, the Benchmark Program, the management team page, the about us page, and the contact page.

Model the SAP estate and the AI consumption pools with the SAP RISE TCO calculator.
Open the Calculator →
White Paper · SAP

Download the SAP RISE Negotiation Guide.

The companion playbook covers the SAP RISE commercial model, the migration credit mechanics, and the negotiation moves that protect the customer through transition.

Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.

SAP RISE Negotiation Guide

Open the playbook in your browser. Corporate email only.

Open the Paper →
3
Separate consumption pools
22%
Median overpay captured
6
Buyer side moves
40%
Discount band at the high tier
100%
Buyer side independence

The July 2025 reset moved AI and data outside the classic SAP user contract. The customer that does not separate the pools at the negotiation table pays the SAP default.

Former SAP Commercial Director
Now on the buyer side, 40 SAP AI engagements advised
More Reading

More from this practice.

SAP Hub →
SAP RISE TCO Calculator
Tool · SAP
SAP RISE TCO Calculator
Model the SAP cloud cost.
8 min read
SAP Advisory Services
SAP · Services
SAP Advisory Services
Buyer side advisory across SAP.
9 min read
SAP RISE Deep Dive
SAP · RISE
SAP RISE Deep Dive
The RISE commercial model.
14 min read
SAP Knowledge Hub
SAP · Hub
SAP Knowledge Hub
All SAP research in one place.
7 min read
Vendor Shield
Program
Vendor Shield
Always on advisory subscription.
6 min read
Editorial photograph of an SAP AI cost review with CFO and CIO around the boardroom table

Cap the AI bill. Protect the Datasphere pool.

We have advised on 40 SAP AI and data licensing reviews since the July 2025 reset. Every engagement starts with one conversation.

Buyer side intelligence, monthly.

Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.