Hello SAP Community, 

I’m excited to share another round of updates and enhancements introduced to SAP Profitability and Performance Management Cloud – Universal Model (SAP PaPM Cloud UM) introduced during May 2026. 

In this What’s New section, you will find information about new features and improvements in the areas of modeling, processing, reporting, and administration. 

Let’s take a closer look at the latest updates and new functionality currently available in SAP PaPM Cloud UM. 

If you’d like to explore previous updates from the team, feel free to check out all past posts using the PaPMCloudUMWhatsNew tag. 

 

Model Screen: Improved Function Attributes Visibility in Protected Environments 

The Model screen now provides a seamless and informative experience for SAP PaPM Cloud Universal Model users with MODEL_ALL and MODEL roles working in protected environments. When selecting a function, the right panel displays the appropriate function information based on the environment type, ensuring users always have access to meaningful content. 

What's Changed 

The Model screen now intelligently adapts the right panel content based on the environment type: 

• Non-protected environment: The right panel displays the full function details. 
• Protected environment: The right panel displays the basic function attributes, giving users clear and relevant information within their access scope. 

 

 

Manage Derivation and Manage Model Derivation: Single-Pass Rule Evaluation 

A new Single-Pass Rule Evaluation checkbox is now available for Derivation and Model Derivation functions. 

This option helps optimize rule evaluation performance for applicable derivation scenarios and is available in the Derivation and Model Derivation headers. 

It enables a first-match run mode for rule evaluation. Instead of processing rules one by one across multiple database statements, the engine compiles all rules into a single SQL CASE statement and runs them in a single operation. 

This reduces database round-trips to a minimum. For large datasets with straightforward rule sets, this is a significant performance gain.

In this mode, the system goes through the rules from top to bottom, and the moment it finds one that matches a record, it applies it and moves on. The remaining rules are not evaluated after a match is found. If no rules match, the record remains unchanged. 

For example, you have three rules: 

1. Country = “DE” and Account = “1000” → Value = “1” 
2. Country = “DE” and Account = “1001” → Value = “2” 
3. Country = “FR” and Account = “1000” → Value = “3” 

A record from Germany with Account “1000” matches Rule 1 and receives Value “1”. A record from France with Account “1000” does not match the first two rules and matches Rule 3, where Value “3” is applied. Records that do not match any rules remain unchanged. 

The first matching rule is applied. Rule order is therefore important, as subsequent rules are not evaluated for the same record. 

This feature is available only when Ensure Distinct Results is set to “Yes”. When Ensure Distinct Results is set to “No”, the checkbox is not available, and existing behavior remains unchanged. 

This mode is designed specifically for one-level derivation scenarios. If the model relies on chained derivation – where the output of one rule becomes the input for another – this mode is not intended for that scenario. This mode is best suited for simpler models, overlapping conditions, large data volumes, and scenarios where the first matching rule should be applied. 

Existing behavior and models are not affected unless the feature is used. Single-Pass Rule Evaluation provides an additional optimization option for supported derivation scenarios. 

 

Manage Writers: New Mode Field – “Explicit” and “Implicit” 

The Writer function now includes a Mode setting in the General Information section, where users can choose how fields are mapped between the input function and the result model: “Explicit” or “Implicit”. All new and existing Writer functions use “Explicit” mode by default. 

“Explicit” Mode 

This is the standard Writer behavior. Users manually map fields between the Input and the Result Model. 

Key highlights: 

• At least one mapped field is required to save a Writer in “Explicit” mode. 

Existing Writer functions without mapped fields will still run. However, new or modified Writer functions must meet this requirement. 

If a Writer function runs without mapped fields, the Result Model structure is created, but no data records are written to the Result Model Entity, leaving it empty. This is particularly important when using “Delete and Insert”, as all existing records are deleted and no new records are inserted.  

“Implicit” Mode 

“Implicit” mode automatically maps fields with matching names between the Input and the Result Model.  

Key highlights: 

• No manual configuration is required if at least one matching field name exists. If none exist, saving is blocked. 

  

• Manual mapping is still allowed, and this can be used when field names differ or when users intend to exclude specific fields. 

• The Fill Fields button is not available in this mode, as field mapping in “Implicit” mode is handled automatically. When field names in the Input and Result Model functions match, the system performs the mapping in the background by default. As a result, no manual field mapping is required. 

Writer’s Behavior with Connections  

The rules apply regardless of whether a connection is used: “Explicit” mode requires at least one manual mapping, while “Implicit” mode requires at least one matching field name. When these conditions are met, the Writer function runs successfully. 

Users can learn more about this new enhancement in an upcoming separate blog post.  

 

Manage Connection: Access to Model Views in Connection Using Environment as Connection Type 

Users can now access Model Views in a connection that has “Environment” as the connection type. 

Previously, only Model Entities were supported for such connections. In some cases, data had to be replicated into a Model Entity to enable cross-environment access, resulting in additional processing steps and duplicated data handling. 

With this enhancement, Model Views with the API State set to “Active” from the source environment are exposed directly, enabling seamless cross-environment access without the need to replicate data into Model Entities. 

For more information about the API State of functions, see Change API State of Function. 

How It Works 

When creating a connection with “Environment” as the connection type, users can select the “Target Model Views” checkbox. 

Once selected, all active Model Views are displayed in the Models list, combined with active Model Entities: 

If the checkbox is not selected, only active Model Entities will be shown: 

Model Views can also be synchronized in the same way as Model Entities. When a Model View is synchronized, a corresponding Model Reference function is created in the target environment, enabling direct access to data from the sourceModel View without requiring execution. This ensures seamless visibility of model data across environments while eliminating data replication. 

For further details, see Manage Connections – Environment in the Application Help for Universal Model. 

 

Manage Processes: Automatic Update of Delta Parameters in Delta Reader 

The Delta Reader includes an enhancement that improves data extraction by automatically adjusting the Delta From and Delta To parameters when an Activity Link is configured, regardless of whether a connection is used. Instead of reloading all data each time, it retrieves only records that were created or updated since the last successful run. This makes data extraction more efficient, reduces system load, and saves processing time, while ensuring that only relevant data is retrieved. 

 
To better understand how this works, let’s look at the following scenario:  

1.  When both “Delta From Parameter” and “Delta Field” are maintained in the Activity Link

• The system evaluates the dataset during execution and identifies the highest value in the selected Delta Field. It then updates the Delta From value automatically, increasing the highest value by 1 (for example, 1 millisecond for timestamps). This ensures that previously extracted records are not retrieved again. 

Initial Data from Source Environment  

Delta Reader Configuration taking data from Source 

 Activity Link configuration  

Activity Initial Parameter Value:  

TSFROM01: 2026-01-01 00:00:00.000 (added manually) 
TSTO01: 9999-12-31 00:00:00.000 (added manually) 

After the initial run, the system updates the delta parameters so that only new data is considered in the next execution. If no new records match the updated filter conditions, the result will simply return no data, confirming that everything is already up to date. This behavior ensures accuracy while avoiding duplicate processing. 

When you check the Data screen in the Delta Reader, and no new records match the updated filter, the result will simply return no data. This means that all records have already been processed in the previous run, and there is nothing new to extract. This 
behavior helps keep the data accurate while avoiding duplicate processing, ensuring the system only works on new updates instead of repeating the same data. 

Note: Depending on the data type used in the Delta Field, the system applies a simple rule: for timestamps, it adds 1 millisecond; for dates, 1 day; for datetime values, 1 second; and for integers, it increments by 1. These small adjustments allow the system to continuously fetch only new data in each run. 

 

Data Type	Update Rule
Timestamp	highest value + 1 millisecond
Date	highest value + 1 day
DateTime	highest value + 1 second
Integer	highest value + 1

2.  When both “Delta From Parameter” and “Delta To Parameter” are maintained in the Activity Link 

