Domain expert AI agents for ERP, built on the stack you already own.
We use the SAP AI stack. Joule, BTP, AI Core. Native, supported by SAP, and deployed in your own SAP BTP account. On ECC 6.0, agents connect through SAP BTP and Cloud Connector, or run on our open stack.
Built in SAP Build, deployed beside SAP-delivered Joule skills, grounded on SAP AI Core.
Vendor invoice posting: extraction, orchestrator, rules-based approval, exception routing.
LangGraph, AG2, CrewAI, Smolagents, Google ADK and Pydantic AI, reaching GenAI Hub and HANA Cloud.
Next.js experience UI on a CAP service layer: approvals, intervention, audit trail, agent harness.
TabPFN and transformers for tabular and vision; voice agents on SAP CAP with Amazon Connect and Retell AI.
Five layers we build and integrate across:
WalkMe enablement runs across the stack.
Narrow read, simulate and write services with typed inputs, idempotency and full audit.
Released APIs, CDS views, RAP services and events behind the same contract, dual-run before cutover.
Agent catalog, capability names and versions, approvals, audit, identity and the model gateway.
Build the SAP access contract once. Version the adapters deliberately. Improve the intelligence behind a stable experience.
The SAP BTP solution flow, layer by layer:
Build Code, Work Zone and Process Automation in a multi-cloud subaccount.
Skills and agents built as one project: actions, tools, settings, MCP and outputs.
Custom skills run beside SAP-delivered Joule skills in the central Joule instance.
AI models and document grounding behind every agent.
SAP Cloud Identity Services authenticate users, third-party providers and services.
Business users and technologists both ship agents.
Every request is checked against the SSO session before anything loads. Unauthenticated requests are redirected to your identity provider.
Principal propagation exchanges the session token for a scoped SAP token on each request, so the agent acts with the user's own SAP authorizations. The design avoids shared service accounts.
Each agent is registered with its own routes and scopes. The gateway enforces per-agent quotas and rejects calls outside them.
Personal and sensitive data is masked before a prompt leaves SAP AI Core and unmasked on the way back. External models only ever receive masked prompts.
Every agent calls SAP through one shared, governed gateway. Agents never call CAP, AI Core or S/4HANA directly.
Gateway adapter translates the call to OData or REST for S/4HANA. On ECC 6.0, BAPIs and RFCs are reached through SAP Cloud Connector.
Data masking, SAP AI Core call, optional external model, then unmasking before the result returns.
The router and gateway emit traces, errors, token usage and cost telemetry for every run.
Our AI team is organized around three disciplines that work together on every engagement.
Multi-step agentic workflows that operate within SAP authorization boundaries, from single-task bots to multi-agent orchestration.
Prompt engineering and RAG pipeline design, tuned for structured, high-stakes ERP data.
Anomaly detection, classification and regression on SAP transactional data, run in your existing infrastructure.
No silos and no handoffs. One team carries the engagement from discovery to production.
Every agent ships at a set level, suggest, approve or act, chosen per process. A level is raised only once the evidence from the level below holds up.
Each run records the reasoning it followed and the steps it took, so an approver can see why the agent acted and an auditor can retrace how.
Approvals and intervention happen in the experience layer, over a service layer carrying identity, workflow state and audit trail.
Every candidate agent scored on business value against implementation effort. You approve the sequence.
One agent, one workflow, one success metric. Weeks, not quarters.
Measured against the baseline captured before the pilot. The number either moved or it did not.
The next agents in the queue reuse the integration layer already built and paid for.
Every agent after the first one costs less than the one before it. That is the reason for running this in sequence.
Finance, sales, operations and procurement use cases, each with its own detail page.
Practical answers on running AI agents with SAP ECC 6.0 and S/4HANA.
SAP ECC 6.0 and SAP S/4HANA. Where a capability differs between the two, we agree the approach with you before any build starts.
In your own SAP BTP account, built on Joule, BTP and AI Core. Your data stays inside your SAP landscape and under your access controls.
No. Agents can work on ECC 6.0. If a migration is planned, we take that plan into account when we design the agent.
No. Agents work through authorized interfaces. If a process would benefit from a configuration change, we raise it with your team and your team decides.
Each agent works under its own user with roles that your security team defines and reviews. Anything outside those roles is not available to the agent.
With one exception process. The first conversation covers the process, your SAP landscape and whether a pilot makes sense.
Meet with us about the exception process you feel is most relevant and critical to your team. We will scope it with you and start the pilot.
