SAP PaPM Cloud Standard Model – Introducing Team Collection

[nicalopez]

Hello dear SAP Community readers!

As part of continuous enhancements in SAP Profitability and Performance Management Cloud Standard Model (SAP PaPM Cloud SM) to be able to provide a seamless experience and flexibility to its users, let me give you the latest feature enhancement in the Teams application.

Currently, users can only assign one team as a Performer or Reviewer in process activities in Process Management which is somehow limited in case multiple teams are needed for process reviews. Apart from this, users still have to assign multiple teams across SAP PaPM Cloud SM applications such as Environments Access Management and in Reader/Writer team for analytic privileges. Even though this remains functional, users are seeking extra flexibility in teams management.

With the new implementation, users can now create a team collection that can contain  . This new feature is especially helpful when users are already part of a team but also need to be included in other teams for specific applications.

This also means that all the child teams will dynamically adapt the access or authorizations of their parent team. Furthermore, it gives the users the flexibility to assign multiple teams as a team collection to Performer/Reviewer in Process Management or Reader/Writer for analytic privileges instead of assigning multiple single teams. 

To show you this amazing new feature enhancement, let's start with the new UI in Teams application. Upon accessing the Teams screen, you will see the new column “Child Teams” in Teams panel. In the Child Teams column, it will simply display all the child teams of the parent team.

 

Creation of Team Collection

The creation of a team collection can be done by adding a single or multiple child teams to a Team.

To add a child team:

1. In the Teams application, select an existing team from the Teams list.
2. Choose the Edit button.
3. Under Child Teams section, click on the dropdown.
4. Choose one or more teams from the list.
5. Choose Confirm.
   
   Spoiler

   The child team added in a team will be automatically visible under the Child Teams column in the form of a hyperlink. Once clicked, it will allow the user to focus or display the specific child team.

After successful creation of a team collection, it is ready to be used in applications such as Environments Access as Authorized Teams, Reader/Writer teams for analytic privileges, and Performer/Reviewer teams in process activities.

The user can also add a new team collection as follows:

1. In the Teams application, choose the Add button from the Teams panel.
2. Define Name and Description of the team.
3. Under Child Teams section, click on the dropdown.
4. Choose team/s from the list.
5. Choose Confirm.
6. Optionally, the user can add users to the created team collection by adding users in Users panel.

The user can remove/unlink the child team from a specific team collection via the Edit Team button and simply remove the child team from the list. In any case, if all child teams of the team collection were removed, the team collection can still exist as a regular team.

To remove/unlink child teams:

1. In the Teams application, select an existing team collection.
2. Choose the Edit button from the Teams panel.
3. Under Child Teams section, remove the child teams.
4. Choose Confirm.Note: The removed/unlinked child teams will no longer have the access or authorization of the parent team and will just exist independently.

Adding Team Collection as child team:

In addition, a team collection can also be a child of another team or multiple teams, which makes it more versatile as shown below.

Note: Circular Parent-Child relationship is not possible wherein a parent team cannot be assigned to its child team (ex. Team X1 is a child of Team X and Team X is a child of Team X1).

Assigning and Managing Team Collection in Applications

Prerequisites: Create team collections.

For example:

Team Collection	Child Teams
TEAM A	TEAM1 TEAM2
TEAM B	TEAM3

Environments Access Screen

The created team collection can now be used as Authorized Teams in private environments.

1. In the Environments Access screen, choose an environment.
2. Choose the Edit Access for Environment(s) button from the header.
3. Choose Private, then assign TEAM A as Authorized Teams.
4. Choose Confirm.

In this scenario, parent TEAM A with child teams TEAM1 and TEAM2 will have access to the private environment, while TEAM B will not be able to see the private environment.

Note: Users should not have ENVIRONMENTS_ACCESS_ALL role.

The parent TEAM B with child team TEAM3 will not have access to the private environment.

Reader and Writer Teams in Master Data with Analytic Privileges

The created team collection can now be used as Reader and Writer in master data with analytic privileges.

1. In the Modeling screen, choose a Characteristic field with master data.
2. Assign the team collection as Reader and Writer in master data values as per below.
   
3. Choose Save. 
4. Access the Input/Output activity (Editable Query).

In this scenario, TEAM A will be able to view and update on the data rows with CUST1, CUST2 and CUST3.
While TEAM B will be able to view and update on the data rows with CUST4 and CUST5. Users that are not part of the Reader and Writer is expected to not see any data rows.

For more info, you may visit related blog post SAP Profitability and Performance Management Cloud: Analytic Privileges

Process Management

The users can have the capability to assign multiple teams in a team collection and assign as Performer and Reviewer in process activities. The teams that are part of the performer and reviewer will also receive the email notifications for every activity action.

1. In the Process Management screen, choose or create a process instance.
2. Assign team collections below in all process activities.
   Performer: TEAM A
   Reviewer:  TEAM B
   For example: 
3. Choose Save.
   

   Note: The users that are part of the team should enable Email Notifications via User Preferences to be able to receive emails.

In this scenario, users part of TEAM A (Performer) can perform Submit activity and users that are part of TEAM B (Reviewer) can perform Reject/Approve the activities.

1. User part of TEAM A (child team: TEAM1) can perform submit and receive email notification.
2. User part of TEAM A (child team: TEAM2) can perform submit and receive email notification.
3. User part of TEAM B (child team: TEAM3) can perform approval and receive email notification.

If you want to learn more about dual control mechanism in SAP PaPM Cloud Standard Model, you may visit this related blog post SAP PaPM Cloud Dual Control Mechanism & Process Instance Filtering

For more information, you may check our Standard Model Application Help: Teams 

That’s it! I hope you find this new feature enhancement useful and your work with SAP PaPM Cloud Standard Model better and stay tuned for more related blog posts, you may also check the same feature in SAP PaPM Cloud - Universal Model via SAP PaPM Cloud Universal Model: What’s New as of 2024-12-12?

See you on the next one!