SAP PaPM Cloud Standard Model: Introducing The AI Conversation Monitor

Hello, SAP Community members!

If you manage SAP Profitability and Performance Management Cloud Standard Model and your organization is using Joule, this one is for you.

As Joule becomes a bigger part of how users work with data and reports, administrators face a practical question: what are users actually discussing with the AI? When a conversation produces an unexpected result, or when a compliance team asks for a record of AI interactions, where do you go?

That changes with the AI Conversation Monitor. Available via the System submenu, it gives administrators a full view of every Joule conversation in the system. You can read the content of any conversation, download conversations as ZIP archives for audit or offline review, upload previously downloaded archives to restore conversations, and delete conversations along with all associated messages and files.

Why Does the AI Conversation Monitor Matter?

Joule conversations contain real business context. The prompts show how users are thinking through their data. The AI responses influenced decisions. The uploaded files were part of active analysis. Without a way to see and manage these conversations from one place, administrators have limited visibility into how AI is being used and no clean path for compliance reviews or data lifecycle management.

Note: Joule users are informed up front that administrators can access their conversations. The AI Notice within the Joule panel displays: “Joule is powered by generative AI and all output should be reviewed before use. System administrators can access conversations for security, compliance, troubleshooting, or quality assurance purposes. Please do not enter any sensitive personal data, and avoid entering any other personal data you do not wish to be processed. Learn more in the Joule Data Protection and Privacy.”

Before You Begin

Downloading, uploading, and deleting conversations each produce a separate log entry in the Application Monitor and the Process Monitor. Each entry includes a dedicated Joule run type and conversation IDs of all affected conversations. These entries persist even after conversations are deleted.
The 400 MB size limit applies to uploads only. Downloads have no cap. The system always produces a single ZIP archive regardless of how many conversations you select or their total size. If you plan to re-upload a downloaded archive larger than 400 MB, split it first.

Access and Required Roles

The AI Conversation Monitor is available to administrators with one of the following roles:

AI_CONVERSATION_ALL: Full access to all toolbar actions, including Download, Upload, and Delete.
SYSTEM_USER_ALL: Legacy role with the same access as AI_CONVERSATION_ALL.
AI_CONVERSATION_READ: Can view the conversation list, open the content panel, and download conversations. Cannot upload or delete.

Administrators without any of these roles will see the AI Conversation Monitor greyed out in the System menu. Navigating to the screen directly returns a 403 Forbidden error.

Note: For details on role templates in SAP Profitability and Performance Management Cloud Standard Model, see Role Templates in Standard Model on the SAP Help Portal.

Meet the AI Conversation Monitor

Navigate to Menu > System > AI Conversation Monitor.

Navigate To Aim Screen.gif

The screen has three areas:

The Conversation List shows a tabular view of all recorded Joule conversations. Each row has six columns: Conversation ID, Title, Local Timestamp, User, Number of Messages, and Number of Files. Sorting, filtering, column arrangement, and grouping work the same way as on other monitors in SAP Profitability and Performance Management Cloud Standard Model. If you have used the Application Monitor or Process Monitor, the table will feel familiar.
The Conversation Content Panel opens on the same screen when you select a row. It shows all prompts and Joule responses in chronological order, plus any files uploaded during that conversation. Each file is a downloadable link, so you can retrieve individual attachments without exporting the full archive. Close the panel with the X button at the top right, the Esc key, or by clicking outside it.

In Line Conversation Pt 2.Gif

The Message Log sits at the bottom of the screen in the same format used on other SAP Profitability and Performance Management Cloud Standard Model screens like Content Management and Process Scheduler. After each download, upload, and deletion, the result appears here, so you can confirm it without leaving the screen.

Toolbar Actions

The header toolbar has three sections: General, Edit, and Layout.

The General section has the Refresh button, which reloads the conversation list without reloading the browser.

The Edit section has three action buttons:

1. Download Conversations

Select one or more rows and click Download Conversations to export them as a single timestamped ZIP archive. The archive contains one folder per conversation. Each folder holds a JSON file with full conversation content and metadata (Conversation ID, Title, Local Timestamp, User, and all messages), plus all files uploaded during that conversation.

Important:

The Download button is not available when no row is selected.
Download is all-or-nothing. Either all selected conversations are packaged successfully, or the entire operation fails. There is no partial download.
The operation is logged in the Application Monitor and Process Monitor under the Joule Conversation Download run type.
When you start a download, the system displays toast notifications to indicate the progress and outcome of the operation and records the result in the Message Log. For single downloads, the Message Log contains the corresponding Conversation ID, while for bulk downloads, it directs you to the Application Monitor, where you can view the complete list of downloaded items.

Download Conversations.gif

2. Upload Conversations

Choose Upload Conversations to restore previously downloaded conversations from a ZIP archive. The Upload button is always available, regardless of row selection.

The system checks the archive and restores only conversations that are not already in the system. If a Conversation ID already exists, that conversation is skipped rather than overwritten. If part of a conversation is corrupted (a single message or file, for example), that part is skipped and the rest of the conversation is still imported. When the upload finishes, the Message Log shows a summary of how many conversations were imported and how many were skipped.

Important:

Upload is available to AI_CONVERSATION_ALL and SYSTEM_USER_ALL only. Administrators with AI_CONVERSATION_READ cannot access this action.
ZIP files larger than 400 MB are rejected. Split the archive before uploading.
The operation is logged in the Application Monitor and Process Monitor under the Joule Conversation Upload run type.
When you start an upload, the system displays toast notifications to indicate the progress and outcome of the operation and records the result in the Message Log. For single uploads, the Message Log contains the corresponding Conversation ID, while for bulk uploads, it directs you to the Application Monitor for the complete list. If some conversations were skipped or partially imported, the Message Log also shows the imported and skipped counts.

Upload Conversations.gif

3. Delete Conversations

Select one or more rows and choose Delete Conversations from the header toolbar. A confirmation dialog opens before the deletion is performed, allowing you to review the action and either proceed with or cancel the operation.

Important:

Conversation deletion is available to users with AI_CONVERSATION_ALL and SYSTEM_USER_ALL role only. Administrators with AI_CONVERSATION_READ role cannot delete conversations.
Deletion is permanent. All associated messages and files are removed and cannot be recovered.
The operation is logged in the Application Monitor and Process Monitor under the Joule Conversation Deletion run type.
Audit log entries in the Application Monitor persist after deletion. A deleted conversation remains traceable by its Conversation ID.
When you start a deletion, the system displays toast notifications to indicate the progress and outcome of the operation and records the result in the Message Log. For single deletions, the Message Log contains the corresponding Conversation ID, while for bulk deletions, it directs you to the Application Monitor, where you can view the complete list of deleted items.

Delete Conversations.gif

Layout

The AI Conversation Monitor supports full layout management. Save private or public layouts, switch between them, set a default, and rename or delete your own layouts, consistent with other monitor screens.

End-to-End Scenario: From Joule Session to Archived Record

Here is what a typical oversight and archiving workflow looks like.

A team member uses Joule for a series of AI-assisted queries. The conversation is recorded automatically and shows up in the AI Conversation Monitor for administrators with the appropriate role.
Navigate to Menu > System > AI Conversation Monitor. The conversation is in the list with its Conversation ID, Title, Local Timestamp, originating user, and message and file counts.
Select the row. The Conversation Content Panel opens inline with the full exchange in chronological order. If the user uploaded a file during the session, it appears as a downloadable link.
To archive the conversation, select the row and click Download Conversations. The system produces a timestamped ZIP with one folder containing a JSON metadata file and all uploaded files. The Message Log confirms the result; the Application Monitor records it under the Joule Conversation Download run type.
To remove the conversation after archiving, select it and choose Delete. Confirm in the dialog. The conversation, its messages, and its files are gone.
Open the Application Monitor via Menu > System > Application Monitor. The deletion log entry is there under the Joule Conversation Deletion run type, with the Conversation ID. That record stays even after the conversation is deleted.

From start to finish: the conversation was created by a team member, reviewed by an administrator, exported as a ZIP, deleted from the active list, and its audit entry confirmed in the Application Monitor.

Wrapping Up

Compliance teams are asking for a record of AI interactions. A manager wanting to know why Joule gave a particular answer last Tuesday. A periodic cleanup of conversations that no longer need to be in the system. These are the situations the AI Conversation Monitor is built for, and it handles all of them from a single screen in SAP Profitability and Performance Management Cloud Standard Model.

How are you using it? Focused on compliance tracking, investigating specific AI responses, or managing conversation volume over time? Share your approach in the comments.

I hope this post gives you a solid picture of what the AI Conversation Monitor can do. If you have questions, reach out via the SAP Profitability and Performance Management Community.

Related Resources

AI Conversation Monitor on the SAP Help Portal. Official documentation covering screen layout, available actions, role prerequisites, and step-by-step procedure.

Source link