SAP PaPM Cloud Universal Model: What’s New as of 2...

arliesanisidro · ‎2025 Feb 10

Hello! We are back again for another series of What’s New for SAP Profitability and Performance Management Cloud Universal Model (SAP PaPM Cloud UM) for this month which aims to continuously provide a seamless experience to its users.

In case you missed it, you can always catch up on the latest developments and releases about SAP PaPM Cloud UM following the relevant tag: PaPMCloudUMWhatsNew.

Now, let’s get started!

Model

Manage Environments: Enhancement for Activation of Large Environments

When activating environments in the Manage Environments screen, as described in the Application Help, users can choose whether the Activation will be performed in the background or not ("Yes" or "No").

Although, we do understand that there may be large environments that consist of multiple functions which might take a while for its activation to finish. Now, if an environment's number of functions exceeds 30, the system will automatically set the environment activation in the background which will allow users to perform other activities in the tenant while the activation is in progress.

Manage Functions: Relations in the Function Object Page

In the Relations section of the Function object page, the column Is New has been introduced. This will allow users to distinguish if the relation is created within the selected Model function or if it is inherited. This new column will display the following value:

"Yes": if the relation/s is created within the current Model function.
"No": if the relation/s is inherited from the Input function of the current Model function.
Please note that this will be populated and is currently applicable only to Model View function of Type: Projection.

For example, a user has a relation created in a Model Entity. Hence, this will be displayed under the Relations section of the said function in its Function object page. Since the relation was created within the Model function itself, it will be populated with the value "Yes" under the Is New column.

If the Model Entity is used as an Input to a Model View of Type: Projection, the relation coming from the Input will be inherited by the Model View. This relation will then appear under the Relations section of the Model View of Type: Projection in its Function object page. As the relation was inherited by the Model View of Type: Projection from the Model Entity function where it was created, it will be populated with the value "No" under the Is New column.

In addition, user should also be able to see the fields inherited from the Relation of its Input upon choosing the Field value help list.

Manage Connections: Maintain Value Help Tag and Assert Not Null

An enhancement has been implemented in Manage Connections wherein Modeling users can maintain or adjust the configuration of the Value Help Tag field and the Assert Not Null checkbox in the columns which the new configuration can be used after syncing models.

Simultaneously, the original values of these attributes can still be seen in the columns Original Value Help Tag and Original Assert Not Null as reference.

Model View: Support for Value Help Tag "Alternative Key"

The Model View function has been enhanced to add a new Value Help Tag called Alternative Key. Using the Alternative Key value help tag assigns data to a field which makes it behave like a master data. To maximize the functionality, the example below can be used as a guide for the configuration.

The Model View function will use a Model Entity function with the data below as its Input.

Configure the Model View function by assigning the field "Desc" in the Field section and set its Value Help Tag as Alternative Key, then Save.

For the functionality to be used by a Model Entity, a relation should be configured in which a field being used on the function will obtain data from the source function.

For more information about the relations functionality, kindly read the blogpost released by our colleague: Master data and high end data validation using relations in SAP PaPM Cloud Universal Model.

After a successful save of the function and activation of the environment, the functionality will now be available when the users add data to a Model Entity. The field that was declared as an Alternative Key to a Model View function now has a value help icon which contains the data, thereby functioning like a master data.

Process

Manage Activities: Dynamic Rules for Conversion to support multiple Assignments

Using the Currency Conversion and Unit Conversion functions, we can change the currency or unit of a measurement without changing the value of that quantity. In addition, it offers the capability of handling multiple conversions under the same Rule ID.

When the Conversion function (Currency and Unit) is used as an Activity Function of an Activity, the Dynamic Rules support only one conversion per Rule ID. To support multiple conversion entries for the same Rule ID, enhancements were made to the Dynamic Rule to maintain the same behavior on the function level.

Report

Story Filters Functionality

We are excited to introduce a new feature for filtering data in Reports called Story Filters. Once set up, Story Filters will be applicable across the Report – improving user experience and control.

