Agents in SAP Build Process Automation

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 subaccounts of SAP Business AI Platform. 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. “SAP Build with AI — Joule in Build Code, Build Apps, Process Automation and Joule Studio” covers the wider SAP Build with AI landscape — Build Code, Build Apps, Process Automation, both editions of Joule Studio; this page stays inside the Process Automation and agent-builder slice of it.

Why it matters

• A consultant who knows only the SAP Build with AI overview cannot debug a Tenant Administration Worker - 6011 deployment failure — that requires the design-time/runtime subaccount split this page 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 page covers the Process Automation / agent-builder slice; “SAP Build with AI — Joule in Build Code, Build Apps, Process Automation and Joule Studio” 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

1. SAP-samples GitHub — btp-agentic-ai-use-cases (main README): Escalation Assistant and Joule integration with code-based agents, use cases and services used
2. SAP-samples GitHub — Escalation Assistant with Joule Studio (10-escalation-assistant-joule-studio/README.md): multi-agent design, destinations across subaccounts, Tenant Administration Worker - 6011
3. SAP-samples GitHub — Joule Integration with Code-based Agent (20-joule-a2a-code-based-agent/README.md): A2A, async REST and streaming A2A Client Service, their timeouts
4. SAP Community — Increase business outcomes by unleashing the power of AI agents (SAP-authored blog behind the sample repo)
5. SAP PartnerEdge — BTP Build with AI Foundation use-case webinar series (education library, source of the sample scenarios)
6. SAP Community — Integrating Joule with code-based agents: three paths forward (SAP-authored, canonical framing this page operationalizes)
7. SAP Community — Joule A2A: connect code-based agents into Joule (SAP-authored, the A2A 'Bring Your Own Agent' pattern)
8. SAP Community — Joule A2A: secure code-based agents with IAS (SAP-authored, identity layer for the A2A pattern)
9. GitHub SAP-samples — btp-joule-a2a-pro-code-agent (full A2A + SAP-RPT-1-as-tool reference scenario)
10. GitHub SAP-samples — joule-a2a-agent-toolkit (TypeScript/CAP or Python+LangGraph agent toolkit)
11. SAP Community — Build a pro-code A2A agent for SAP S/4HANA Cloud with the CAP Agent Plugin (Alpha, @cap-js/agents)
12. Joule Studio Agent Builder Hits General Availability — SAPinsider
13. Integrating AI Agents with Joule — SAP Architecture Center
14. Build AI Agents on SAP BTP — SAP Architecture Center (AI golden path)
15. Building AI Agents with Joule Studio — SAP Architecture Center
16. SAP News — Joule Work and SAP Business AI Platform (8 Oct 2026); superseded on status by SAP TechEd (27 Oct 2026): Joule Studio GA rolling out in phases
17. SAP News, 27 Oct 2026 — SAP TechEd press release (governed agent gateway; Joule Studio runtime free through December 2026 for select customers; design time free under fair-use limits)
18. SAP — Commercial Model, version 10.2026 (Joule Studio runtime free to end-2026, p. 10)