This blog outlines the basic features of SAP JOULE Agent setup for validating EHS Incident location, and creating EHS Incident, and retrieving EHS Incidents summary. I have leveraged SAP JOULE`s low-code and no-code capabilities to build an impactful solution.
“A near miss reported today is an accident prevented tomorrow”…
If you want to gain a nuanced understanding of the Joule Skill and Process Automation setup, use the link below:
- SAP JOULE & ME : My First JOULE Skill in SAP EHSM-Incident Management Without Coding
- SAP Joule Skill for Technical Completion of Maintenance Orders in S/4HANA Asset Management
- SAP Build Process Automation(SBPA):S4HANA Asset Management-Automating Major Maintenance Work Request
What`s the difference between a Joule skill and Joule Agent?:
- Joule Skill: It executes predefined and repetitive single operations with known inputs and outputs.
- Joule Agent: It focuses on problem solving with multi-step complex strategy.
(In my view, JOULE Skill is like a hand that executes what it is told, and JOULE Agent is like a brain that decides which skill to be used, in what order, and under what conditions.)
Pre-requisites for a Joule Agent:
- Joule Skills that will be used in the Agent.
Joule Agent Blueprint:
Joule agent`s behavior is driven by a prompt. Post receiving the prompt, the agent goes through the set of instructions, context, and tool definitions that joule studio has assembled , and empowers the LLMs(Large Language Models) to automate the tasks and drives business outcomes. The clarity of the prompt is the most critical factor in determining the Joule Agent`s reliability and performance. The key components of Joule Agent are:
- Expertise: It defines agent`s role.
- Instructions: It specifies the agent`s primary and non-negotiable task.
- Additional Context: It specifies rules and conditional logic.
- Tool Descriptions: Defines the available tools and acts as the agent`s manual for its capabilities.
Key Principles for the Agent setup:
- Define a clear goal and the required steps to reach it.
- We must break the complex rules into simple, ordered lists.
- We must ensure that every step leads to a clear action.
- Avoid ambiguity.
- Grant access to the required tools for the agent`s job.
- We must maintain the consistency in the instructions.
Exception Management: Joule Agents are designed for complex tasks, which means they need to be tested and validated carefully. Results are not always the same for the same input and behavior can vary depending on the model and configuration. Building a reliable agent usually take a few iterations, with clear instructions, well-scoped inputs, and the right tools. Agent`s don`t think like humans, and in some cases a joule skill may be a better fit. So it`s important to understand when to use each.
My Business Use Case:
Our organization`s policy is that every employee can report an EHS Incident (Incident, Near Miss, Safety Observation). To support this, we have setup seamless integration between SAP Asset Management and SAP EHSM modules.
Each equipment is treated as an EHS Location and is assigned with a unique “Technical Identification Number”. Our employees typically recognize the equipment by this technical ID, rather than the SAP Equipment Code (Internal Number), which is harder to remember. So, our EHS Incident Agent helps employees in creating an EHS Incident by retrieving and validating the EHS Location ID linked to the Equipment by using the Equipment Technical Identification Number.
Come on in…let us experience the SAP Joule Agent`s capabilities, It really is the bee`s knees…
To achieve my business use case, I have created two Joule Agents, one agent is responsible for retrieving the EHS location that is integrated with an Equipment, and the second agent is responsible for creating an EHS Incident.
Joule Skills mentioned below are wrapped in for an EHS Incident Agent to retrieve EHS Location integrated with an Equipment.
Joule Skills mentioned below are wrapped in for an EHS Incident Agent for creating an EHS Incident using user`s natural language prompt.
Let us setup Joule Agents : EHS Incident Location Identifier Agent and EHS Incident Creation Agent.
For Instance, I have chosen LLM Provider as “Anthropic” and Planning Model & Response Model as “Claude Sonnet 4”.
Assign the required Joule Skills under “Tools” tab:
Mini Note: While assigning the Joule Skills, we must consider that, the more tools an agent has, the more complex its decision-making becomes. This can lead to wrong tool choices, slower performance. The bad practice is granting an agent access to all the available tools. A good practice is granting agent access only to the specific tools it needs to perform its job.
EHS Incident Creation Joule Agent:
Once the Joule Agent setup is done, we can test the agent capability using the option “Test” and release and deploy in the respective environment. For Instance, I have created a private environment for testing my Joule Agent. Let us test the Joule agent capabilities.
Let us first retrieve the EHS Incident details:
Let us create an EHS Incident.
Mini Note: Since the OData demands the date in the UTC format, I have Instructed the agent to consider the current date and time in UTC format if user does not input the date.
Once we are satisfied with the Joule Agent behaviour, we can deploy the Joule Agent. For Instance, I have deployed my Joule Agents in the “Asset Management Environment”.
Let us launch the “Joule”.
Let us check the Incident in the EHSM-Incident Management using Manage Incident Application.
Now let us retrieve the EHS Incident details.
As part of my instructions, my Joule Agent will prompt user to provide the date range for the retrieval process.
Once user provides the date range, Joule Agent fetches the details and displays the summary by Incident category.
Key Takeaways:
- Separate Joule Agents by clear responsibilities. For Example: Retrieving EHS Incident Location ID details and Creating an EHS Incident.
- Keep Joule Agents lean and specialized for better performance.
- Overloading Joule Agent with more Joule Skills can increase complexity , bring decision making capability down, reduces reliability.
Mini Note:
If you want to launch these two agents quickly or want to try them in your own landscape, they are officially available on SAP Business Accelerator Hub. You can access these pre-built templates to fast-track your setup.
SAP Sapphire 2026 Innovation Guide:
The biggest takeaway from SAP Sapphire 2026 is , Joule has officially evolved from a simple text chatbot into a comprehensive orchestration layer for complex business processes. SAP is introducing a unified, intent-driven ecosystem with JOULE WORK.
Please check the link below for a deep dive into the Joule Work at SAP Sapphire 2026…
Meet Joule: The future of work
&
If you want to gain knowledge on the seamless integration of EHSM Locations and Asset Management, checkout my blog post link below.
SAP S/4HANA EHS : Environment Management (Emissions Management) – Part:1 (Master Data Entities)
😊This brings me to the end of the SAP Joule Agent setup process walkthrough. I hope my blog post proves helpful for the SAP functional consultants begin their journey with the SAP Joule Agents using Low Code – No Code strategy.
Stay tuned for more updates on SAP Joule Agents in Asset Management and EHSM space…
—
Yours Sincerely,
Pardhasaradhi Reddy. Chelikam
#abap