Varad
SAP Joule has moved well past its early days as a simple chat assistant bolted onto S/4HANA. Anyone who has been tracking SAP’s product announcements this year knows the pace of change has been almost dizzying. What started as a conversational helper is now being repositioned as the operating layer for how people actually work inside SAP systems. If you run an SAP landscape, manage a BTP team, or simply use Joule day to day, understanding where this platform is headed matters a lot more than knowing what it used to do.
This article breaks down where Joule stands right now in the middle of 2026, what SAP has confirmed is coming next, and what it practically means for developers, business users, and IT leaders planning their roadmaps for the rest of the year and into 2027.
From Copilot to Autonomous Platform
The biggest shift in Joule’s story this year is the move away from thinking of it as a single assistant. SAP Joule has evolved from a copilot into a full agentic AI platform with more than forty specialized agents and over two thousand four hundred skills. That is not a marketing exaggeration. It reflects a genuine architectural change in how SAP is building the product, spreading intelligence across finance, procurement, supply chain, and HR rather than keeping it confined to a chat window. SAVIC Technologies
At Sapphire 2026 in Orlando, SAP leadership framed the company differently than in past years. SAP CEO Christian Klein presented SAP as a business AI company, announcing 224 agents and 51 assistants spanning finance, spend management, supply chain, HCM, and customer experience. That number alone tells you SAP is no longer treating AI as a bolt on feature. It is the product strategy. ERP Today
Joule Work and the End of Traditional Navigation
One of the more surprising announcements from Sapphire was Joule Work, a new interface concept that SAP describes as replacing traditional app navigation altogether. Instead of clicking through menus and tiles to find the right transaction or report, users describe what they want in plain language and Joule figures out the rest. Joule Work abandons traditional app navigation entirely, letting users describe outcomes in natural language while Joule coordinates data, workflows, and agents to execute them. ERP Today
SAP showed this off with a retail example that resonated with a lot of attendees. H&M demonstrated Store Intelligence Agents monitoring real time retail data alongside an AI powered InStore Concierge that delivers personalized product recommendations to shoppers. It is a good illustration of where SAP wants Joule to go, from answering questions to actively running parts of the business in the background. SAP Community
If your teams are used to memorizing transaction codes and navigating deeply nested Fiori apps, this is worth watching closely. The learning curve for new hires could shrink dramatically once outcome based interaction becomes the norm rather than the exception.
A Unified Platform Underneath
Behind the scenes, SAP has also been consolidating its technology stack so Joule has one consistent foundation to run on. SAP consolidated SAP Business Technology Platform, SAP Business Data Cloud, and AI Foundation into a single unified architecture, with the SAP Knowledge Graph at its core encoding fifty years of SAP ERP engineering into machine readable semantic relationships. This matters more than it sounds like on paper. A lot of the frustration customers have had with AI features in enterprise software comes from those features not actually understanding the data model underneath them. By grounding Joule in a knowledge graph built from decades of SAP’s own engineering logic, the agents are meant to reason about business processes the way a long tenured SAP consultant would, not just pattern match against generic text. SAP Community
Joule Studio 2.0: Building Agents Without an IT Ticket
For developers and citizen developers alike, the most consequential update might be Joule Studio 2.0. SAP has been signaling for a while that it wants to democratize agent building, and this release backs that up with a genuinely low friction offering.
At Sapphire 2026, SAP unveiled Joule Studio 2.0 along with a fully SAP managed version that requires zero infrastructure setup, zero configuration, and zero provisioning by the customer’s IT team. That is a meaningful departure from how BTP development has historically worked. For the first time, a business analyst, a process owner, or a developer at a mid market enterprise can build, test, and deploy a production ready Joule agent without touching BTP configuration or AI Core provisioning. SAVIC TechnologiesSAVIC Technologies
SAP is sweetening the deal to drive adoption too. Customers and partners can receive free design time access, including AI assisted development capabilities under fair use limits, through the end of 2026. If your organization has been holding off on experimenting with agent building because of licensing or infrastructure concerns, this removes a big chunk of that friction, at least for now. SAP
For teams that prefer working in familiar coding tools, SAP has widened its support list as well. Cursor has joined the list of supported coding tools, and AutoGen and LlamaIndex have joined the supported agent frameworks. Combined with the existing Visual Studio Code extension and a dedicated command line interface, Joule Studio is clearly trying to meet developers wherever they already work rather than forcing them into a single proprietary environment. The New Stack
New SAP Domain Models
SAP is also investing in its own foundation models tailored specifically to its ecosystem. SAP introduced the SAP Domain Models, a family of SAP aware foundation models built around the second generation SAP ABAP 2 coding model along with new specialized variants for SAP S/4HANA and Ariba. Early access is already open, with broader availability expected later this year. The New Stack
This is a smart bet on SAP’s part. Generic large language models are good at general reasoning but often stumble on ABAP quirks, custom code patterns, and SAP specific business logic. A model trained specifically on that domain should, in theory, produce fewer hallucinated field names and more usable code suggestions out of the box.
Interoperability Instead of a Walled Garden
For years, one of the fair criticisms of SAP’s ecosystem was that it played nicely mostly with itself. That is visibly changing. SAP has been striking partnerships that open Joule up to tools enterprises already rely on.
SAP acquired a minority stake in the Berlin based automation platform n8n at a five point two billion dollar valuation, integrating it into Joule Studio to give BTP developers a low code orchestration layer for connecting SAP and non SAP systems. General availability for that integration is targeted for the third quarter of 2026, and SAP is positioning it as a way to satisfy GDPR and data residency requirements since workflows stay inside SAP’s own cloud infrastructure rather than crossing into a separately hosted environment. ERP Today
Agent to agent communication is also getting a serious upgrade. The Agent2Agent protocol is now bidirectional, allowing third party agents to natively call Joule agents within enterprise processes, with general availability for bidirectional integration with Salesforce Agentforce and ServiceNow planned for the fourth quarter of 2026. For organizations running a mixed vendor landscape, and let’s be honest, most large enterprises do, this is arguably more important than any single new Joule feature. It means Joule does not have to be the only agent in the room to be useful. ERP TodaySAP Community
On the infrastructure side, SAP has also been quietly making its models more portable. Anthropic’s Claude has been named the primary reasoning model powering Joule across the Autonomous Suite, chosen for multi step reasoning that enables enterprise grade agent workflows with full security and compliance controls. That is a notable signal about how SAP is thinking about reliability at scale, favoring proven reasoning capability over building everything from scratch internally. SAP Community
What This Means for Finance, Procurement, and Supply Chain Teams
The abstract platform talk is interesting, but the practical changes are where most readers will care most. A few concrete shifts are worth flagging for specific business functions.
On the finance side, SAP introduced a new flagship offering called SAP Enterprise Planning built around what it calls a Sense Reason Act model, detecting signals as they emerge, evaluating constraints in real time, and connecting plans directly to execution automatically. SAP has been vocal about the pain point driving this, noting that a large share of organizations still find financial planning, budgeting, and forecasting far too time consuming using traditional periodic cycles.
Procurement teams are getting their own dedicated push too, with autonomous spend management covering the full source to pay lifecycle. Eleven distinct Joule assistants are meant to address the fragmentation that typically exists between procurement, finance, and operations teams, each handling a specific slice of the process rather than one assistant trying to do everything.
Manufacturing and supply chain functions are seeing targeted additions as well, including a new AI window inside the SAP Engineering Control Center that lets users interact with complex control functions using natural language, and a smart BOM recommender that analyzes historical bill of materials data to help production engineers build more consistent structures faster.
Getting Ready for What’s Coming
If you are responsible for an SAP environment, there are a few practical steps worth taking now rather than waiting for everything to go fully generally available.
Start by auditing your current Joule footprint. Many organizations activated basic Joule capabilities early on and never revisited the configuration. Given how much has changed architecturally, it is worth checking whether your tenant is even set up to take advantage of the unified platform changes.
Second, take the free Joule Studio access seriously. With zero infrastructure setup and free design time access running through the end of the year, this is a low risk window to let a few developers or business analysts experiment with building a real agent rather than reading about it secondhand.
Third, think about your clean core strategy alongside this rollout. SAP has been formalizing certification programs for BTP extensions specifically to keep custom code upgrade compatible across release cycles. Agent building only compounds the risk of technical debt if it is not done with governance in mind from day one.
Finally, keep an eye on the interoperability roadmap if you run a multi vendor stack. The bidirectional agent to agent protocol work happening this year could meaningfully change how you think about orchestration across Salesforce, ServiceNow, and Microsoft tools alongside SAP.
The Bottom Line
Joule in 2026 barely resembles the assistant SAP introduced a couple of years ago. It has grown into a genuinely ambitious platform play, spanning a managed low code studio, domain specific foundation models, deep interoperability with outside ecosystems, and a fundamentally different interaction model in Joule Work. Not every piece of this will land smoothly, and general availability dates for several features are still a quarter or two out. But the direction is clear. SAP is betting its future on agents that understand its own business logic natively, and organizations that start experimenting now will have a real head start once these capabilities move from early access into everyday production use.
