This Blog is Part 1 of a Blog Series (4 Parts!). Click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise – Blog Series.
POV 1: Create Custom Agents in SAP
If your business requirements cannot be fulfilled with the out-of-the-box SAP Joule Agents and you wish to use SAP data for your custom agent, then SAP Build’s Joule Studio Agent Builder is the recommended solution.
In Joule Studio Agent Builder, you can use no-code/low-code as well as natural language prompting (through embedded Vibe Coding) to create custom Joule skills and Joule Agents. As a reminder, Joule skills are deterministic meaning they will be able to complete a specific task relatively quickly. Joule agents, on the other hand, reason and problem solve across multi-step scenarios within a defined business domain.
Image taken from Joule Studio Agent Builder; showcasing embedded Vibe Coding used to create a custom Restocking Agent. Source
Why would you want to create SAP agents within SAP?
SAP knows SAP best – Joule is the agent orchestrator that allows it to be proactive and is deeply connected to business context and deep domain knowledge. SAP’s business context is the “magic” of joule that helps determine the sequence and which agents or tools to use. SAP Agents will always have the business context to understand what is being asked of them and how to answer, therefore resulting in more reliable and relevant responses.Controlled Enterprise-wide Governance – Joule is strictly role based. Meaning it is tightly integrated across the SAP security landscape through BTP’s Cloud Identity Service (CIS) – which manages user authentication and access between your apps and Joule. For example, if Joe with US specific Finance roles & authorizations (R&A) is given access to a custom agent containing world-wide Finance info, Joe will only see financial data/information relevant to the US as per his assigned R&A. Similarly, Joe will be able to prompt Joule regardless of the SAP cloud application, if he has access. For example, if he has access to S/4HANA Cloud, SuccessFactors, and Work Zone – he will be able to use any app’s Joule interface to prompt it. Joule’s security landscape results in responsible responses across the SAP landscape. Please see the Architecture Diagram for detailed architecture of Joule Studio and CIS.Connect non-SAP data – Joule allows you to connect non-SAP data sources using APIs, as well as grounded external/internal documents allowing you to blend non-SAP and SAP data with your grounded policies and documentation.
In short, creating an SAP Agent outside of SAP will result in additional effort to rebuild business context and security.
Next POV?
To check out Part 2 of the Blog Series click: POV 2 – Agent to Agent Collaboration with SAP and non-SAP Agents.
Or click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise – Blog Series.
Source: Blog by Michael on Joule Agent Builder
Source: Blog by Amit Bangora on Joule Skill Build
This Blog is Part 1 of a Blog Series (4 Parts!). Click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise – Blog Series.POV 1: Create Custom Agents in SAPIf your business requirements cannot be fulfilled with the out-of-the-box SAP Joule Agents and you wish to use SAP data for your custom agent, then SAP Build’s Joule Studio Agent Builder is the recommended solution.In Joule Studio Agent Builder, you can use no-code/low-code as well as natural language prompting (through embedded Vibe Coding) to create custom Joule skills and Joule Agents. As a reminder, Joule skills are deterministic meaning they will be able to complete a specific task relatively quickly. Joule agents, on the other hand, reason and problem solve across multi-step scenarios within a defined business domain.Image taken from Joule Studio Agent Builder; showcasing embedded Vibe Coding used to create a custom Restocking Agent. SourceWhy would you want to create SAP agents within SAP?SAP knows SAP best – Joule is the agent orchestrator that allows it to be proactive and is deeply connected to business context and deep domain knowledge. SAP’s business context is the “magic” of joule that helps determine the sequence and which agents or tools to use. SAP Agents will always have the business context to understand what is being asked of them and how to answer, therefore resulting in more reliable and relevant responses.Controlled Enterprise-wide Governance – Joule is strictly role based. Meaning it is tightly integrated across the SAP security landscape through BTP’s Cloud Identity Service (CIS) – which manages user authentication and access between your apps and Joule. For example, if Joe with US specific Finance roles & authorizations (R&A) is given access to a custom agent containing world-wide Finance info, Joe will only see financial data/information relevant to the US as per his assigned R&A. Similarly, Joe will be able to prompt Joule regardless of the SAP cloud application, if he has access. For example, if he has access to S/4HANA Cloud, SuccessFactors, and Work Zone – he will be able to use any app’s Joule interface to prompt it. Joule’s security landscape results in responsible responses across the SAP landscape. Please see the Architecture Diagram for detailed architecture of Joule Studio and CIS.Connect non-SAP data – Joule allows you to connect non-SAP data sources using APIs, as well as grounded external/internal documents allowing you to blend non-SAP and SAP data with your grounded policies and documentation.In short, creating an SAP Agent outside of SAP will result in additional effort to rebuild business context and security.Next POV?To check out Part 2 of the Blog Series click: POV 2 – Agent to Agent Collaboration with SAP and non-SAP Agents.Or click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise – Blog Series. Source: Blog by Michael on Joule Agent BuilderSource: Blog by Amit Bangora on Joule Skill Build Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
