-
How is this different from your Joule Agents page?
-
This page is the platform: adopting the SAP Business AI Platform, grounding it in your data, and choosing your models and governance. The Joule Agents page is the agent-building practice that runs on top of it, including how we ship a fleet of agents against a real S/4HANA tenant. Most clients need the platform work first.
-
Do we have to use SAP Joule and SAP's models, or can we use our own?
-
Either. You can run Joule with SAP Domain Models, or bring your own LLM on AWS Bedrock, OpenAI, or Anthropic and let SAP ground and serve it through the Generative AI Hub and MCP Gateway. The SAP-side work, Domain Models, BDC, Integration Suite, identity, is the same either way, which is the part we focus on.
-
Will our existing AI experiments survive SAP's endorsed-path direction?
-
SAP is steering agent calls onto endorsed paths: Joule, Integration Suite, or the MCP Gateway. If your experiments call SAP APIs another way, expect rework. We build on those endorsed paths already, so what we deliver holds up as the guidance tightens.
-
How do you keep an AI agent from giving wrong answers on our data?
-
Trust comes from the data layer, not the model. Our agents read through the same official OData APIs that Fiori uses, with no caching or shadow data, so a user can verify any answer against the system of record. We ground answers in SAP Domain Models and BDC, and require human approval on anything that writes back to SAP.
-
We are still on on-premise S/4HANA. Is this only for cloud?
-
No. The agents and MCP servers we run in production today connect to on-premise S/4HANA through BTP destinations and Cloud Connector, the same trust layer your other integrations use. The AI platform lives on BTP, your system of record can stay where it is.