ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
Joule Studio, classic edition
The low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.
Extending Joule beyond SAP's own agents means a skill or an agent of your own, and this is SAP's published way to build one without a code base. A project of type Joule agent and skill is created in the SAP Build lobby. A skill is deterministic: input and output parameters, actions that wrap OData APIs through destinations configured in the BTP cockpit, conditional logic and response templates. An agent is defined by an expertise and instructions, a choice of LLM provider, base model and advanced model, a maximum number of thinking steps, and its tools: Joule skills, document grounding from resource groups in SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp, a calculator, other agents as sub-agents, and MCP servers reached through streamable-HTTPS destinations carrying the property sap-joule-studio-mcp-server. Deployment registers the result with Joule. Since the new Joule Studio was announced on 2026-05-13, SAP's documentation carries this one as the classic edition.
Where it sits
Lives in
Provides
Agent toolingCAPBTPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.
Serves
Requires
SAP AI CoreSAP AI Coredocument grounding as an agent tool: the resource groups holding the documents live in SAP AI Core
Designs
Integrating and Extending JouleIntegrating and Extending Jouledesign time for custom Joule skills and AI agents
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
Before choosing this
Conditions
PolicySAP API Policy 4.2026a§ 2.2.2from Agent toolingAn agent built into an application reaches SAP Application APIs, whether directly or through tools generated from a service that proxies them.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
capire's own guide states that CAP-level agents are intended only for exposing custom CAP application services, and names section 2.2.2 for the agentic-access provisions. Check which endpoints the agent's tools end up calling, and consult SAP's reference architectures for the endorsed routes.
SAP API Policy 4.2026a →What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
Connections
Group by
NodeRelationBasis
Functional
Agent toolingAgent toolingBuilding an agent into your own applicationSAP and community, unassessed
provides
stated
provides Agent tooling
Builds a Joule agent on a canvas, expertise, instructions, model settings and tools, and a Joule skill as a deterministic flow over OData actions, and deploys both to Joule.
“Add tools to your agent. The following tools are available: Document grounding Calculator Joule skill”“Configure Destinations : Set up Action Projects to wrap OData APIs and connect to backend systems”“Destinations have the required additional property of sap-joule-studio-mcp-server = true”
Building an agent into your own application
Technical
SAP AI CoreSAP AI CoreAI runtime on BTP with the Generative AI Hubsap official, btp
needs
stated
needs SAP AI Core
document grounding as an agent tool: the resource groups holding the documents live in SAP AI Core
“Document grounding: create resource groups in AI Core with your business documents, then add those resource groups as tools to your agent in Joule Studio.”
AI runtime on BTP with the Generative AI Hub
Download
Learn more
Readings
- Adapting SAP Joule for Purchase Order Creation from an Existing Purchase RequisitionAdapting SAP Joule for Purchase Order Creation from an Existing Purchase RequisitionA custom Joule Agent and Joule Skill, built in Joule Studio, classic edition to extend SAP Joule past its built-in Purchase Order display and change features: a buyer's single sentence naming a Purchase Requisition number becomes a created Purchase Order, with the skill wrapping the Purchase Requisition and Purchase Order OData V4 APIs as Action Packages reached through two destinations. The author anchors the agent's success condition to a PurchaseOrderNumber in the skill's output rather than an HTTP status code, and reports that the Purchase Requisition item structure does not map one-to-one onto the Purchase Order creation payload.jonathanvi59, published 2026-08-19jonathanvi59, SAP Community
- ARC-1 with Joule Studio: Bringing Real ABAP System Context into JouleARC-1 with Joule Studio: Bringing Real ABAP System Context into JouleBrings the same BTP-deployed ARC-1 endpoint into Joule through a Joule Studio, classic edition agent configured with Anthropic Claude Sonnet 4 and two MCP servers, ARC-1 and mcp-sap-docs, for work that starts in SAP where the previous part started in Microsoft 365. Two read-only showcases carry the ABAP Cloud readiness edge: a clean core check of one class that reports it is not released, uses USR02 and BUT000 directly and has no ATC findings, and a modernisation backlog for package ZSD_LEGACY which, as that package did not exist, grouped 28 ZSD* objects into risk buckets instead. The route through SAP Integration Suite API Management or a future MCP gateway is presented as a target architecture and not yet a productive setup, because Joule Studio's documentation requires streamable HTTP destinations and does not support MCP servers that need interactive OAuth user authorisation.published 2026-05-06Marian Zeis, blog.zeis.de — Marian Zeis
- Building Custom Joule Skills via RFC: Guide for SAP S/4HANA and ECC IntegrationBuilding Custom Joule Skills via RFC: Guide for SAP S/4HANA and ECC IntegrationWalks a Joule skill from a spoken question about a production order's status to an answer in SAP Build Workzone: a Cloud Connector tunnel and a destination in the BTP cockpit reach the S/4HANA or ECC system, a BAPI/RFC Action Project in SAP Build wraps the BAPI that reads the order, and Joule Studio, classic edition turns the action into a skill and deploys it. Establishing the connection and its destination before the action project exists is RFC connectivity and Destinations done for a low-code consumer rather than a CAP service. The action type here is BAPI/RFC, alongside the OData actions Joule Studio's own entry names.Robin-Qiu, published 2026-04-01Robin-Qiu, SAP Community
5 more
- Integrating and Extending JouleIntegrating and Extending JouleSAP's reference architecture for SAP Joule across SAP cloud applications: a request is checked against a Scenario Catalog of the applications' skills and a Knowledge Catalog answered by retrieval-augmented generation, combined with the user's roles and history, sent to an LLM available through the generative AI hub, and, where a Joule function is needed, turned into a call to the backend. Its identity page is the authentication path: each user sits in the Identity Directory of Cloud Identity Services with a Global User ID, Identity Provisioning synchronises role assignments into SAP Build Work Zone, whose navigation service decides which functions a user may call, and the Destination service exchanges the user's token to call a function in the user's name. Its extension page covers Joule Studio in SAP Build, where Joule skills automate rule-based tasks over APIs and AI agents plan and reason with models and document grounding from SAP AI Core, the ground agent tooling covers; a later Joule Studio page describes a managed Joule Studio Runtime on the SAP Business AI Platform, which has no entry here.published 2026-03-16SAP Architecture Center, SAP Architecture Center
- Custom Joule SkillsCustom Joule SkillsA custom Joule skill is a workflow written to extend what Joule does out of the box for one specific business need, built and deployed through Joule Studio in SAP Build; the page states this is the supported way to extend Joule's built-in capabilities. Through Joule Studio a skill reaches SAP and external APIs via the destinations already configured in the BTP subaccount and Build environment, with the workflow itself versioned, monitored and deployable from the same tool.SAP, SAP BTP AI Best Practices
- Content-based Agents with SAP Joule Studio Agent BuilderContent-based Agents with SAP Joule Studio Agent BuilderJoule Studio, classic edition, the capability in SAP Build the page calls Joule Studio, is where an organisation creates and manages its own Joule skills and Joule agents; its Agent Builder is for a custom agent that handles a multi-step task by combining instructions, model-backed planning and reasoning, and a configured set of tools, Joule skills, document resources, MCP servers, or other agents run as subagents. The page states an agent executes inside the calling user's own security context through SAP Cloud Identity Services, and can be tried against a test conversation before deployment. That is the tool-and-turn-taking ground agent tooling covers, here built through Joule Studio rather than in application code.SAP, SAP BTP AI Best Practices
- Building enterprise agent extensions with the Joule Studio solutionBuilding enterprise agent extensions with the Joule Studio solutionExtending SAP's standard agents with third-party integrations and business actions in Joule Studio: agents that run a process across systems, call an external service, put an approval step in the middle and bring the result back into the business context, which is what SAP Joule's agents do and what Joule Studio, classic edition is in the atlas. The abstract names Joule Studio without saying which edition the exercise uses, and lists outcomes rather than the steps built. A TechEd 2026 hands-on session (Wednesday 28 October, Berlin), presented by Charan Ravikumar, Jacob Hornberger, Maria Kondratyeva and Michael Zadikowitsch, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
- Connecting AI agents to the ABAP RESTful application programming modelConnecting AI agents to the ABAP RESTful application programming modelJoule Studio, classic edition connects Joule Agents to applications built with the ABAP RESTful application programming model through actions and skills, calling the OData services those applications expose their business objects through: the tools an agent may call, which is the agent tooling concern seen from the ABAP side. The abstract promises alternative integration patterns and does not name them. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Leon Karlau, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
What changed
- vagent builder, generally available 2025-12-19
Before this, Joule Studio built skills: deterministic flows over actions. The agent builder added agents, with a model choice, sub-agents as tools, document grounding, and MCP servers connected through destinations.
Makes stale:Guidance that Joule Studio builds skills only, or that connecting a Joule agent to an MCP server needs the new Joule Studio.
What’s New
from SAP Help Portal, readhelp.sap.com/whats-new, Joule Studio, classic editionSAP’s wordsOn SAP Help Portal
10 entries from to , counted per month.
New Test Experience for Joule Agents
Query Parameters for MCP Servers
Additional Outputs for Actions
Add Tools via Vibe Coding
Agent Orchestration Configuration
ProcessAutomationParticipant Role Added
Automatic Date Formatting Enabled for Joule Skill Messages
Markdown Enabled for Joule Skill Messages
Human-in-the-Loop Confirmation for Joule Skills in Joule Agents
New Action Buttons for Messages
Others providing
Compare all 14 on the Agent tooling page →Agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed
- a2a-plugina2a-pluginExposes an annotated CDS service as an Agent-to-Agent protocol agent — @a2a opts the service in, @a2a.Skill declares what it offers, and an agent handler answers.independent, capExposes an annotated CDS service as an Agent-to-Agent agent
- com.sap.cds:cds-adapter-agentcom.sap.cds:cds-adapter-agentThe A2A agent adapter for CAP Java, turning an @agent-annotated Application Service into a conversational endpoint whose queries and unbound actions become tools for a configured LLM.sap official, capA2A adapter turning a CAP Java service into an LLM-backed agent
- @cap-js/agents@cap-js/agentsSAP's own CDS plugin for building agents inside a CAP service, wired to audit logging and telemetry through peer dependencies rather than leaving observability to the author.sap official, capCDS plugin for building agents inside a CAP service
- cap-agent-ui5-webuicap-agent-ui5-webuiGives a CAP agent a UI5 web interface out of the box, so an agent built in the service has somewhere to be talked to without a separate frontend project.independent, capUI5 web interface for an agent built in a CAP service
- @mi8y/cap-agents-memory@mi8y/cap-agents-memoryA LangGraph Store written against CDS: the facts and preferences an agent keeps between sessions are entities in the CAP database, read and written inside a request handler under its tenant.independent, capLangGraph Store keeping agent memory as CDS entities
- @mi8y/cap-agents-sdm-backend@mi8y/cap-agents-sdm-backendA Deep Agents filesystem backend whose files are documents in an SAP Document Management repository, so what a CAP agent reads and writes stays where people can open it too.independent, capDeep Agents filesystem over an SAP Document Management repository
- @mi8y/cds-langgraph-persistence@mi8y/cds-langgraph-persistenceA LangGraph checkpointer backed by CDS, so an agent's state survives the request that created it — durability for LangChain and LangGraph agents running inside the CAP Node.js runtime.independent, capLangGraph checkpointer backed by CDS for CAP agents
- cds-agentscds-agentsTurns a CAP service into a tool layer for agent frameworks — a CAPToolkit bound to a named service, with a tool strategy controlling how much of it becomes callable.independent, capToolkit turning a CAP service into tools for agent frameworks
- @sap/joule-studio-cli@sap/joule-studio-cliSAP’s CLI package for both legacy Joule digital assistants and the new Joule Studio solution workflow, through the joule and jl commands.sap official, btpCLI for Joule digital assistants and Joule Studio solutions
- Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrellaSAP's managed environment for building custom agents and workflows
- @sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersjl, the pro-code CLI of the new Joule Studio: a solution is a folder with a solution.yaml and typed assets, validated, built into a zip and deployed to Joule Studio's managed runtime, with Claude Code or OpenCode wired in over MCP. Early Adopter Care.sap official, btpPro-code CLI for building and deploying Joule Studio solutions
- SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btpSAP's AI engagement layer across SAP applications
- @saptarishi/cds-plugin-llm@saptarishi/cds-plugin-llmA CAP service kind that puts eleven model providers behind one chat, stream, embed and batch interface, so which backend a service calls is a profile in package.json rather than a change to the handler.independent, capCAP service kind putting eleven model providers behind one API
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, ai-and-agents
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-joule-studio-classic- JSON
- /artifacts/sap-joule-studio-classic.json
- MCP
- Connecting an agent