Analyst(s): Keith Kirkpatrick
Publication Date: August 19, 2026
SAP has expanded agentic AI across ABAP development through an MCP server, Visual Studio Code support, custom code migration agents, and broader release coverage. The strategy could reduce transformation work, but its success depends on code accuracy, business logic retention, and predictable usage costs.
What Is Covered in This Article:
- SAP’s open IDE and MCP strategy for agentic ABAP development
- Custom code agents designed to support SAP S/4HANA migration
- Controls for code accuracy, business logic, security, and data protection
- Expanded release support and consumption-based pricing for ABAP AI
- SAP’s broader shift toward autonomous enterprise workflows
The News: SAP outlined the next stage of its ABAP strategy in an August 18 interview with Sonja Liénard, senior vice president and head of ABAP platform. Liénard explained how SAP is combining ABAP Cloud, developer-focused AI capabilities, and specialized agents for transformation, migration, and quality validation.
The interview provided additional detail on SAP’s open IDE strategy, the role of its ABAP MCP Server, and safeguards covering code accuracy, business logic, security, and data protection. It also identified upcoming milestones, including a second clean-core transformation agent planned for Q3 2026 and further multi-agent orchestration during 2026.
Will Usage-Based Pricing Broaden Agentic ABAP Development?
Analyst Take: SAP has provided further detail on how its open developer tools, MCP server, migration agents, and expanded release support fit into its agentic ABAP development strategy. The approach could reduce transformation work, but its success depends on code accuracy, business logic retention, and predictable usage costs.
Open Tooling Broadens Agentic ABAP Development
SAP’s open IDE strategy adds Visual Studio Code alongside Eclipse and gives ABAP developers access to an environment with a broad ecosystem of AI extensions. The initial Visual Studio Code release focuses on ABAP Cloud and SAP Fiori application development, while SAP plans to add classic ABAP support and more object types during 2026. Eclipse remains the full-featured ABAP development environment until Visual Studio Code reaches feature parity, and the first custom code migration agent currently requires Eclipse. The ABAP Language Server separates development capabilities from the IDE, while the MCP server exposes those capabilities to compatible coding agents in both cloud and on-premises environments from release 7.31 onward. This architecture makes interoperability, rather than a single SAP-controlled assistant, the foundation of agentic ABAP development.
Migration Agents Target Custom Code Complexity
Custom ABAP code can contain years of undocumented business logic that remains tightly connected to standard SAP objects, making SAP S/4HANA migration time-consuming and expensive. SAP’s first Mass S/4 Custom Code Conversion Agent identifies ABAP Test Cockpit issues and fixes them at scale through deterministic rules or AI-generated changes. SAP plans to add a Mass Clean Core Adoption Agent and a Web Dynpro to SAP Fiori App Modernization Agent later in 2026 as part of a migration strategy spanning seven agent families from planning through execution. The company targets a 40% efficiency gain in custom code transformation work, while its broader AI-powered ERP migration toolchain aims to reduce migration costs by up to 30%. These targets make migration efficiency a measurable test of whether SAP’s agents can move beyond code assistance and materially improve ERP transformation.
Automation Still Requires Human Judgment
AI-generated code can appear plausible while containing subtle errors, so SAP combines human review with agent-led testing and validation. AI agents perform quality checks, but developers retain responsibility for judgment at critical steps involving business logic and architecture. SAP also directs its custom code agents to explain and understand existing code before proposing changes, which addresses the risk that automation could remove logic built up over many years. ABAP AI services operate within SAP compliance and trust frameworks, and customers control which contextual information they share when models access sensitive business data. Agentic ABAP development will only support critical enterprise processes if SAP maintains these controls as the number and scope of agents increase.
Pricing Could Determine the Adoption Curve
SAP has lowered technical access barriers by extending ABAP AI to SAP S/4HANA Cloud Private Edition releases from 2021 onward through a hub service on SAP Business Technology Platform. The service combines authentication, license management, access to SAP BTP AI Core, and ABAP-specific business logic while operating largely independently of the backend release. SAP has also replaced users-per-month billing with consumption-based AI units, and the free promotion for SAP Joule for Developers ABAP AI capabilities ends in September 2026.
SAP must show that AI units provide predictable costs in practice because broader technical availability alone does not resolve buyer uncertainty over how agentic capabilities should be priced.
ABAP Forms Part of SAP’s Broader Agent Strategy
SAP’s ABAP initiative also supports a wider plan to release nearly 50 AI assistants by the end of Q3 FY 2026 and more than 400 Autonomous Suite agents by FY 2026. The company is embedding AI across finance, procurement, supply chain, human resources, and customer operations rather than treating it as a separate chatbot layer. Dremio adds data lakehouse capabilities across SAP and non-SAP data, Reltio strengthens master-data governance and semantic models, and Prior Labs adds AI capabilities for structured business data. Management expects consumption-based, usage-based, and value-based models to drive more cloud growth by 2030 than traditional seat expansion. SAP’s broader agent strategy will depend on connecting this data foundation and commercial model to controlled execution within the business workflows that ABAP supports.
What to Watch:
- Can SAP expand Visual Studio Code beyond its initial SAP Fiori scope quickly enough to reduce dependence on Eclipse for full ABAP development?
- The planned Q3 FY 2026 clean-core transformation agent will test whether SAP can extend automation beyond initial custom code conversion while preserving business logic.
- How closely will efficiency gains from the Custom Code Assistant track SAP’s 40% target across customer migration projects?
- Customers will need to assess whether AI-unit consumption provides more predictable spending once the free promotion ends in September 2026.
- Code accuracy and human oversight will remain key measures as SAP introduces more agents and multi-agent orchestration.
- Consistent governance across finance, procurement, supply chain, human resources, and customer operations will become more consequential as SAP expands Autonomous Suite agents.
See SAP’s complete feature on how agentic AI is advancing the ABAP platform.
Declaration of generative AI and AI-assisted technologies in the writing process: This content has been generated with the support of artificial intelligence technologies. Due to the fast pace of content creation and the continuous evolution of data and information, The Futurum Group and its analysts strive to ensure the accuracy and factual integrity of the information presented. However, the opinions and interpretations expressed in this content reflect those of the individual author/analyst. The Futurum Group makes no guarantees regarding the completeness, accuracy, or reliability of any information contained herein. Readers are encouraged to verify facts independently and consult relevant sources for further clarification.
Disclosure: Futurum is a research and advisory firm that engages or has engaged in research, analysis, and advisory services with many technology companies, including those mentioned in this article. The author does not hold any equity positions with any company mentioned in this article.
Analysis and opinions expressed herein are specific to the analyst individually and data and other information that might have been provided for validation, not those of Futurum as a whole.
Read the full Futurum Group Disclosure.
Other Insights From Futurum:
SAP Q1 FY 2026 Earnings Show Cloud ERP Suite Acceleration
Precision Over Prose: Why SAP Knowledge Graph is the Secret to Production-Ready AI
Can SAP Finally Kill the ETL Monster? The Dremio and Prior Labs Acquisition Explained
Author Information
Keith Kirkpatrick is VP & Research Director, Enterprise Software & Digital Workflows for The Futurum Group. Keith has over 25 years of experience in research, marketing, and consulting-based fields.
He has authored in-depth reports and market forecast studies covering artificial intelligence, biometrics, data analytics, robotics, high performance computing, and quantum computing, with a specific focus on the use of these technologies within large enterprise organizations and SMBs. He has also established strong working relationships with the international technology vendor community and is a frequent speaker at industry conferences and events.
In his career as a financial and technology journalist he has written for national and trade publications, including BusinessWeek, CNBC.com, Investment Dealers’ Digest, The Red Herring, The Communications of the ACM, and Mobile Computing & Communications, among others.
He is a member of the Association of Independent Information Professionals (AIIP).
Keith holds dual Bachelor of Arts degrees in Magazine Journalism and Sociology from Syracuse University.
