Introduction
As SAP continues to roll out Joule integrations across multiple LoBs, with stronger and wider SAP and non-SAP ecosystem bringing the powerful AI-driven assistance, Agents, Agents to Agents, and many more functionalise to our business users. To ensure these functionalities run smoothly, every organization requires the right administrative setup and awareness of key configurations; at the same time it becomes increasingly important to understand how to manage, troubleshoot, understand the consumption patterns in your organisation with most frequently used questions driving your organizational process are some of the key features, and enhance the digital assistant’s functionality efficiently.
This blog aims to help administrators and support colleagues navigate the essential aspects of managing Joule service within an SAP Business Technology Platform environment. It walks through the available roles and role collections, their purposes, and how to configure them effectively.
The blog also focuses on troubleshooting best practices — highlighting the common checks, logs, and details that SAP Support typically requests during issue resolution. By following these guidelines, you can resolve common problems faster, share the right information upfront, and reduce back-and-forth communication with SAP.
Ultimately, this guide aims to make your Joule operations more efficient, your issue-handling more structured, and your collaboration with SAP smoother and quicker.
Before we get started, it’s important to understand the overall Joule integration for your organization. Please look at the blogs below:
This blog post is a series for Joule Activation:
SAP Business AI – Overview for all !!! (Includes information on Joule Supported Data Centers, Different scenarios during Joule setup, etc..)Joule – Unified Setup: Bridging Simplicity and Performance (Demo Video to understand the Unified Setup, Joule basics & architecture, how to set up Joule, etc…) Joule for SAP S/4HANA Cloud Private Edition – A Comprehensive Setup GuideJoule Setup – End-to-End Setup Guide (for all Line of Business) Unified Approach Joule for SAP S/4HANA Cloud Public Edition – Setup GuideSAP Digital Supply ChainJoule for SAP Integrated Business Planning (SAP IBP) – Setup GuideJoule Setup for SAP Integrated Product DevelopmentJoule – Getting Started with Document Grounding – setup guideActivate Joule with SAP Build Work Zone and SAP Mobile StartAnalytical InsightsAnalytical Insights in Joule – Setup GuideJoule Integration with SAP Ariba – Setup GuideJoule Integration with SAP Concur – Setup GuideJoule integration with SAP Signavio Process Transformation Suite – Setup Guide
👉Managing Joule on SAP BTP: Roles, Analytics, Administration and Troubleshooting – you are here
Blogs – Work in Progress (WIP):
SAP Digital Supply Chain (WIP)SAP Asset Performance ManagementSAP Product Lifecycle ManagementSAP Digital Manufacturingand more to be added towards General Availability
****************************************************************************
This blog explains the key features and administration aspects of Joule on SAP BTP.
Joule FeaturesDownloading traces for debugging and SAP supportConversation search across chat historyVersion details, support components, and personalization settingsRoles and Access ManagementAvailable Joule roles in SAP BTPCreating and managing role collectionsAssigning roles to users and user groupsEnd User accessTenant Admin and Joule Admin CenterExtensibility Developer capabilitiesAdmin and Analytics InterfacesJoule Analytics Center for usage statistics and trendsConversation History FAQsActive and expired conversationsRetention limits and lifecycle behaviour
Disclaimer:
This blog is meant to provide a general understanding and practical guidance for working with SAP Joule based on common scenarios. For detailed and up-to-date information, please always refer to the Joule | SAP Help Portal.
1. General Features – Download Traces, Conversation Search, etc.
1. 1 Download Traces
One of the important things to make note of is that one can download traces which can be attached in case of any errors/support required from the team. This option enables the user to be quick in providing the information for debugging which would be required by the SAP Support teams. To download traces, just click on Settings, in the pop-up, go to About and click Download Traces.
Image 1
Another pop-up will come, where you can choose whether to include message history in the trace files. Once done, click on Download and you’ll have a .zip file downloaded. This file can be attached in the support ticket created to SAP in case of any errors faced while using Joule.
Image 2
The file downloaded can contain the following details
Joule version and environment details.UI Logs and the most recent 5-10 HTTP requests.Correlation IDs for the last 5-10 messages that can be used by SAP to fetch additional details logged by SAP.Message history as a JSON file (included only based on user consent).
Find the support Components to which the ticket has to be created for specific joule issues in the below table.
CA-JOULE
Joule
CA-JOULE-CI
Joule Conversation Logging and Insights
CA-JOULE-CLI
Command Line Interface tool
CA-JOULE-CLT
Joule Messaging Client-related topics
CA-JOULE-CLT-COP
Specific for Joule x Copilot Integration
CA-JOULE-COMP
Joule Compiler
CA-JOULE-CONSULT
Joule Consulting
CA-JOULE-CR
Joule Conversational Runtime
CA-JOULE-PRV || CA-JOULE-PRV-INT
Provisioning & Integrations with applications
CA-JOULE-TA
Tenant Administration – Joule Content Deployment related issues
CA-JOULE-TR || CA-JOULE-PRV-ONB
Tenant Runtime (Bot-runtime), Joule Subscription, SPR, TO and Approuter issues
BC-CP-MP-FOR
Unified Customer Landscape (UCL)
BC-IAM-IDS
IAS
For further information, you can refer to the help portal – Monitoring and Troubleshooting | SAP Help Portal.
1.2 Conversation Search
Conversation search allows users to quickly find past conversations (including expired conversations) from their history.
From the side navigation panel, click on the search icon to access conversation search.
Image 3
Enter one or more keywords to search across your conversations.
Image 4
Search results are dynamically updated as you type. Matching strings are highlighted in the results obtained from the search. The results returned include both the conversations where the title may contain the search term as well as those where the search term is found in any of the messages in the conversation. Selecting a search result navigates you directly to the matched conversation and message.
1.3 Other features
User can also check the version of Joule and the Support Component to raise tickets for Joule in Setting > About.
Image 5
In Settings > Personalization, you can choose to disable streaming and whether to turn off animations.
Image 6
2. Joule Roles
Prerequisite: You should be a subaccount admin.
As an administrator, you’ll be able to view the available roles and role collections in your subaccount. Open the SAP BTP Cockpit and go to your global account and subaccount.
Choose Security > RolesSearch for “das” in the search bar.You’ll see the list of the available roles for Joule under the Application Name das-application
Image 7
2.1 Create Role Collections, Assign Roles and Users
In order to assign the roles to users or user groups, we need to first add them into role collections as these roles are not part of any collection and cannot be assigned to users unless we create the collection. To create a role collection (screenshot attached),
Go to Security > Role CollectionsClick on Create, enter a name for the role collection and click Create.
Tip: You can decide to create one common role collection for all Joule roles and assign them together or create separate role collection in case you want have better controls and maintain it individually.
Image 8
The new role collection will get listed in the page, now select the created role collection, and click on Edit.
Image 9
Now, under Roles, click on the textbox, a pop-up will appear.
Image 10
Search for “das-application” in Application Identifier. Select the appropriate option. You’ll see the Joule roles listed. Select the ones which must be added and click on Add.
Image 11
This helps us to create the Role collections which now can be assigned to the users.
To assign users, go to the users section under the role collection, enter the email-id and select appropriate identity provider. Now you can Save the role collection.
Image 12
Now let’s go to our joule and see what options are available as a user with the role “End User”.
2.1.1 End User (end_user)
This is the role which gives the user access to the standalone URL of your Joule tenant. For more on using the joule web client, refer Using the Joule Web Client | SAP Help Portal.
2.1.2 Tenant Admin (tenant_admin)
As a tenant admin, you can access the Joule Admin Center – a tenant specific user interface, offered for customizing respective Joule configurations. You can find more information here – Joule Admin Center | SAP Help Portal.
To access the Joule Admin Center:
Go to the BTP Cockpit and open your subaccount having Joule. Go to Subaccount Overview > Instances and Subscriptions.
Expand the Joule application subscription (das-application). Click Go to Application to fetch the Joule application URL.
Image 13
Get the Joule tenant URL and append “/admin” to form the admin center URL for the respective Joule tenant – <Joule tenant URL>/admin.
Image 14
You’ll get the below page for Joule Admin Center, given you have the role tenant_admin assigned to your user. Here you can find the list of assistants available in your Joule, and you can select each of them to see their system alias and destinations setup for each.
Image 15
Note: SAP team is actively working to add more details and features to this page, stay tuned for more updates. In your case you may only see the “sap_digital_assistant” with standard Joule integration.
2.1.3 Extensibility Developer (extensibility_developer)
This one is applicable to the customers/partners who would like to use Joule extensibility in your landscape. This role is required to build and deploy capabilities for Joule. For more information, refer Joule Development | SAP Help Portal.
In addition, this role provides Debug option which provides visibility into runtime execution through the Logs View, which helps administrators and developers monitor and troubleshoot custom capabilities effectively.
With this role, users can:
View end-to-end execution logs for Joule conversations.Easily identify execution outcomes using visual status tags (Blue for success, Red for errors).View Correlation IDs to trace requests across the complete conversation and use these as supporting information for issue analysis and support ticket creation.
Use log details as To use the Debug features, open the Joule conversation window, click on the Debug icon on the top right corner. A side window named “Request Logs” will appear, Here you can find the logs and trace the conversation.
Image 16
A side window named “Request Logs” will appear, Here you can find the logs and trace the workflow of the conversation in case you face any error or run into an issue. You can expand the log messages by clicking on the arrow beside the message to find further details.
Image 17
Now, let us see how to fetch the Correlation ID for a conversation in Joule. This ID must be shared with the support team for effective troubleshooting and error tracing.
Open the conversation for which you want to retrieve the Correlation ID. For messages generated by Joule, a debug icon is displayed in the top-right corner of the message. This icon will be blue if the response was generated successfully. In case the request ran into an error, the icon will be red.
Image 18
Click this icon to open a split view titled “Response Payload.” Scroll to the bottom of the payload, where you will find the correlationID field.
Image 19
Share this Correlation ID with the Joule support team to assist with issue investigation and analysis.
Note: For every conversation where Joule is not working as expected or run into any errors, the Joule Support team will be requesting the correlation ID or the conversation trace. Please ensure to have these information attached to the support ticket which you’ll be creating for the issues/troubleshooting.
2.1.4 Analytics Admin (analytics_admin)
Joule offers an analytical insight on the Joule usage with the analytics_admin role. You can find the official help page here – Joule Analytics Center | SAP Help Portal.
Go to the BTP Cockpit and open your subaccount having Joule. Go to Subaccount Overview > Instances and Subscriptions.
Expand the Joule application subscription (das-application). Click Go to Application to fetch the Joule application URL.
Image 20
Get the Joule tenant URL and append “/analytics” to form the Joule Analytics Center URL for the respective Joule tenant (your BTP subaccount) – <Joule tenant URL>/analytics.Image 21
You’ll get the below page of Joule Analytics Center. Click Acknowledge and continue to explore the analytical insights provided.
Image 22
You can view analytics across interaction types, products, scenarios, and client types for a selected time range, providing insights into overall Joule usage, adoption, and engagement.
The Summary section highlights key metrics, including total messages, total conversations, and the average messages per conversation, giving a quick snapshot of overall interaction volume and conversation depth.
Image 23
We have 2 sections, Messages and Conversation – each representing a different level of interaction. A message is an individual request or response generated within Joule and is counted across all conversations. A conversation represents a single, distinct interaction thread initiated by a user, identified by its conversation topic name. Each conversation can contain one or more individual messages exchanged within that thread.
The Messages section breaks down message activity by product, scenario, and interaction type, helping you identify which products and scenarios are most frequently used and how users interact with Joule across different interaction types.
Image 24
The Product Usage graph clearly shows which products are using Joule most actively. From the sample data in the screenshot below, SAP S/4HANA Public Cloud has the highest usage, followed by SuccessFactors and SAP Analytics Cloud / Just Ask, while products such as IBP and IPD show comparatively lower message volumes. This view helps identify where Joule adoption is strongest and enables easy comparison of usage across different products.
Image 25
The Scenario Usage graph shows how frequently different scenarios are used in Joule. From the data, scenarios such as “ESH_U_SALESORDER” and “purchase order–related scenarios” have higher usage. Other scenarios, including employee views, feedback, and scheduling workflows, show comparatively lower usage. This view helps identify the most actively used scenarios and supports prioritization of monitoring and optimization efforts for high-impact workflows.
Image 26
The Interaction Type Usage graph illustrates how users engage with Joule across different interaction types. The data shows that scenario-based interactions account for most of the usage, followed by direct responses and slot filling, while information retrieval and file uploads contribute only a small portion. This view helps understand preferred interaction patterns when interacting with Joule.
Image 27
You can also find weekly statistics of messages and conversations.
The Message Count Over Time graph shows how the total number of messages sent to Joule varies over the selected time range. From the sample view, you can see clear peaks and drops, indicating periods of higher and lower activity. This helps administrators and the organization to identify usage trends, understand peak activity periods, and correlate spikes with specific events, releases, or user activity.
Image 28
The Conversation Count Over Time graph displays how the number of unique conversations changes over time. In the sample screenshot, you can observe days with higher conversation counts, indicating increased user engagement, followed by periods of lower activity. Comparing this graph with the message count helps distinguish between longer conversations and an increase in the number of users or sessions, providing better insight into overall usage behavior.
Image 29
You can also find Product Usage and Scenario usages under the Conversations showing which product/scenario generate the most conversations.
Image 30
Additionally, there is a Client Type Usage graph which shows the number of conversations across different client types, such as Desktop, Mobile, and Copilot, helping you understand how conversations are distributed by access channel.
Image 31
Overall, these graphs make it easy to visually identify where usage is highest, compare adoption across products, scenarios, and interaction types, and gain actionable insights for monitoring and operational analysis.
3. FAQs on Joule Conversation History
Adding, deleting, and renaming conversationsCreate a new conversation by selecting the “New Conversation” option from the side panel menu.
Image 32
When a new conversation is created, a conversation title is automatically generated based on the first user request–response in the conversation thread.You can rename a conversation at any time by hovering over the conversation in the side panel and selecting “Rename” from the conversation menu, or by selecting Rename from the conversation header.
Image 33
To delete a conversation, hover over the conversation in the side panel or open the action menu from the conversation header, then select Delete. A pop-up will appear, confirm by clicking “Delete”
Image 34
Image 35
Active conversationsA maximum of 10 active conversations can be maintained at any time. This helps users keep conversations segregated and organized, for example by using separate conversations for different applications such as SAP S/4HANA and SuccessFactors, or by specific business scenarios like leave requests, travel requests, and other workflows.Conversations are sorted with the most recently active on top.Switch between conversations to continue engaging in a different conversation.
Image 36
Image 37
Expired conversationsA conversation expires after 8 hours of inactivity. Upon expiration you’ll be notified and provided with an option to trigger a new conversation.Conversations are sorted by the creation date of the thread with the newest at the top.Conversations are deleted automatically 7 days after the date of creation.Expired conversations cannot be continued. They can only be referenced for past interaction history.
Image 38
As Joule adoption grows across products and scenarios, effective administration becomes the backbone of a reliable user experience. With a clear understanding of Joule roles, analytics, and troubleshooting tools, administrators can proactively monitor usage, resolve issues faster, and support business users more efficiently.
Credits & Special thanks to RIG Team (Nagesh Caparthy & Naga Swathi T J) for supporting this blog post.
Until the next update — stay tuned and happy learning!!!
Best Regards,
Amrita Varshini E R
SAP Business AI RIG Team
IntroductionAs SAP continues to roll out Joule integrations across multiple LoBs, with stronger and wider SAP and non-SAP ecosystem bringing the powerful AI-driven assistance, Agents, Agents to Agents, and many more functionalise to our business users. To ensure these functionalities run smoothly, every organization requires the right administrative setup and awareness of key configurations; at the same time it becomes increasingly important to understand how to manage, troubleshoot, understand the consumption patterns in your organisation with most frequently used questions driving your organizational process are some of the key features, and enhance the digital assistant’s functionality efficiently.This blog aims to help administrators and support colleagues navigate the essential aspects of managing Joule service within an SAP Business Technology Platform environment. It walks through the available roles and role collections, their purposes, and how to configure them effectively.The blog also focuses on troubleshooting best practices — highlighting the common checks, logs, and details that SAP Support typically requests during issue resolution. By following these guidelines, you can resolve common problems faster, share the right information upfront, and reduce back-and-forth communication with SAP.Ultimately, this guide aims to make your Joule operations more efficient, your issue-handling more structured, and your collaboration with SAP smoother and quicker.Before we get started, it’s important to understand the overall Joule integration for your organization. Please look at the blogs below:This blog post is a series for Joule Activation:SAP Business AI – Overview for all !!! (Includes information on Joule Supported Data Centers, Different scenarios during Joule setup, etc..)Joule – Unified Setup: Bridging Simplicity and Performance (Demo Video to understand the Unified Setup, Joule basics & architecture, how to set up Joule, etc…) Joule for SAP S/4HANA Cloud Private Edition – A Comprehensive Setup GuideJoule Setup – End-to-End Setup Guide (for all Line of Business) Unified Approach Joule for SAP S/4HANA Cloud Public Edition – Setup GuideSAP Digital Supply ChainJoule for SAP Integrated Business Planning (SAP IBP) – Setup GuideJoule Setup for SAP Integrated Product DevelopmentJoule – Getting Started with Document Grounding – setup guideActivate Joule with SAP Build Work Zone and SAP Mobile StartAnalytical InsightsAnalytical Insights in Joule – Setup GuideJoule Integration with SAP Ariba – Setup GuideJoule Integration with SAP Concur – Setup GuideJoule integration with SAP Signavio Process Transformation Suite – Setup Guide 👉Managing Joule on SAP BTP: Roles, Analytics, Administration and Troubleshooting – you are hereBlogs – Work in Progress (WIP):SAP Digital Supply Chain (WIP)SAP Asset Performance ManagementSAP Product Lifecycle ManagementSAP Digital Manufacturingand more to be added towards General Availability****************************************************************************This blog explains the key features and administration aspects of Joule on SAP BTP.Joule FeaturesDownloading traces for debugging and SAP supportConversation search across chat historyVersion details, support components, and personalization settingsRoles and Access ManagementAvailable Joule roles in SAP BTPCreating and managing role collectionsAssigning roles to users and user groupsEnd User accessTenant Admin and Joule Admin CenterExtensibility Developer capabilitiesAdmin and Analytics InterfacesJoule Analytics Center for usage statistics and trendsConversation History FAQsActive and expired conversationsRetention limits and lifecycle behaviourDisclaimer:This blog is meant to provide a general understanding and practical guidance for working with SAP Joule based on common scenarios. For detailed and up-to-date information, please always refer to the Joule | SAP Help Portal.1. General Features – Download Traces, Conversation Search, etc. 1. 1 Download TracesOne of the important things to make note of is that one can download traces which can be attached in case of any errors/support required from the team. This option enables the user to be quick in providing the information for debugging which would be required by the SAP Support teams. To download traces, just click on Settings, in the pop-up, go to About and click Download Traces.Image 1Another pop-up will come, where you can choose whether to include message history in the trace files. Once done, click on Download and you’ll have a .zip file downloaded. This file can be attached in the support ticket created to SAP in case of any errors faced while using Joule.Image 2The file downloaded can contain the following detailsJoule version and environment details.UI Logs and the most recent 5-10 HTTP requests.Correlation IDs for the last 5-10 messages that can be used by SAP to fetch additional details logged by SAP.Message history as a JSON file (included only based on user consent).Find the support Components to which the ticket has to be created for specific joule issues in the below table.CA-JOULEJouleCA-JOULE-CIJoule Conversation Logging and InsightsCA-JOULE-CLICommand Line Interface toolCA-JOULE-CLTJoule Messaging Client-related topicsCA-JOULE-CLT-COPSpecific for Joule x Copilot IntegrationCA-JOULE-COMPJoule CompilerCA-JOULE-CONSULTJoule ConsultingCA-JOULE-CRJoule Conversational RuntimeCA-JOULE-PRV || CA-JOULE-PRV-INTProvisioning & Integrations with applicationsCA-JOULE-TATenant Administration – Joule Content Deployment related issuesCA-JOULE-TR || CA-JOULE-PRV-ONBTenant Runtime (Bot-runtime), Joule Subscription, SPR, TO and Approuter issuesBC-CP-MP-FORUnified Customer Landscape (UCL)BC-IAM-IDSIASFor further information, you can refer to the help portal – Monitoring and Troubleshooting | SAP Help Portal.1.2 Conversation SearchConversation search allows users to quickly find past conversations (including expired conversations) from their history.From the side navigation panel, click on the search icon to access conversation search.Image 3Enter one or more keywords to search across your conversations.Image 4Search results are dynamically updated as you type. Matching strings are highlighted in the results obtained from the search. The results returned include both the conversations where the title may contain the search term as well as those where the search term is found in any of the messages in the conversation. Selecting a search result navigates you directly to the matched conversation and message. 1.3 Other featuresUser can also check the version of Joule and the Support Component to raise tickets for Joule in Setting > About.Image 5In Settings > Personalization, you can choose to disable streaming and whether to turn off animations.Image 62. Joule RolesPrerequisite: You should be a subaccount admin.As an administrator, you’ll be able to view the available roles and role collections in your subaccount. Open the SAP BTP Cockpit and go to your global account and subaccount.Choose Security > RolesSearch for “das” in the search bar.You’ll see the list of the available roles for Joule under the Application Name das-applicationImage 72.1 Create Role Collections, Assign Roles and UsersIn order to assign the roles to users or user groups, we need to first add them into role collections as these roles are not part of any collection and cannot be assigned to users unless we create the collection. To create a role collection (screenshot attached),Go to Security > Role CollectionsClick on Create, enter a name for the role collection and click Create.Tip: You can decide to create one common role collection for all Joule roles and assign them together or create separate role collection in case you want have better controls and maintain it individually. Image 8The new role collection will get listed in the page, now select the created role collection, and click on Edit.Image 9 Now, under Roles, click on the textbox, a pop-up will appear.Image 10 Search for “das-application” in Application Identifier. Select the appropriate option. You’ll see the Joule roles listed. Select the ones which must be added and click on Add.Image 11 This helps us to create the Role collections which now can be assigned to the users.To assign users, go to the users section under the role collection, enter the email-id and select appropriate identity provider. Now you can Save the role collection.Image 12Now let’s go to our joule and see what options are available as a user with the role “End User”.2.1.1 End User (end_user)This is the role which gives the user access to the standalone URL of your Joule tenant. For more on using the joule web client, refer Using the Joule Web Client | SAP Help Portal.2.1.2 Tenant Admin (tenant_admin)As a tenant admin, you can access the Joule Admin Center – a tenant specific user interface, offered for customizing respective Joule configurations. You can find more information here – Joule Admin Center | SAP Help Portal.To access the Joule Admin Center:Go to the BTP Cockpit and open your subaccount having Joule. Go to Subaccount Overview > Instances and Subscriptions.Expand the Joule application subscription (das-application). Click Go to Application to fetch the Joule application URL.Image 13Get the Joule tenant URL and append “/admin” to form the admin center URL for the respective Joule tenant – <Joule tenant URL>/admin.Image 14You’ll get the below page for Joule Admin Center, given you have the role tenant_admin assigned to your user. Here you can find the list of assistants available in your Joule, and you can select each of them to see their system alias and destinations setup for each.Image 15 Note: SAP team is actively working to add more details and features to this page, stay tuned for more updates. In your case you may only see the “sap_digital_assistant” with standard Joule integration. 2.1.3 Extensibility Developer (extensibility_developer)This one is applicable to the customers/partners who would like to use Joule extensibility in your landscape. This role is required to build and deploy capabilities for Joule. For more information, refer Joule Development | SAP Help Portal.In addition, this role provides Debug option which provides visibility into runtime execution through the Logs View, which helps administrators and developers monitor and troubleshoot custom capabilities effectively.With this role, users can:View end-to-end execution logs for Joule conversations.Easily identify execution outcomes using visual status tags (Blue for success, Red for errors).View Correlation IDs to trace requests across the complete conversation and use these as supporting information for issue analysis and support ticket creation.Use log details as To use the Debug features, open the Joule conversation window, click on the Debug icon on the top right corner. A side window named “Request Logs” will appear, Here you can find the logs and trace the conversation.Image 16A side window named “Request Logs” will appear, Here you can find the logs and trace the workflow of the conversation in case you face any error or run into an issue. You can expand the log messages by clicking on the arrow beside the message to find further details.Image 17Now, let us see how to fetch the Correlation ID for a conversation in Joule. This ID must be shared with the support team for effective troubleshooting and error tracing.Open the conversation for which you want to retrieve the Correlation ID. For messages generated by Joule, a debug icon is displayed in the top-right corner of the message. This icon will be blue if the response was generated successfully. In case the request ran into an error, the icon will be red.Image 18Click this icon to open a split view titled “Response Payload.” Scroll to the bottom of the payload, where you will find the correlationID field.Image 19Share this Correlation ID with the Joule support team to assist with issue investigation and analysis.Note: For every conversation where Joule is not working as expected or run into any errors, the Joule Support team will be requesting the correlation ID or the conversation trace. Please ensure to have these information attached to the support ticket which you’ll be creating for the issues/troubleshooting.2.1.4 Analytics Admin (analytics_admin)Joule offers an analytical insight on the Joule usage with the analytics_admin role. You can find the official help page here – Joule Analytics Center | SAP Help Portal.Go to the BTP Cockpit and open your subaccount having Joule. Go to Subaccount Overview > Instances and Subscriptions.Expand the Joule application subscription (das-application). Click Go to Application to fetch the Joule application URL.Image 20Get the Joule tenant URL and append “/analytics” to form the Joule Analytics Center URL for the respective Joule tenant (your BTP subaccount) – <Joule tenant URL>/analytics.Image 21You’ll get the below page of Joule Analytics Center. Click Acknowledge and continue to explore the analytical insights provided.Image 22You can view analytics across interaction types, products, scenarios, and client types for a selected time range, providing insights into overall Joule usage, adoption, and engagement.The Summary section highlights key metrics, including total messages, total conversations, and the average messages per conversation, giving a quick snapshot of overall interaction volume and conversation depth.Image 23We have 2 sections, Messages and Conversation – each representing a different level of interaction. A message is an individual request or response generated within Joule and is counted across all conversations. A conversation represents a single, distinct interaction thread initiated by a user, identified by its conversation topic name. Each conversation can contain one or more individual messages exchanged within that thread.The Messages section breaks down message activity by product, scenario, and interaction type, helping you identify which products and scenarios are most frequently used and how users interact with Joule across different interaction types.Image 24The Product Usage graph clearly shows which products are using Joule most actively. From the sample data in the screenshot below, SAP S/4HANA Public Cloud has the highest usage, followed by SuccessFactors and SAP Analytics Cloud / Just Ask, while products such as IBP and IPD show comparatively lower message volumes. This view helps identify where Joule adoption is strongest and enables easy comparison of usage across different products.Image 25The Scenario Usage graph shows how frequently different scenarios are used in Joule. From the data, scenarios such as “ESH_U_SALESORDER” and “purchase order–related scenarios” have higher usage. Other scenarios, including employee views, feedback, and scheduling workflows, show comparatively lower usage. This view helps identify the most actively used scenarios and supports prioritization of monitoring and optimization efforts for high-impact workflows.Image 26The Interaction Type Usage graph illustrates how users engage with Joule across different interaction types. The data shows that scenario-based interactions account for most of the usage, followed by direct responses and slot filling, while information retrieval and file uploads contribute only a small portion. This view helps understand preferred interaction patterns when interacting with Joule.Image 27You can also find weekly statistics of messages and conversations.The Message Count Over Time graph shows how the total number of messages sent to Joule varies over the selected time range. From the sample view, you can see clear peaks and drops, indicating periods of higher and lower activity. This helps administrators and the organization to identify usage trends, understand peak activity periods, and correlate spikes with specific events, releases, or user activity.Image 28The Conversation Count Over Time graph displays how the number of unique conversations changes over time. In the sample screenshot, you can observe days with higher conversation counts, indicating increased user engagement, followed by periods of lower activity. Comparing this graph with the message count helps distinguish between longer conversations and an increase in the number of users or sessions, providing better insight into overall usage behavior.Image 29You can also find Product Usage and Scenario usages under the Conversations showing which product/scenario generate the most conversations.Image 30Additionally, there is a Client Type Usage graph which shows the number of conversations across different client types, such as Desktop, Mobile, and Copilot, helping you understand how conversations are distributed by access channel.Image 31 Overall, these graphs make it easy to visually identify where usage is highest, compare adoption across products, scenarios, and interaction types, and gain actionable insights for monitoring and operational analysis. 3. FAQs on Joule Conversation HistoryAdding, deleting, and renaming conversationsCreate a new conversation by selecting the “New Conversation” option from the side panel menu.Image 32When a new conversation is created, a conversation title is automatically generated based on the first user request–response in the conversation thread.You can rename a conversation at any time by hovering over the conversation in the side panel and selecting “Rename” from the conversation menu, or by selecting Rename from the conversation header.Image 33To delete a conversation, hover over the conversation in the side panel or open the action menu from the conversation header, then select Delete. A pop-up will appear, confirm by clicking “Delete”Image 34Image 35Active conversationsA maximum of 10 active conversations can be maintained at any time. This helps users keep conversations segregated and organized, for example by using separate conversations for different applications such as SAP S/4HANA and SuccessFactors, or by specific business scenarios like leave requests, travel requests, and other workflows.Conversations are sorted with the most recently active on top.Switch between conversations to continue engaging in a different conversation.Image 36 Image 37Expired conversationsA conversation expires after 8 hours of inactivity. Upon expiration you’ll be notified and provided with an option to trigger a new conversation.Conversations are sorted by the creation date of the thread with the newest at the top.Conversations are deleted automatically 7 days after the date of creation.Expired conversations cannot be continued. They can only be referenced for past interaction history.Image 38 As Joule adoption grows across products and scenarios, effective administration becomes the backbone of a reliable user experience. With a clear understanding of Joule roles, analytics, and troubleshooting tools, administrators can proactively monitor usage, resolve issues faster, and support business users more efficiently.Credits & Special thanks to RIG Team (Nagesh Caparthy & Naga Swathi T J) for supporting this blog post. Until the next update — stay tuned and happy learning!!!Best Regards,Amrita Varshini E RSAP Business AI RIG Team Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
