At SAP Sapphire 2026 in Orlando, CEO Christian Klein took to the stage and unveiled a huge reframing of SAP’s product story. The “Autonomous Enterprise” is the new vision. It is an AI-driven ERP ecosystem where intelligent agents automatically coordinate and execute complex business workflows with humans supervising rather than manually managing every step.
For SAP-using organizations, this announcement signals a shift: the scope and complexity of change management has increased substantially.
About this series: Navigating the Autonomous Enterprise
This article is part 1 of a 4-part series dedicated to unpacking the major components of the Autonomous Enterprise and what it means for change management teams using SAP today.
- Part 1: SAP Autonomous Enterprise: Key Notes of Change from SAP Sapphire 2026
- Part 2 (coming soon): SAP’s Business AI platform extends the scope of change management and governance in SAP
- Part 3 (coming soon): Ensuring success in the Clouds begins on the ground
- Part 4 (coming soon): Preparing for SAP’s Business AI platform
The 3 Pillars of the Autonomous Enterprise
To understand the role of change management, we must look at the architecture that Klein introduced under the Autonomous Enterprise banner.
- SAP Business AI platform: SAP has bundled BTP, Business Data Cloud, and Business AI into a single environment.
- SAP Autonomous Suite: The workforce – at the time of writing there are 51 Joule Assistants orchestrating 224 specialized agents across finance, supply chain, procurement, HCM, and CX.
- Joule Work: The new front door where you describe the outcome and Joule routes the data, workflow, and agents to deliver it.
We’ve been watching SAP’s AI development closely, with particular attention to the supporting infrastructure around it – especially BTP as essential for ABAP extensions in Public Cloud, Integration Suite, and the adoption of clean core concepts.
The stability of change
So, almost two weeks in, what’s the impact for Basis teams and SAP developers? Nothing… yet!
The SAP Business AI platform is built on top of core ERP. The role of change management will transform to include a larger set of core assets the business depends on. Core ERP won’t go away but instead becomes the foundation for future innovation. On it, agentic AI and the Autonomous Enterprise are built, utilizing the foundational layers managed today.
How does this impact change management teams?
Classic SAP changes are now agent-facing. A transport modifying a transaction, a BAPI or Z-program used to land in QA where humans clicked through it.
Now that same transport may break, alter or silently degrade an agent execution path. The agent doesn’t necessarily fail loudly – it might just perform tasks incorrectly or with incorrect information.
Agent definitions are themselves changes. A prompt update, a guardrail tweak, a tool permission added in Joule Studio, are configuration changes which in every sense matter to an auditor. SAP will version them inside Joule Studio. It’s up to change management teams to gate them through the same approval processes SAP ABAP changes receive today.
Small changes might have bigger impacts. Whether it is cost center reorganization, a refractor of master data, or a change to a customizing node in S/4HANA, backend updates are no longer low impact. A customizing entry now has the potential to alter agent behavior.
Customizing has always had impact, but like other types of change, the area of impact is now potentially much larger and perhaps not fully known until runtime.
Agent identity and entitlement is a change. Agents act with authority. Whose authority? Service accounts have been a Segregation of Duties (SoD) headache forever, and we’re now scaling them up by an order of magnitude and giving them autonomous decision rights.
Every permission granted to an agent is a SOX-relevant change. Every revocation is too.
Change is inevitable with the Autonomous Enterprise
The Autonomous Enterprise is genuinely interesting. The shift in user experience from “person performs task” to “person oversees autonomous execution” is the most consequential thing SAP has shipped since Fiori, arguably since Business Suite.
It changes the job of the SAP user. It changes the job of the Basis team. It changes the job of the auditor. And it absolutely changes the job of change management.
What doesn’t change is the rule that’s been true for 30 years of SAP: the system is only as reliable as the discipline around the changes made to it.
The agents inherit that discipline. Or the absence of it. And the tools enforcing that discipline today don’t go away but become more important.
Klein said it himself from the stage: ”Moving to the Autonomous Enterprise requires serious change management. Adoption of AI goes hand-in-hand with business process change and end-user enablement.”
The role of change management just got a lot more technical, a lot more strategic, and infinitely more important.
Next week in part 2, we will dive into our thoughts on governance and compliance in an agentic ERP environment and explore the coming new requirements for change teams.