This is the practical companion to the overview. It sets out exactly what you provide, what we deliver, how it installs into your existing SAP system, and how it stays under your control — no story, just what you need to plan a rollout.
AI Core Hub supplies the control room, the assistant, the knowledge engine and the skills. To switch it on, you bring the following.
Two model roles are needed, and they are different types. A generative model (the brain) reads context and the screen, reasons, calls skills, and writes the answer — essential. A small embedding model turns documents and questions into vectors so the knowledge base retrieves by meaning — this powers grounded answers. Both can be a private model you host, a hosted endpoint, or a corporate AI gateway; usually one provider serves both, so this is one relationship, not two. Optional: split the brain into a fast text model for everyday questions and a stronger reasoning model for the hard cases, with the Hub routing between them.
A small, dedicated team responsible for one product or area. They own its documentation, decide its agents and skills, and keep its knowledge current. Separating products into zones keeps answers accurate and keeps the cost per question (the AI tokens) low — an agent only ever reads its own zone. You stand these up around the teams you already have.
A system to load it into (ECC or S/4HANA). No SAP BTP, no separate platform, no extra servers — it runs inside the system you already operate.
The manuals, specs, process notes and resolved tickets each team wants its agents to answer from. Optional at the start — the baseline-documentation service (below) can give every agent a head start before a team writes anything.
Where teams set up zones, applications, agents, skills, keys and the knowledge base — loaded into your existing system.
The docked chat agent, reachable from any screen, that reads context and answers from your knowledge under the user's own authorisations.
The ready skills (screen reading, safe queries, field help and more), the grounding/knowledge engine, and the framework to add your own.
Installation into your system, the working configuration, and hands-on guidance through a first pilot zone.
AI Core Hub is delivered as a set of standard objects that load into your established SAP functionality. There is no separate runtime, middleware or cloud platform to provision — the configuration Hub and the in-screen assistant simply become available within the system you already operate. The only outbound connection is from your system to the model you nominate, over one managed channel with keys held centrally. Every data read happens under the user's own SAP authorisations.
A typical adoption path:
Most SAP landscapes have thousands of objects and very little documentation. As an optional part of implementation, we scan the objects across your system — tables, programs, transactions, custom code, and the way they connect — and produce a system-wide picture of how it fits together. This becomes baseline knowledge every agent can draw on, so even a zone that hasn't loaded its own documents still answers usefully from day one.
It is delivered as a single comprehensive document, or, if you prefer, split into separate documents per area or product. The result is yours to keep — living documentation of a landscape that usually has none — and can be refreshed as your system changes.
Agents are useful on day one, before any team has documented a thing.
It captures how objects connect, so answers understand context rather than just names.
Team documents layer on top and take priority; the baseline stays as the fallback.
| Capability | Status |
|---|---|
| In-screen chat agents (personas) with knowledge + skills | in the prototype |
| Per-team zones, applications, skills registry, key resolution | in the prototype |
| Knowledge base (grounded answers from your documents) | in the prototype |
| Baseline documentation of your whole system (one or many documents) | service |
| Workflow agents (ServiceNow responder, intelligent background jobs) | rolling out |
| Guided data changes inside standard SAP transactions | roadmap |
| Term | Meaning |
|---|---|
| Zone | A dedicated team that owns one product or area, with its own agents, documents and keys. |
| Application | A single transaction or a whole business area — wherever a group of people do their work. |
| Agent (persona) | A name, an instruction and one focused job. Never a generic “bot”. |
| Skill | A concrete, safe action an agent may take inside SAP — read the screen, check stock, run a read-only query. |
| Knowledge base | A zone's documents, filed by meaning, that agents answer from (RAG). |
| Keys | The connection to your AI models, resolved centrally at company / team / user level. |
| Chat agent | A persona that answers questions, docked beside a screen. |
| Workflow agent | A persona triggered by an event or schedule that runs a process on its own. |
The fastest way to evaluate AI Core Hub is a short pilot on one team and one transaction.