#20261113002_EN1 min readCategory: SAP transformation
By Cahit Temizkan, Founder & Managing Director, OXORY
The question behind most AI-in-SAP projects
Most teams do not struggle with the model. They struggle with the access path: how should an agent read from and write to SAP in a way that is controlled, traceable and survives the next upgrade? There are three realistic answers.
Three paths, one rule
The rule we apply: **API and MCP first, screen reading only where no API exists, and the language model only reasons. It never touches SAP directly.**
- **Joule Studio.** SAP-native, centrally managed, built on SAP Build and BTP. Skills handle fixed, repeatable operations; agents plan and pick tools for processes with exceptions.
- **MCP server.** An open standard that exposes SAP functions (OData, BAPI, RFC, REST) as tools with schemas. It runs with or without BTP and is reusable across agents.
- **Screen reading.** An agent that sees the screen, clicks, types and verifies. It works for SAP GUI, legacy applications and portals, but it is sensitive to UI changes.

What is easy to get wrong
MCP only governs access. It does not give an agent business context; that comes from tool descriptions, authorizations and grounding in your own data. Third-party MCP servers also come with operational responsibility on your side, a point SAP's own architecture guidance makes explicitly. And a screen-reading agent needs an isolated session, a restricted technical user, human approval for critical steps and a maintenance plan.
Read the full technical paper
We wrote the details up as a technical paper: the three AI layers on BTP, skill versus agent, the reference architectures, both custom paths, a decision table and the guardrails. Read the technical paper.
If you want to know which path fits your landscape, a short potential workshop is the usual first step. Talk to us.
Next step
Let's work out how this applies to your own SAP landscape and delivery plan.
Read the technical paperMore articles
— AMS & support
In-House Team or Outsourced AMS? Decision Matrix for SAP Support
— AMS & support
How to Calculate SAP AMS Costs
— Shoring
SAP Shoring or Nearshore? Model and Cost Comparison
