Two Buyers, One Question, Two Different Answers
Ravi is an SAP MM consultant leading a Joule pilot for a mid-size distributor. (Ravi is a fictional example based on a common project situation.)
It is demo day. Two buyers sit side by side in front of the same SAP system. Both open Joule. Both type the same question:
"Show me my purchase orders that are waiting for approval."
The first buyer gets a neat list in seconds, with links to open each order.
The second buyer gets a polite reply saying Joule cannot help with that request.
The room goes quiet. The procurement head turns to Ravi and asks the question every consultant dreads in a demo: "Why does it work for her and not for him?"
Ravi knows Joule is SAP's AI copilot. He has watched SAP's videos. But in that moment, he cannot explain what actually happens between the question and the answer. So he cannot say where it broke.
This article fixes that. You will see the 7 steps that run behind the screen every time someone asks SAP Joule a question , explained in plain language. You will also get a troubleshooting table you can use on real projects and a 60-second way to explain it all to a client.
At a glance
Why "Behind the Screen" Knowledge Matters for Consultants
Consultants who understand how Joule processes a request can design it, troubleshoot it and explain it, which is what clients pay for.
To a business user, Joule looks simple: type a question, get an answer. That simplicity is the point. But a lot of SAP technology has to work together to make it feel that way, and every piece is something a consultant may be asked to configure, test or explain.
Clients ask three questions about Joule more than any others: Can we trust the answer? Is our data safe? Why does it behave differently for different users? All three are answered by the same 7 steps.
The description below is based on SAP's reference architecture for integrating and extending Joule and SAP Learning's material on Joule core capabilities . We have simplified the technical names so the flow is easy to follow. Exact behavior differs by SAP product and release.
The 7 Steps at a Glance
Every Joule request follows the same path: ask, identity check, context, choose a path, get the facts, write the answer, deliver it.
How SAP Joule handles one question ยท 7 steps
The identity check is highlighted because it shapes everything after it. Each step is explained below.
Step 1: You Ask a Question in Plain Language
Every Joule interaction starts in the Joule client, the chat panel built into supported SAP cloud applications.
SAP groups what Joule can do into four types of capability. Knowing which type a question belongs to is the first thing a consultant should check, because each type follows a slightly different path behind the screen.
Source: SAP Learning, Introducing SAP Joule Core Capabilities . Available capabilities depend on the SAP product, release and license.
Step 2: Joule Checks Who You Are and What You May See
Before Joule does anything with your question, it confirms your identity and your permissions.
This is the step most people forget, and the one that explains Ravi's demo. According to SAP's reference architecture , SAP Cloud Identity Services handles authentication and authorization for Joule, and Joule enforces the same role-based permissions the user has in the SAP application itself.
In simple terms: Joule can never show you more than you could see by opening the app yourself. If a buyer is not allowed to approve purchase orders in SAP, Joule will not let them do it through a chat either.
Consultant tip: when you prepare a Joule demo, test it with the exact users and roles that will be in the room, not with an administrator account that can see everything.
Step 3: Joule Reads the Context Around Your Question
Joule does not look at your question alone. It also considers who you are, what you asked earlier and which SAP applications your company uses.
SAP's reference architecture describes a context layer inside the Joule service on SAP BTP. It keeps track of:
This is why the same question can lead to different, but correct, answers for a buyer and a finance manager. It is also why Joule will not suggest an SAP Ariba feature to a company that does not use SAP Ariba.
Step 4: Joule Picks the Right Skill, Agent or Knowledge Source
With the question and the context in hand, Joule decides how to respond: answer from knowledge, open an app, run a business function or hand the work to an agent.
Behind the scenes, the Joule service checks two catalogs:
Source: SAP Architecture Center, Integrating and Extending Joule .
For example, "What is a sales order without charge?" points to the knowledge catalog. "Show my purchase orders waiting for approval" points to a transactional scenario in the scenario catalog.
This step is also where custom work plugs in. Using Joule Studio , customers and partners can build their own skills and agents. Once deployed, they become new options Joule can choose from, alongside SAP's own.
Why this matters: if Joule says it cannot help, it often means no matching skill or scenario exists for that request in that product. The fix may be a different phrasing, a different app or a custom skill, not "better AI".
Step 5: Joule Fetches Business Data or Trusted Knowledge
Joule grounds its response in real sources: your SAP business data for transactional and analytical requests, and curated documents for knowledge questions.
For business data , Joule calls the relevant SAP back-end system, such as SAP S/4HANA Cloud, SAP SuccessFactors or SAP Ariba, through SAP's connectivity and destination services. The call runs with the user's own permissions, so the identity check from step 2 still applies.
For knowledge , Joule uses SAP documentation and, if the company sets it up, the company's own documents. SAP calls this document grounding. A company could, for example, ground Joule in its internal procurement policy, so "What is our approval limit for IT purchases?" gets an answer from the company's own rules.
Step 6: The AI Model Writes the Response, Within Guardrails
A large language model manages the conversation and turns the facts into a clear answer, but it works inside SAP's safeguards.
According to SAP's reference architecture , the large language model handles dialog management. SAP draws on models from technology partners, also available through the AI Foundation on SAP BTP.
Three safeguards are worth explaining to every client:
Plain-language version for clients: the AI model is the writer, not the source. The facts come from your SAP system and approved documents, and your permissions decide what it can see.
Step 7: Joule Filters the Response and Hands It Back to You
The response is checked one last time, then delivered in the format that fits the request, and you stay in control of any action.
The human check
For actions that change business data, the user is the final decision maker. Joule proposes; the person confirms. This is not only good practice, it is also how you should design and train for Joule on every project:
That is the full journey: one question, seven steps, usually in a few seconds.
When Joule Does Not Answer: A Step-by-Step Troubleshooting Table
Most Joule problems on projects trace back to one of the 7 steps, and the step tells you where to look first.
Use this table in testing, in hypercare and in your next demo rehearsal.
Alt text: Seven-step SAP Joule troubleshooting guide showing symptoms, likely causes and first checks.
For detailed setup and support steps, always follow the current SAP Help Portal guide for your product, because configuration differs between SAP S/4HANA Cloud Public Edition, Private Edition and other applications.
How to Explain the 7 Steps to a Client in 60 Seconds
A short, honest explanation of how Joule works builds more trust in a workshop than any demo.
Here is a script you can adapt. Read it aloud once, then say it in your own words.
"When you ask Joule a question, it first checks who you are, so you only ever see what your SAP role allows. It looks at your context, like your role and what you asked before. Then it decides whether you need an explanation, an app, your business data or an action. It gets the facts from your SAP system or from approved documents. An AI model turns those facts into a clear answer, within SAP's safeguards, and SAP states that its model partners may not train on your data. Finally, Joule shows you the answer, and for any change to your data, you confirm it first."
That is about 100 words, roughly 45 to 60 seconds when spoken.
Three follow-up questions to prepare for
Consultants who can explain the flow clearly are well placed to lead the Joule conversation on their projects.
Free SAP Joule Resources From the SAP Learner Community
The SAP Learner Community on LinkedIn, run by ZaranTech, shares free SAP Joule and SAP AI resources every week. These go deeper on the steps above:
Follow the SAP Learner Community for new Joule resources every week.
Back to Ravi's Demo
After the demo, Ravi walks through the 7 steps with the second buyer's user account. Step 1 is fine: Joule opens. At step 2, he finds the answer. The second buyer's user is missing the role that allows purchase order approval, so Joule correctly refuses to show the list.
The next day, the role is added, and the same question returns the same list for both buyers. More importantly, the procurement head now trusts Joule more, not less, because she has seen that it respects SAP's permissions exactly.
That is the value of understanding what happens behind the screen. You stop guessing, and you start explaining.
Learn SAP Joule hands-on, with an expert instructor
ZaranTech's live SAP Joule training (24 hours) helps you understand how Joule works, practice real scenarios and explain Joule confidently to clients. To go further into Joule Studio, SAP AI Core, Generative AI Hub and AI agents, explore the ZaranTech SAP AI Masterclass , a 40-hour live program with 24+ hands-on labs.
About ZaranTech
ZaranTech offers live instructor-led, self-paced and corporate training in SAP, Workday, AI and enterprise technologies, with 400+ courses, 32,000+ learners trained, 350+ corporate clients and learners in 37+ countries.
Related Reads
Sources
Checked on 5 Oct 2026. Joule behavior and setup differ by SAP product and release.