Key Features

Report Filtering
- Story Filters are relevant for all pages in a report, allowing for consistent data filtering across multiple sections. They are initially defined in the General section, where Page Filters are set.
- Users can assign specific statuses to fields of Story Filters:
  - Mandatory: At least one value must be maintained as the default. If left empty, the object saves, but the data will not load in the report.
  - Mandatory Single Value: Requires exactly one default value.
  - Optional (Default): Filters are optional, giving users flexibility.
  - Optional Single Value: Allows selection of a single optional value.
  - Fixed: A predefined value is set and cannot be changed in Display Mode.
- Once defined, Story Filters appear at the top of each page in the Report and can be adjusted in Display Mode.
Dynamic Filtering in Display Mode
- Users can modify Story Filters in the header of the Report without switching to Edit Mode.
- Changes apply across the entire report in real-time.
- To apply changes, the Apply Filters button should be chosen.
Story and Page Filter Interaction
- Users can seamlessly switch between Story Filters and Page Filters in Edit Mode.
- Story Filters updates across all Report pages when added or modified in Edit Mode.
- Story Filters and Page Filters work together to refine datasets.
- If conflicting values exist, Page Filters take precedence.

Enhanced Reader Team and Writer Team Adjustments in Report page

Adjustment of Reader Team and Writer Team directly in the Report page is now possible. This enhancement enables a more flexible report management, making it easier to tailor access based on user roles.

Key Features

Reader Team and Writer Team Adjustments in Page
- Users can now define Reader Team and Writer Team for individual report pages directly in the General panel of a report page. This allows better control over who can view and edit each page, reducing the need for separate reports for different user groups.
New Fields in Page panel
- Reader Team: Select team(s) that can view the page from a list of all available teams.
- Writer Team: Select team(s) that can edit the page from a list of all available teams.
Enhanced Reusability and Efficiency
- Reports can now be designed for multiple teams without requiring duplication. For example: User A (Team: PagesGermany) and User B (Team: PagesUSA) can share access to the same report while only viewing their respective pages.
Improved Access Control
- Users can only view pages if their team is part of the Reader Team.
- Users can only edit pages if their team is part of the Writer Team.
Default Behavior for New Pages
- When a new page is created, it inherits the Reader Team and Writer Team settings from the overall report. This ensures a consistent access model without additional manual configuration.

Enhanced Grid Context Menu with Filter Management

An improvement in the Grid context menu is also introduced bringing more intuitive filter management options and improving user experience in handling reports. These updates align the Grid context menu with the existing Chart context menu and add exclusive options for reports.

Key Features

New Filter Management Options in Grid Context Menu
These options mirror the functionality already available in the Chart context menu.
- The context menu is accessible by right-clicking on a grid cell or header, presenting two filter options:
  - Add to Filters: Allows user to quickly add a selected field or value to active filters.
  - Remove from Filters: Removes the selected field or value from active filters.
- The Add to Filters and Remove from Filters options dynamically adjust based on the filter state:
  - If a field/value is already in filters, Add to Filters is disabled and Remove from Filters is enabled.
  - If a field/value is not in filters, Add to Filters is enabled and Remove from Filters is disabled.
Exclusive Grid Context Menu Filter options for Reports
These options provide greater flexibility in managing report specific filters.
- The Add to Page Filters and Remove from Page Filters options are available only for grids within Reports.
  - Add to Page Filters: Adds the selected field or value as a page-level filter, applying it globally across the page.
  - Remove from Page Filters: Removes the selected field or value from page-level filter.
- These options are disabled if the field/value is already in or removed from the page-level filters.
- Selections update immediately, and changes reflect across the entire Report instantly.

Introducing the "Insert Rules Element" Functionality

Insert Rules Element functionality is introduced for Reports, providing an intuitive way to add rule elements directly into Report pages. This enhancement streamlines rule-based operations and allows users to manage functions with greater efficiency as well as perform data simulation analysis.