• The system calculates the difference between Delta From and Delta To, then moves the whole range forward using that same interval. To prevent overlap with previously extracted data, it also increases the new Delta From value by 1 (for example, 1 millisecond for timestamps), before starting the next range. This helps the system continuously pick up only new data without repeating anything. 

Initial Data from Source Environment  

Delta Reader Configuration taking data from Source 

Activity Link configuration  

Activity Initial Parameter Value:  

TSFROM01: 2026-01-22 00:00:00.000 (added manually) 
TSTO01: 2026-01-22 00:15:00.000 (added manually) 

After the initial run, the Delta Reader automatically updates the timestamp range to keep data extraction smooth and accurate. In this example scenario, if the original interval is 15 minutes (from 00:00:00.000 to 00:15:00.000), the system adds 1 millisecond to the last end time, creating a new start time of 00:15:00.001. It then applies the same 15-minute interval to set the next end time (00:30:00.001). This ensures that each new run moves forward without overlapping previous data while keeping the same time range. 

With this update, the system automatically adjusts both the Delta From and Delta To parameters. When you check the Data screen in the Delta Reader, and no records appear, it simply means there is no new data available. This is normal because the system has already processed the earlier records. Since the system only selects data within the updated timestamp range, no records match the filter, so no data is returned. 

Note: Depending on the data type. It calculates the difference between Delta From and Delta To, then adds a small increment to move the range forward. For a timestamp, it adds 1 millisecond; for a date, it adds 1 day; for a datetime, itadds 1 second; and for an integer, it adds 1 number. These small adjustments help ensure that only new data is processed in the next run without repeating previous records. 

 

Data Type	Update Rule
Timestamp	difference + 1 millisecond
Date	difference + 1 day
DateTime	difference + 1 second
Integer	difference + 1 number

Lastly, you can confirm everything worked correctly by checking the Event Log. The status should show “Run Finished” along with the number of records fetched. This means the process is completed successfully. 

For more information, see the Delta Fields and Parameters guide available in the Help Portal. 

 

Display Runtime Environments: Last Accessed Timestamp 

A new Last Accessed At column is now available in the Display Runtime Environments screen, providing a reliable timestamp of the most recent meaningful interaction recorded for each environment. This makes it easy to distinguish actively used environments from those that have been sitting idle – without having to manually review logs. 

What’s Changed 

A new Last Accessed At field has been introduced to Runtime Environments. This timestamp is automatically updated whenever a meaningful user interaction occurs, covering three key event types: 

• Data modifications – any Create, Update, or Delete operation performed on data within the runtime environment updates the timestamp. For example, adding a new record, editing an existing entry, or removing data will all update the timestamp. This applies across all editing modes – “Indirect”, “Direct”, and “Inline”. 

• Process and Activity actions – any action performed on a Process or Activity within the runtime environment is considered a meaningful interaction. This includes operations such as process termination, activation, activity confirmation, and activity run. For example, confirming a pending activity or activating a process will immediately reflect on the Last Accessed At timestamp. 

• Intentional read access – navigating to a populated Report screen, opening a Page, or accessing the Data screen are all treated as deliberate user interactions and will update the timestamp. For example, opening a report that already has data will trigger an update, as it requires intentional navigation by the user. Note that incidental or background read events are excluded. Only interactions requiring explicit user action update the timestamp.  

Key Benefit 

The Last Accessed At timestamp gives users a dependable and up-to-date reference for assessing runtime environment activity. By capturing meaningful interactions across data modifications, process and activity actions, and intentional read access, users can identify which environments are actively used, and which may be due for review or maintenance from a centralized view. 

 

Manage Report: Enhanced Activity Management and Import/Export Functionality in Rule Element 

The Rule Element in the Report screen has been enhanced with an Activity Selection field and integrated activity actions, enabling users to work with multiple activities directly within the Rule Element. When multiple activities are available for a function with dynamic rules, users can select and switch between activities. The system then updates fields, the rules or results configuration, and related data based on the selected activity. 

The availability of the Activity dropdown and related actions adapts automatically according to the activity status and availability. For functions without activities, the Activity field remains visible but does not provide selection options. 

This enhancement allows for activity lifecycle management, such as Run, Confirm, and Reject, without navigating to Manage Activities. The Run action is available only for active activities and automatically updates the activity status upon execution. Activity status synchronization between Manage Activities and the Rule Element is supported for statuses such as “Active”, “Confirmed”, “Rejected”, and “Inactive”. 

In addition, the Rule Element now supports Import, Export, and Erase functionality for both Rules and Result data. Users can export existing rules or result data, modify them externally, and import them back into the system directly from the Rule Element. Exported files are generated and linked through Comments, while imported content is accurately restored into the grid. The availability of Import, Export, and Erase actions dynamically depends on the selected activity and its status, ensuring a controlled and consistent user flow.  

 

Report Screen: Print Preview Editor 

SAP PaPM Cloud Universal Model now provides a fully interactive Print Preview Editor when you choose the Print button in the Report screen. A modal opens displaying a live preview of the report, giving you full control over how the output looks before printing or saving as a PDF. 

The Print Preview Editor lets you fine-tune the layout interactively before printing or exporting the report. Adjust orientation, resize elements, and modify text settings to ensure the printed or exported document looks exactly the way you want it. 

Key Features of the Print Preview Editor 

• Live Preview Modal: A modal window opens showing exactly how the report will appear when printed. 

• Page Orientation: Switch between “Portrait” and “Landscape” orientation to best fit your report content. 

• Manual Element Resizing: Resize tables, images, and table columns by dragging their borders to fit the page. 

• Fit to Page / Original Size: Choose the Fit to Page button to automatically scale content to the page width or choose the Original Size button to restore elements to their default size. 

• Column Deletion: Hover over a column header to reveal the Remove Column icon, then choose the icon to remove the column from the table directly within the preview. 

• Font and Line Height Controls: Right-click an element to access the Font Size and Line Height controls from the context menu. Adjust the values to customize text appearance and readability. 

• Add New Line Before and After: Right-click a supported element and choose Add New Line Before or Add New Line After from the context menu to insert a new line at the desired position. 

• Print and PDF Export: When the layout is finalized, choose the Print / Save as PDF button to generate the output. 

  

Manage Containers: Improved Filename Format for Container Exports 

The Manage Containers screen includes an enhancement to how exported container filenames are generated. Exported files no longer include special characters in their filenames, improving compatibility across platforms and tools. 

What’s Changed 

With this update, the filename convention has been revised to a clean, standardized format: 

New format: _YYYY-MM-DD_HH-MM-SS.zip 

Where: 

• ENVIRONMENT_ID – the unique identifier of the exported Runtime Environment 
• YYYY – year 
• MM – month 
• DD – date 
• HH – hour 
• MM – minutes 
• SS – seconds 

For example, an exported container will now be named something like CADEMO_2026-05-25_06-17-05.zip – where the timestamp follows a readable date-time format using underscores, with no special characters. The updated format uses a cleaner and more consistent date-time structure for exported filenames. The timestamp is expressed in UTC and covers both full environment exports and delta environment exports. 

It is important to note that files exported using the previous filename convention are still fully supported – existing container zip files using the old format can still be uploaded. 

This change ensures that newly exported container files are consistently named, free of special characters, and compliant with the naming standards expected across various platforms. 

 

Manage Tenant Settings: Tenant Freeze and Unfreeze Support 

Users with the ADMINISTRATION_ALL or TENANTSETTING roles can now freeze and unfreeze a tenant within the Manage Tenant Settings application.  

This enhancement provides full self‑service control over upgrade behavior during critical business periods – such as year‑end closing, major migrations, or any time when unplanned upgrades could affect business activities. 

Users with TENANTSETTING_READ can view the current upgrade policy but cannot modify it. 

What's New 

Freeze Tenant and Unfreeze Tenant Buttons 

Two new action buttons are now available in the Manage Tenant Settings screen: 

• Freeze Tenant: Suspends automatic upgrades for the selected tenant. 
• Unfreeze Tenant: Restores the tenant to its standard upgrade schedule. 

These actions allow administrators to safeguard system stability with a single action quickly. 

Automatic Tenant Setting Provisioning 

A Tenant Setting record is now automatically created during upgrade if one does not already exist in the tenant. This ensures the freeze/unfreeze functionality works immediately – no manual initialization required.  

Simplified User Interface – Create and Delete Buttons Removed 

Because each tenant supports exactly one Tenant Setting, the Create and Delete buttons have been removed from the main application level. This streamlines the experience and avoids confusion. 

Note: Creating multiple email templates within a Tenant Setting remains fully supported. For more details, refer to the Manage Tenant Settings Help Portal page or the update introduced in SAP PaPM Cloud Universal Model: What’s New as of 2024-10-07. 

How the Freeze/Unfreeze Process Works 

1.  Freezing a Tenant 

Upon selecting the existing Tenant Setting, if the tenant is in Auto Upgrade Policy, the Freeze Tenant button will be enabled. 

When the Freeze Tenant button is selected, the Freeze Tenant dialog opens, where users can set Disable regular tenant upgrades to “Yes”. After confirming the action, the tenant is assigned a Frozen Upgrade Policy. 

This indicates that no upgrades will be applied until the tenant is unfrozen.  

2.  Unfreezing a Tenant 

If the user intends to return to the Auto Upgrade Policy, just select the Frozen tenant setting, and the Unfreeze Tenant button will be enabled.  

To return to the Auto Upgrade Policy, the user can select the frozen tenant setting. The Unfreeze Tenant button then becomes available. 

When the Unfreeze Tenant button is selected, the Unfreeze Tenant dialog opens, where users can set Enable regular tenant upgrades to “Yes”. After confirming the action, the tenant returns to the Auto Upgrade Policy, and upgrades resume.  

Upgrade Policy Visibility –  New Audit Fields 

To improve transparency and auditability, the Tenant Setting record now includes three new fields: 

• Upgrade Policy – Indicates whether the tenant is in “Frozen” or “Active” state. 
• Changed On – Timestamp of the most recent policy change. 
• Changed By – The administrator who performed the action. 

These fields provide immediate clarity on the tenant’s upgrade status without requiring cross‑system checks. 

 

Deprecated Function Notification 

SAP PaPM Cloud Universal Model now clearly identifies deprecated runtime functions directly within the Data screen. When a user opens the Data screen for a function that has been marked as “Deprecated” (via the API state), a notification banner is displayed at the top of the screen, ensuring users are immediately aware that the function should no longer be actively used and may be removed in a future release. 

To maintain upgradeability, functions are deprecated instead of being removed immediately. Without a visible indicator, users may continue using deprecated functions without being aware of their state. This improvement removes that ambiguity and helps teams plan their transitions proactively. 

What's Changed 

• A notification banner now appears at the top of the Data screen when the underlying runtime function has an API state of “Deprecated”.
• The banner displays a clear, user-friendly message: “This function is deprecated and may be removed in future releases.” 
• Users can dismiss the banner using the Close (X) button. 
• The banner reappears each time the Data screen is opened for a deprecated function – dismissing it in a previous session does not suppress future warnings. 
• The banner is non-blocking; users can still view and interact with all data on the screen as usual. 

 

Adapt UI in Show Screen 

Users can now maintain Color, Hidden, and Read-Only conditions directly from the Profile menu without opening the object page in Adapt UI mode. 

The new Adapt UI option opens a centralized configuration dialog. Users can manage conditions for available fields and columns using the same layout and behavior as the existing  Adapt UI functionality. 

This enhancement also supports scenarios where Object Page access is unavailable, such as calculation views. Users can maintain conditions consistently for any function directly from the Data screen. 

 

That wraps up this edition! 

I hope you enjoy exploring the latest features and improvements delivered in SAP PaPM Cloud UM. Don’t forget to check back next month for more updates. 

Thank you for taking the time to read, and feel free to share this post with your colleagues and friends. Thank you😊!