SAP Joule Licensing: What's Actually Included in Each Plan

What SAP Joule Actually Is (and Isn't)

SAP Joule is SAP's enterprise AI copilot — a natural language interface that connects to SAP applications and enterprise data to answer questions, execute transactions, and surface insights. Launched in 2023 and expanded significantly through 2024 and 2025, Joule is positioned as SAP's primary AI differentiator in the cloud ERP market and a key reason for enterprises to choose RISE or GROW with SAP over competitive alternatives.

The confusion about SAP Joule licensing begins with SAP's own marketing. Joule is presented as a single, unified AI assistant — but technically it is a family of capabilities built on SAP AI Core, integrated into different SAP applications at different depths. Joule in SAP S/4HANA handles financial and operational workflows. Joule in SAP SuccessFactors addresses HR use cases. Joule in SAP Ariba supports procurement. Each integration represents a different set of AI skills built on the common Joule framework — and each may be separately licensed or separately within scope of your contract.

All Joule capabilities consume SAP AI units. The amount consumed varies by application and use case complexity. And the total AI unit allocation in your contract determines how extensively your users can engage Joule before incurring overage charges or needing to purchase additional capacity. Understanding this architecture is the foundation for understanding why SAP Joule pricing plans differ so much in practice from what they appear to include on paper.

Joule in RISE with SAP: What's Included

RISE with SAP is SAP's flagship cloud ERP bundle, and Joule is central to its value proposition. SAP's commercial positioning suggests Joule is broadly included in RISE — but the actual inclusion depends on which RISE edition you're on, which S/4HANA release is in your contract, and what AI unit allocation is specified in your Order Form BoM.

What RISE contracts commonly omit — or present as included when they are not — is the AI unit allocation required to sustain meaningful Joule adoption at scale. Our RISE with SAP advisory team reviews the specific AI unit schedule in every RISE contract we evaluate, because the bundled allocation is almost always undersized for enterprise-wide Joule deployment.

Joule in GROW with SAP: The More Limited Picture

GROW with SAP is SAP's mid-market cloud ERP offering, built on S/4HANA Cloud Public Edition. Joule inclusion in GROW is more restricted than in RISE — a distinction that SAP's sales team does not always volunteer during the sales process, particularly with growing companies being upsold from on-premise ECC to cloud.

GROW contracts typically include Joule access limited to the core S/4HANA Public Edition skill set — the predefined, SAP-managed Joule capabilities that come with the Public Edition application. Custom Joule scenarios, extended knowledge base connectivity, and cross-application Joule skills outside the standard Public Edition scope require additional AI unit purchases and, in some cases, a BTP add-on that is not included in the base GROW bundle.

For mid-market enterprises, this creates a specific cost risk: the AI capabilities that are most valuable for their specific business processes — custom procurement workflows, industry-specific transaction processing, integration with non-SAP systems — are precisely the capabilities that fall outside GROW's standard Joule inclusion. By the time this becomes apparent, the enterprise is committed to a contract that doesn't cover their actual AI use cases, and SAP has the leverage to charge premium rates for the add-ons required.

Joule in S/4HANA Cloud Public Edition

For enterprises running SAP S/4HANA Cloud Public Edition outside of the GROW bundle, Joule access follows a simpler but equally important licensing logic. Joule in S/4HANA Cloud Public Edition is a feature of the application itself — it does not require a separate Joule licence as a standalone purchase. However, the depth of Joule capability available to a given user depends on their named user licence type.

Professional Users in S/4HANA Cloud Public Edition have full access to the embedded Joule skill set for their assigned functional areas. Limited Professional Users have a restricted subset. Functional Users — often used in operational or data-entry scenarios — have minimal or no Joule access depending on their functional scope. This user-type dependency on Joule capability is not prominently documented in SAP's standard product literature, which means enterprises often discover that their majority user population (which is typically Licensed as Limited Professional or Functional rather than Professional) has less Joule access than they anticipated.

The AI unit consumption mechanics in Public Edition follow the same rules as RISE: AI units are consumed per Joule interaction, allocated at the contract level, and expire at year-end without carryover unless explicitly negotiated. For a complete picture of how AI units work across SAP's cloud portfolio, see our guide to SAP AI unit consumption.

Joule Standalone Add-On SKUs

For enterprises that need Joule capabilities beyond what their RISE, GROW, or S/4HANA Public Edition contract includes, SAP offers add-on SKUs that can extend coverage in specific directions. The most common add-ons our team encounters in contract reviews are:

• Joule for Custom BTP Applications: Enables Joule embedding in BTP-developed custom applications — not included in standard RISE or GROW bundles. Requires BTP AI Core capacity in addition to AI unit allocation.
• SAP AI Foundation (formerly AI Core + AI Launchpad): The underlying infrastructure for custom AI model training, deployment, and orchestration. Required if you want to use your own LLMs alongside Joule's SAP-managed models.
• Joule for SAP BTP Integration Suite: Extends Joule AI assistance to integration workflow design and monitoring — relevant for enterprises managing complex SAP-to-third-party integrations.
• Extended AI Unit Blocks: Additional AI unit capacity beyond bundled allocation, available at block pricing. Per-unit economics vary significantly by block size and account context — always benchmark against what's achievable through negotiation.

Each of these add-ons carries its own pricing, and none are included in standard RISE, GROW, or S/4HANA contract bundles unless explicitly specified in your Order Form. SAP's commercial team will typically present these as optional enhancements — but for enterprises with ambitious AI deployment roadmaps, they are functionally necessary, which gives the SAP team leverage to charge premium rates if the need arises post-contract-signing.

The Hidden Gaps SAP Doesn't Advertise

Beyond the plan-level inclusions described above, there are structural gaps in Joule licensing that SAP's commercial team avoids discussing proactively. Knowing them before contract negotiations gives enterprise buyers the ability to close them before they become cost problems.

Gap 1: New Joule Skills Released After Contract Signing

SAP releases new Joule skills and capabilities on a regular cadence — quarterly or faster in periods of rapid development. Whether these new skills fall within your contracted Joule coverage depends on how your Order Form defines "SAP Joule." If the definition references specific service identifiers or a point-in-time capability list, new skills released after signing may be outside your entitlement. SAP's standard contract language does not automatically include future Joule capabilities — forward-looking coverage clauses must be explicitly negotiated. Our contract negotiation team includes forward-looking AI coverage as a standard clause in every contract we review.

Gap 2: Third-Party Data Source Integration

Joule's ability to query non-SAP data sources — SharePoint, Salesforce CRM, custom enterprise data lakes — requires additional configuration on SAP AI Core and, in many cases, additional BTP service consumption beyond the standard Joule allocation. Enterprises planning to extend Joule beyond SAP system boundaries need to account for this additional infrastructure cost, which is entirely separate from the AI unit consumption of Joule queries themselves.

Gap 3: Joule Admin and Configuration Rights

Configuring Joule — defining knowledge sources, tuning response quality, managing skill assignments, monitoring consumption — requires specific BTP roles and potentially BTP Professional User licences. These configuration and administration rights are not included in the end-user Joule access that comes with RISE or GROW Professional User licences. Enterprises that deploy Joule without a dedicated admin resource typically discover they need BTP access rights they haven't licensed, generating additional compliance exposure.

Negotiating Forward-Looking Joule Coverage

The most important Joule licensing negotiation is not about today's capability set — it's about ensuring your contract covers the Joule capabilities SAP will release over the next three to five years. SAP's AI development velocity has increased substantially since Joule's launch, and the gap between what's included in standard contract language today and what Joule will be capable of by renewal time in 2027 or 2028 is significant.

Effective negotiating positions for Joule coverage include: defining Joule entitlement by application scope rather than specific service identifiers (so new S/4HANA skills are automatically in scope); including an explicit "future AI capabilities" clause that covers Joule features released during the contract term without additional charge; and tying the AI unit allocation to a usage-scaled model rather than a fixed block, so that adoption-driven consumption growth doesn't automatically trigger expensive overage.

None of these terms are offered by SAP as standard. All require documented preparation and a willingness to push back on SAP's first-draft contract language. Enterprises that engage independent SAP licensing advisors before signing Joule-inclusive contracts consistently achieve broader coverage, better unit economics, and more flexible consumption terms than those negotiating directly against SAP's commercial team.

For the full picture of how Joule licensing sits within SAP's AI strategy, see our comprehensive SAP AI licensing overview for 2026. For budget planning guidance, see our SAP AI budget planning framework.