Hello again SAP Community members!
Days and months are coming fast, and now we’re in the Q2 of 2024 and of course, I’m delighted to introduce you to another wave of new features and enhancements in SAP Profitability and Performance Management Cloud Standard Model (SAP PaPM Cloud SM)!
If you want to revisit all the blog posts released from my colleagues, you can check this tag for easier reference: https://community.sap.com/t5/tag/PaPMCloudSMWhatsNew/tg-p
Without further ado, let me walk you through the newest additions that are now available, and you can already experience them in your SAP PaPM Cloud SM tenant:
System > History Monitor
The History Monitor view has been enhanced to have a user-friendly and transparent view so that the users will understand the context which the changes were made in.
Starting from the left side, the column sequence starts with Entry ID, Environment, Version, Function, Function type (newly introduced history details), Description, History Type, Time (previously named Local Timestamp column) and User GUID.
The Function type column is newly added that displays the function type identifier. For example, AL stands for Allocation and it means that the changes is within the Allocation Function (All Allocation Function Types). Here are the other Function Type identifier:
- Calculations (All Calculation Function Types) = CA
- Calculation Unit = CU
- Condition = CD
- Conversions (All Conversion Function Types) = CV
- Derivation = DE
- Description = DS
- Joins (All Join Function Types) = JO
- Model Join = MJ
- Model Tables (All Model Table Function Types) = MT
- Model Views (All Model View Function Types) = MV
- Queries = QE
- Remote Function Adapters (All RFA Function Types) = RF
- Transfer Structure = TR
- Views = VI
- Writers = WR
Additionally, a new feature was introduced wherein the user can compare the two (2) chosen environment basing on their history version entries in the History Monitor screen.
A new button namely “Compare” is added in the Tools Header button. This will be enabled once a history log version is selected in the History Monitor list (multiple selection is also applicable).
Upon clicking the Compare header tools button, the “Selected history versions:” pop-up dialog box will be prompted that will show the history log versions selected on the list that will be compared.
In order to compare History Log versions, two (2) log entries should be selected in the “Selected history versions:” pop-up dialog box.
If only one (1) history log version is selected in the History Monitor list, in the “Selected history versions:” pop-up dialog box, the message “Select next version to compare” is prompted and the COMPARE button is disabled.
If more than two (2) log entries are selected in the History Monitor list, in the “Selected history versions:” pop-up dialog box, the multiple history logs selected will be displayed that allows the user to choose which history log version will be compared. However, the user is only allowed to select only two (2) history logs to be compared.
Note:
If the user wanted to select the 3rd history log version in the screenshot, the user needs to unselect first the one of the selected and then select the desired history log to be compared.
Once the selected History Log versions are finalized, COMPARE button is now enabled and upon choosing the button, the user will be able to open a new screen namely “Comparison”.
In the Comparison screen, it will display two (2) panes which are for the two (2) history version logs highlighting the code line sections with differences.
User Preferences > System Language
The new language Korean ‘KO’ has been added to the User Preferences > Language section that allows the users to change the language to Korean.
To learn more about the available languages in the User Preferences > System Language section, please visit the Application Help Portal through this link.
Business Events Management
During modeling there are various ways for the user to make a mistake which will be reflected into execution of function. All business events, erroneous data or any kind of error that occur during execution of activities can be seen using a Business Event Management Screen (BEM).
Previously, only users with most powerful role EXECUTION_MAN_ALL were able to see business events indicator in the Process Management screen, since they are the only one authorized to access Business Events Management Screen. Now, since users with role EXECUTION_USER_ALL can also access Process Management screen, which is prerequisite for business events management screen, business events indicator will also be available for them if user is part of performer or reviewer group (at least of one activity) as well as accessibility to Business Events Management Screen.
The user will be able to see business indicators beside the execution activity if there are errors or unassigned items. Business Events Indicators are displayed as clickable red circles:
In the Business Event Management screen, there are still some authorizations that are limited for users with EXECUTION_USER_ALL role depending on if the user is part and not part of the Team assigned to an Input/Output Activity and Execution Activity.
Scenario 1: User is assigned as Performer and/or Reviewer Team in the Input/Output Activity only
If the user with EXECUTION_USER_ALL role is only part of the Performer and/or Reviewer Team of the Input/Output Activity only, the Actions > Go to buttons Show, Analyze and Initialize are enabled and the user can access the mentioned screens.
However, the Run and Restart buttons are disabled as the user is not part of the of the Performer and/or Reviewer Team of the Execution Activity.
Scenario 2: User is assigned as Performer and/or Reviewer Team in the Execution Activity only
If the user with EXECUTION_USER_ALL role is only part of the Performer and/or Reviewer Team of the Execution Activity only, the Header Tools button for Run and Restart and Actions > Restart button are enabled, and the user can run and restart the activity.
However, the Actions > Go to buttons Show, Analyze and Initialize are disabled as the user is not part of the of the Performer and/or Reviewer Team of the Input/Output Activity.
Scenario 3: User is assigned as Performer and/or Reviewer Team in the Input/Output Activity and Execution Activity
If the user with EXECUTION_USER_ALL role is part of the Performer and/or Reviewer Team of the Input/Output Activity and Execution Activity, the Actions > Go to buttons Show, Analyze and Initialize are enabled and the user can access the mentioned screens. And also, the Header Tools buttons for Run and Restart are enabled and the user can run the activity.
Scenario 4: User is not assigned as Performer and/or Reviewer Team in the Input/Output Activity and Execution Activity
If the User with EXECUTION_USER_ALL role is not part of the Performer and/or Reviewer Team of the Input/Output Activity and Execution Activity, the Actions > Go to buttons Show, Analyze and Initialize are enabled and the Header Tools buttons for Run and Restart and Actions > restart are disabled.
I sincerely hope that these latest additions will be helpful and give you better SAP PaPM Cloud SM experience.
Furthermore, feel free to share this with your colleagues and stay informed with the latest news for SAP PaPM Cloud SM by following the below SAP Community tags:
Thank you and see you on the next What’s new series! 😊
- SAP Managed Tags:
