Hello SAP Community,
Welcome to our latest What's New update! In this edition, we'll walk you through the newest enhancements and features designed to improve your experience with SAP Profitability and Performance Management Cloud Standard Model.

System | AI Conversation Monitor 

A new AI Conversation Monitor screen is available under System. Administrators can use it to monitor all Joule conversations across the system, review the complete exchange for any conversation, and delete conversations that are no longer needed. 

How it works: 

1. Navigate to System > AI Conversation Monitor. The screen displays all Joule conversations in the system. Each row includes the Conversation ID, Title, Local Timestamp, User, Number of Messages, and Number of Files. All columns support sorting and filtering. 
2. To view a conversation, select a row to expand the content inline. Prompts and responses appear in chronological order. Any files attached to the conversation are available as downloadable links. 

1. To delete one or more conversations, select them using the checkboxes and choose Delete Conversations from the toolbar. A confirmation dialog appears before the conversations are deleted. After the deletion is completed, the list refreshes and a Deletion completed toast appears.  

The deletion is also logged in the Application Monitor and Process Monitor with the Joule Conversation Deletion run type. 

AI Conversation Monitor screen supports the standard layout management features. Users can save private or public layouts, switch between them, and set a default that applies automatically when the screen is opened. 

For more information, refer to the SAP Help Portal. 

Settings | Fast Track Release Cadence Compatibility Messages 

To help prevent compatibility issues between tenants using different release cadences, two new dialogs have been introduced for Fast Track users. 

1. Updated Fast Track Activation Dialog 
   

   The confirmation dialog displayed when activating Fast Track mode on the Settings screen now includes forward compatibility guidance. Users are informed that: 

   • Environments exported from a Fast Track system can be imported on any release cadence. 
   • If the destination system uses the monthly release cadence, users must wait for the next monthly release before importing. 

   

   • If Fast Track is deactivated later, the change takes effect with the next monthly release. 

   

2. New Environment Export Compatibility Warning 

A new Fast Track Export Compatibility warning dialog is displayed whenever a user exports an environment from a Fast Track tenant. The dialog reminds users that the exported environment can be imported immediately only into systems using the Fast Track release cadence. Importing into a monthly release cadence system requires waiting for the next monthly release. 

These changes help prevent import failures caused by version incompatibilities between Fast Track and monthly-release tenants. 

For more information, refer to the Release Cadence Settings | SAP Help Portal 

Process Monitor | Cancel Activation 

Now in SAP Profitability and Performance Management Cloud Standard Model, users can cancel an activation that is queued or currently in progress directly from the Process Monitor.  

Note: The Cancel Activation action is available only to users assigned the EXECUTION_MAN_ALL role.  

Authorized users can select an activation and use the Cancel Process action to stop its execution.  

Depending on its current state, the activation is either cancelled immediately or removed from the queue.  
 
After a successful cancellation, a dedicated red cancellation status icon is displayed in the Process Monitor, providing a clear visual indication that the activation was cancelled and corresponding notifications will appear: 

In addition, informative status updates and cancellation message loglog are consistently reflected in the In addition, informative status updates and cancellation messages in Application Monitor:  

and Modeling screen:  

giving users full visibility into the outcome of the cancelation action. 

Modeling | Supported Partitioning Run Modes for Model Tables 

The Partitioning field in the Expert section of a Model Table Properties Panel allows modelers to assign a Partitioning function to control how the table's data is partitioned at runtime. The Partitioning function itself is configured as a separate entity, where a Run Mode field defines the processing behavior. Previously, all available Run Mode values appeared as selectable options in that configuration, including modes that do not apply partitioning ranges at the database level, with no design-time indication that certain selections would have no effect. 

This raises a natural question for modelers assigning partitioning to a Model Table: if a Partitioning function is configured with a Run Mode that does not activate partitioning, will the Model Table silently process data without partitioning? 

SAP Profitability and Performance Management Cloud Standard Model now filters the options available in the Partitioning field under the Expert section of the Model Table Properties Panel. Only Partitioning functions configured with one of the four effective Run Modes (PPBP, PPDP, SPXP, SUXP) are displayed as selectable options. Partitioning functions using non-partitioned Run Modes no longer appear in this list. 

• PPBP (Parallel, Packaged, Batch-Process, Partitioned): Processes each package in parallel using batch jobs, with partitioning ranges applied at the database level. 

• PPDP (Parallel, Packaged, Dialog-Process, Partitioned): Processes each package in parallel using dialog mode, with partitioning ranges applied at the database level. 

• SPXP (Sequential, Packaged, Process like Caller, Partitioned): Processes each package sequentially using the caller's process type, with partitioning ranges applied at the database level. 

• SUXP (Sequential, Unpackaged, Process like Caller, Partitioned): Processes the dataset as a single unpackaged run using the caller's process type, with partitioning ranges applied at the database level. 

Important: For existing Model Table entities that had a Partitioning function with a non-partitioned Run Mode assigned, the system automatically clears the Partitioning field in the Expert section. This does not affect function execution because those Partitioning functions were not applying partitioning at runtime. 

Note: This restriction applies specifically to the Partitioning field within a Model Table function. Partitioning configurations in other function types are not affected by this change. 

For more details, see the SAP Help Portal documentation on Partitioning. 

Modeling | Query-based Master Data: Duplicate Value Validation 

In SAP Profitability and Performance Management Cloud Standard Model, Query-based Master Data allows modelers to drive field value lists directly from a Query Function's output. Previously, the system applied no uniqueness check on those query results: if the underlying query contained duplicate values, activation proceeded without warning, and duplicates could silently enter the field's master data. 

This raises a natural question for modelers who build field definitions around query output: what happens when the query produces duplicate values? Does the system silently accept them, reject the activation, or deduplicate automatically? 

SAP Profitability and Performance Management Cloud Standard Model now validates Query Function output for duplicate values at two points in the lifecycle. When a Query Function is configured as a Query-based Master Data source, if duplicates are detected in the query results, activation is aborted and a message identifies the duplicate entries, preventing corrupted master data from being saved. 

The validation covers two points in the lifecycle: 

• At activation: If the Query Function assigned as Query-based Master Data contains duplicate values at the time of activation, the activation is blocked and a message points to the duplicate data. 

• Post-activation: If a duplicate value is added to an editable query after activation, the model table that uses the field with Query-based Master Data cannot be saved, and the same duplicate validation error is returned. 

Important: Activation will fail if the Query Function used as Query-based Master Data contains duplicate values. All duplicates must be resolved in the query before activation can complete successfully. 

Note: This validation applies only to Query Functions configured as a Query-based Master Data source. Query Functions used in other modeling contexts are not affected. 

For more details, see the SAP Help Portal documentation on Query and Query-based Master Data. 

Modeling | Query-based Master Data 

Query-based Master Data has been available in SAP PaPM Cloud Standard Model for some time, allowing you to source master data from an external query rather than maintaining it manually. When configuring the Query Elements, you could already map tags such as KEY, DESCR, IS_NODE, PARENT_KEY, HIER_NAME, and others to define the structure of your master data. 

However, with this enhancement you will have the ability to control who can view and edit the data directly through the query configuration. Until now, this was only possible through the Internal Master Data configuration table. 

Two new tags are now available in Query Elements: 

• READ_ACCESS — maps the column that defines which teams can view the data 

• WRITE_ACCESS — maps the column that defines which teams can edit the data 

This enhancement brings External (Query-based) Master Data in line with the access control capabilities that are already available for Internal Master Data, providing a consistent and flexible way to manage data access across both approaches. 

How to configure it 

After mapping the READ_ACCESS and/or WRITE_ACCESS in the Query Elements, maintain the access values in the Data Management Screen. Enter team names as semicolon-separated values in the corresponding columns — for example: TEAMTEST;TEAMMOTHER. 

Access rules 

The access logic is intuitive and explicit: 

Read Access	Write Access	Who can view	Who can edit
empty	empty	All users	All users
TEAM1;TEAM2	empty	TEAM1;TEAM2	No users
empty	TEAM3	TEAM3	TEAM3
TEAM1;TEAM2	TEAM3	TEAM1;TEAM2;TEAM3	TEAM3
TEAM1;TEAM2	TEAM2	TEAM1;TEAM2	TEAM2

A few things worth noting: 

• Teams listed in Write Access are automatically granted Read Access. There is no need to specify the same team in both columns. 

• If a team name does not exist in the system, a warning toast is displayed when the value is entered in the Data Management Screen, and an additional warning is shown upon query activation.  

For more details, see the SAP Help Portal documentation on Query and Query-based Master Data. 

Modeling | Deletion Activity in Process Template 

A new Deletion Activity is available in SAP Profitability and Performance Management Cloud Standard Model, which can be added to a process template to delete function data across the environment as part of a process flow.  

Previously, environment-wide data deletion in the Modeling screen could only be performed manually using the Delete Data from Selected Function or Delete Data from All Functions button. The new Deletion Activity allows users to incorporate data deletion directly within a process template and automate it as part of a process flow. 

The Deletion Activity can be placed anywhere in the process chain within a process template or configured as a standalone node. Multiple Deletion Activities can be added independently within the same template. 

The following deletion options are available: 

• Delete data from all functions (default) – Deletes data from all functions in the environment except for model tables with Transport Data option set to “Yes” and functions with linked result model tables with Transport Data option set to “Yes”. SAP HANA functions are also excluded from data deletion. 
  

• Delete data from selected functions – When selected, an additional Functions for Data Deletion field is displayed, where you specify the functions to include. With this option, data can also be deleted for functions linked to result model tables with Transport Data option set to “Yes”. 
   

How it works:  

1. Open the Modeling screen of any environment. 
2. Expand the Calculation Unit Details > Process Templates. 
3. Open the palette in the left panel, then drag and drop the Process Template node to Process Templates. 
4. With the Process Template node selected, drag and drop the Deletion Activity from the palette to the node. 
5. With the Deletion Activity selected, open its properties in the right panel. 
6. Under Delete Type, select one of the following options: 
7. Delete data from all functions (default option) 
8. Delete data from selected functions – If this option is selected, specify the functions in the additional Functions for Data Deletion field that appears. 
9. Save and activate the Deletion Activity. 
10. Run the Deletion Activity to delete data depending on the Delete Type configured for it. 

The Deletion Activity is also logged in the Application Monitor and Process Monitor with the run type Run. It can also be performed as part of a process instance in Process Management or included in an automated process when added as part of a process instance job in Process Scheduler. 

For more information, see Calculation Unit | SAP Help Portal. 

Report Management | Create, Update, or Delete Report Charts 

You can now use Joule in Act mode to create new charts, update existing ones, or delete charts from your report — all through a simple conversation, without leaving the chat. 

Previously, charts could only be added or modified manually through the report editor. With this update, Joule can create and manage charts based on dynamic data sourced from the process activity tables and views available in the report palette as input or output activities — the same data a user can access when creating charts manually. You can specify the chart type in your instruction, and Joule uses the corresponding data source from the report. 

The following chart types are supported: 

Dynamic Data Charts 

Process  Relationship  Waterfall  Stacked Bar/Column  Stacked Area  Time Series  Heat Map

Numeric Point  Dimension Value  Sankey    Chord  Sheet  Grid  Combination Column and Line

Combination Stacked Column and Line  Pie  Donut  Sunburst  Line  Bar/Column

Map Display (Region-Based) 

When a Region field is available in the data, the following chart types can also be displayed on a map:  

• Pie 

• Donut 

• Sunburst 

• Bar/Column 

To get started, open the Joule panel in the Report Management application, choose Act to switch to Act mode, and type your instruction specifying the chart type and any relevant data or positioning details. 

The following actions are supported: 

Action	Example Prompt
Add a new report chart	“Please create a bar/column chart with a title ‘Overview of Top-Up Tax Amount in 2024’ based on the data of Input/Output Activity ‘Top-Up Tax Amount’ with measure — Top-Up Tax Amount, and the following dimensions — Country/Region, Parent Company Code. Insert it in the Reporting and Simulation page.”
Update an existing chart	“Please change the chart type of ‘Overview of Top-Up Tax Amount in 2024’ into a line chart and update the title to ‘2024 Top-Up Tax Amount’”
Delete a report chart	“Delete the Heatmap chart entitled ‘Version Comparison: Net GloBE Income vs. Top-Up Tax by Country & Scenario.’”

Joule applies non-destructive actions (create, update) immediately by automatically refreshing the report screen.  

For destructive actions such as deletion, Joule asks for your confirmation before proceeding — choose Approve to apply or  Reject to cancel. 

The following notes apply: 

• Changes applied by Joule in Act mode cannot be undone. For updated charts, you can ask Joule to restore the previous version based on the conversation context. 

• Deleted charts cannot be recovered. 

• If you do not specify a position, Joule adds the new chart at the end of the report. 

• If you are in Edit mode with unsaved changes, save or discard them first — Joule will prompt you if needed. 

For more information, refer to the relevant pages on our SAP Help Portal: Create, Update, or Delete Report Charts | Prompting Recommendations 

Environments | Enhanced Delete Confirmation Dialog 

The confirmation dialog in the Environments screen has been updated to display a more detailed list of the nodes and environments that will be deleted, giving users greater clarity before confirming the action. 

Previously, the dialog displayed a generic message. It now dynamically lists the names and IDs of the selected items, and adapts the dialog title and body text to match the exact selection — for example, distinguishing between a single node, multiple nodes, environments only or a combination of both. 

When multiple nodes and environments are selected, up to 10 nodes and 10 environments are listed individually. When the selection exceeds these limits, the remaining items are summarized as a count of the items not listed. 

For a complete list of all deleted nodes and environments, refer to the message logs in the Application Monitor under the Environment Deletion run type. 

For reference to the deletion process, refer to Environment | SAP Help Portal. 

Source link