AI agents inside SAP S/4HANA
Agents that read your CDS views and OData services, and complete real work — order holds, material verification, returns — with a human approving the edge cases.
S/4HANAODataAgentsFiori
What we build
Most "AI for SAP" demos stop at a chat window that summarises a screen. We build agents that do the work — safely, inside your authorisation concept.
A Torotech agent is a small, auditable service on BTP that:
- reads business context through ABAP CDS views and OData V4 services (no direct table access, ever)
- reasons with a model of your choice (Anthropic Claude, Azure OpenAI, or SAP AI Core)
- summarises data, forms a query, compares records, or proposes an action — entirely through the app's own OData services, with the request shown to an approver before anything writes back
- writes back only after approval rules pass, and logs every step to a change document
Typical first projects
| Process | What the agent does | Guardrail |
|---|---|---|
| Sales order holds | Reads block reasons, credit exposure and delivery dates; drafts the release or the customer note | Release above a threshold needs a human |
| Material verification | Compares inbound ASN, PO and goods-receipt data; flags mismatches with a suggested resolution | Never posts a GR on its own |
| Returns triage | Classifies return reasons from free text and photos; proposes disposition and credit | Credit memo is always approved |
How an engagement runs
- Map the workflow (same day). We sit with the people who do the work today and identify which OData services and entities the app already uses — and the exceptions that actually matter.
- Build and wire it (1–2 days for a simple app). Chat shell, orchestrator, narrow LLM, OData calls — wired into the app that already exists. Nothing gets rebuilt underneath it.
- Test it with the people who'll use it. Real phrasing, real edge cases, before anyone else sees it.
- Go live. One integration, live for every user immediately — write-backs sit behind an approval inbox until the numbers earn wider auto-approval. More complex, multi-system workflows take longer, but the pattern itself doesn't change.
Stack
- SAPUI5 App -- SAP BAS or VSCODE -- SAP S4HANA Backend or SAP ECC(On Prem or On Cloud) -- OpenRouter
Tell us about the process that hurts.
A 30-minute call is enough to tell whether an agent, an extension or a plain good Fiori app is the answer. No deck, no discovery fee.