Concept card

Agents in SAP Build Process Automation

As of 2026-09-25

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Agents in SAP Build Process Automation?

C122 maps SAP Build with AI end to end; this card is the narrower, hands-on view of one path through it — building a Joule agent whose action-taking step is a process automation, wired to sub-agents, document grounding and MCP servers, and, when the agent needs to reach code outside Joule, connected through one of three A2A integration options with their own hard timeouts.

Design time and runtime live in different subaccounts

An agent built in Joule Studio's agent builder is designed inside SAP Build Process Automation but executes inside a Joule instance — and SAP's own sample code is explicit that these are frequently two different SAP BTP subaccounts. When that split exists, any BTP destination the agent depends on — an MCP server's credentials, for instance — must be created identically in both subaccounts: once for SAP Build Process Automation at design time, once for the Joule instance at runtime. Skip one and the deployment doesn't fail quietly; SAP's documented failure mode is a specific error, Failed to create agent using mass deploy content due to exception... (error code: Tenant Administration Worker - 6011), which reads like an infrastructure problem but is almost always a missing destination in one of the two subaccounts. C122 covers the wider SAP Build with AI landscape — Build Code, Build Apps, Process Automation, both editions of Joule Studio; this card stays inside the Process Automation and agent-builder slice of it.

Why it matters

A consultant who has only read C122's survey of SAP Build with AI cannot debug a Tenant Administration Worker - 6011 deployment failure — that requires knowing the design-time/runtime subaccount split this card documents.
The 'process automation inside a skill' pattern is the documented answer to a question every agent build eventually asks: where does a write action actually happen, and how is it audited and retried?
Picking A2A for a task that legitimately takes longer than a minute produces a hard, undebuggable timeout; knowing the three integration shapes upfront avoids a redesign mid-project.

Key points

Joule agents are designed in SAP Build Process Automation (Joule Studio agent builder) but run in a Joule instance — often a different BTP subaccount.
Destinations (e.g. MCP server credentials) must be duplicated in both subaccounts; a missing one surfaces as 'Tenant Administration Worker - 6011' on deployment, not as a named missing destination.
SAP's own reference pattern for a write action: a process automation invoked from inside a skill, not a bare REST call from the agent.
Multi-agent design: a root agent orchestrates specialised sub-agents (e.g. policy check, search, record handling), each independently configured and testable in the agent builder.
Web/external tool access in Joule agents runs through MCP servers registered as BTP destinations.
Reaching code-based agents outside Joule: direct A2A (1-minute timeout), async REST API (5-minute timeout), or an intermediate A2A Client Service with streaming for longer tasks.
Code-based agents are typically built with the SAP Generative AI Hub, SAP Cloud SDK for AI, and a framework such as LangGraph.
This card covers the Process Automation / agent-builder slice of SAP Build with AI; C122 covers the full landscape (Build Code, Build Apps, both Joule Studio editions).

Terms used on this page

Agent builder: The Joule Studio capability for composing Joule agents from skills, instructions and sub-agents.
Destination: A BTP configuration object holding connection details (e.g. an MCP server's credentials) that must exist in both the design-time and runtime subaccount.
Root agent / sub-agent: A multi-agent design where one orchestrating agent delegates specialised tasks to independently configured sub-agents.
A2A (Agent-to-Agent) protocol: The protocol Joule uses to call an external, code-based agent directly; capped at a one-minute request timeout in SAP's documented example.
A2A Client Service: An intermediate streaming service placed between Joule and a code-based agent to support long-running tasks without hitting a fixed timeout.
Tenant Administration Worker - 6011: The error code SAP's sample documents for a mass-deploy failure typically caused by a destination missing in one of the two subaccounts.

Sources

Full card available to members. What the full card adds: the full decision framework · the common pitfalls and their fix · the cheat sheet · the code blocks · the facts worth quoting.

Open in the app →