SAP Shows How Enterprise AI Development Really Works
The debate about AI replacing developers misses the point. At SAP, AI isn't replacing anyone—it's solving the real problems that slow down enterprise development teams.
Bharat Sandhu, SVP and CMO, SAP Business Technology Platform where thousands of developers build applications that connect to complex SAP systems. His team has moved beyond basic code completion to something more practical: AI that understands enterprise context.
The Context Problem
Most AI coding tools work fine for standalone applications. But enterprise development is different. When a developer wants to access a general ledger, the AI needs to know which database to query, what records to examine, and how that connects to supply chain or HR systems.
"Context is what differentiates and what matters," Sandhu says. "It's not just the context of the application code. It's the context of your back end systems."
SAP's Joule for Developers handles this through what they call semantic understanding. The tool connects to a knowledge graph that knows what a sales order is and how it relates to customers, inventory, and financial data. This isn't just about writing better code—it's about writing code that actually works in complex business environments.
Making Legacy Code Useful Again
Every enterprise has the same problem: mountains of legacy code written by people who no longer work there. Documentation is sparse. Business rules are buried in decades-old logic.
Joule for Developers tackles this head-on. It can read existing code and explain not just what the code does, but which SAP tables it accesses and how it connects to business processes. It can refactor old code to make it more maintainable and generate documentation so future developers don't face the same problems.
"The biggest challenge customers have is a lot of legacy code," Sandhu explains. "People wrote code, and then they retired, and now you have these monolithic applications."
The Developer Response Surprised Everyone
SAP expected resistance from experienced developers and enthusiasm from newcomers. What happened was the opposite.
Initially, senior developers were skeptical while junior developers got excited about AI assistance. But that pattern flipped. Experienced developers realized they could focus on architecture while AI handled routine tasks. They also knew how to use these tools more effectively.
"The advanced developers became bigger fans and use it much more effectively," Sandhu says. "They know what good looks like."
This mirrors what happened with low-code platforms. Developers initially rejected them as beneath their skills, then adopted them when project demands became overwhelming.
Agent-Based Development Changes Everything
SAP has moved beyond code completion to what Sandhu calls agent-based development. Instead of writing individual functions, developers can describe complete business applications.
Tell the system you want an invoice processing application that flags payments overdue by 90 days from specific suppliers and regions. The AI creates the data model, builds the business logic, and handles the user interface.
This isn't magic. The code still goes through testing and human review. But it shifts developer time from writing basic CRUD operations to solving actual business problems.
Why Most AI Projects Fail
Sandhu has seen plenty of failed AI implementations. The pattern is always the same: companies treat AI as an experimental side project instead of core business transformation.
"Most customers work on the fringes of systems," he says. "To really use AI innovatively, you have to change core processes. You have to work inside out from business systems."
Successful companies don't create AI innovation labs. They integrate AI into existing workflows that already generate revenue. They change how they make products, serve customers, or run operations.
"It's easier to change an existing business model and make it better than to create a new project with a new business model on the side," Sandhu explains.
The Enterprise Advantage
Consumer AI tools train on public code repositories. Enterprise AI tools need different training data and different security models. SAP hosts its own models and never uses customer data for training. The code AI generates goes through multiple validation layers before reaching developers.
This enterprise focus creates opportunities for new types of applications. Sandhu mentions compliance systems that understand spending patterns in ways rule-based systems never could. Travel booking agents that negotiate across multiple vendors within budget constraints. Applications that were too complex to build before AI became practical.
What's Next
The speed of change makes long-term predictions difficult. But Sandhu sees clear short-term trends. Development teams will reorganize around AI capabilities. Requirements documentation will become more important as natural language interfaces improve. Agents will write and deploy code based on performance metrics.
His advice for developers is simple: start now. Don't wait on the sidelines. The tools are ready, the productivity gains are real, and the competitive advantage goes to teams that learn these workflows first.
The question isn't whether AI will change enterprise development. At SAP, it already has.