Key Features

"Insert Rules Element" button
- A new Insert Rules Element button is now available and enabled in Edit Mode of report page. Choosing the button opens a "Create Rule Element" dialog.
Rule Element Selection and Configuration
- The dialog defaults to the current environment, though users can switch environments to select business functions from other environments as well. Functions which can be selected include:
  - Allocation
  - Calculation
  - Derivation
  - Transfer Structure
  - Currency Conversion
  - Unit Conversion
- Model Functions like for example Model Entity, Model Calculation, and Model Derivation are not included in the selection list.
Rule Management Features
- Once selected, rule elements are embedded directly into the Report page. The Rule Element grid consists of:
  - Rules
  - Input/Result
- Users can perform various actions on rules, including:
  1. Search for rules
  2. Select a rule
  3. Group rules
  4. Create new rules
  5. Delete existing rules
  6. Edit rules
  7. Run rules
Running Rules from the Report Screen
- Upon choosing Run, an Activity selection dialog appears. Once the selected Activity is Run, the results tab refreshes based on the chosen Activity ID.

Access Data Screen from Application Element in Reports

We utilize the Activities Application Element in the Report page to manage tasks and activities that need to be completed. Previously to review the data linked to an Activity, users had to navigate to the Activity and open the associated Data Screen via "Show Data".

Now it's even easier; users can directly choose "Show Data" within the Application Element – which enables user to jump straight to the Data Screen linked to the Activity.

Data Screen

Create homepage tile of selected Layout

Users can now save their created layouts in the Data Screen as a new tile in their homepage using the Save as Tile option.

In the Data Screen, choose Share dropdown.
Choose Save as Tile. Afterwards, a message that Tile is created will appear.

The created tile will be available in the homepage and once chosen, it'll automatically navigate user to the Data Screen of the specific layout.

Enhanced Inline Editing with Hidden Field logic in Data Screen

Improved inline editing functionality in the Data Screen is introduced ensuring consistency with Object Page editing logic. This enhancement provides a seamless experience when working with hidden fields based on conditional settings.

Key Enhancements

Consistent Hidden Field Logic Across Editing Modes
- When inline editing is enabled in the Data Screen, hidden fields will now follow the same logic as in the Object Page.
- If a field is configured to be hidden based on a condition, it will remain blank during edit mode.
Dynamic Hidden Field Behavior in Data Screen
- Pre-Save Visibility: When switching from Object Page to Data Screen, hidden records are initially visible.
- Editing Mode Behavior: When entering inline editing mode, hidden records will not be visible.
- Post-Save Visibility: Upon Save, hidden records become visible again, ensuring logical consistency.
Hidden Field Configurations in Object Page
- Users can configure hidden conditions in Adapt UI:
  1. Click on the three dots in the upper corner of a record.
  2. Define the conditions for hiding a selected record.
  3. Save changes.
- Hidden conditions apply only to the selected record, not the entire dataset.

That's a wrap for now!

Those are the new features and enhancements we have, and I hope it made you thrilled to further explore SAP PaPM Cloud UM. Stay tuned as we have more exciting releases in store.

Have fun modeling and see you again on the next one!

ShubhranshuP · ‎2025 Feb 14

Very Nice Blog and good introduction of additional features.

Can you please help with,

1. if the "Add to Filters" and Add to Page Filters" support selecting multiple Items from Grid and Filter ?

2. Does the "Enhanced Reader Team and Writer Team Adjustments in Report page" respects the Reader /Writer Team defined as part of Data Privileges ?

e.g:

- in a report with different Company Code details, I have defined a Writer Team called "RPT_WRITER"

- I have 2 different Company Code and 2 different writer Team Defined as part of Data Privileges. CC1_WRITER and CC2_WRITER.

Question: Now if i assign CC1_WRITER and RPT_WRITER to Person A, then he will be able to see the details of only CC1 or can see details of both CC1 and CC2.