SAP provides a free add-on in PS to the standard SAP ERP application. The add-on doesn’t belong to the standard SAP functionality, but can be used together with the standard SAP functionality. The support of this add-on, however, is not part of the standard SAP support. You need to install the add-on yourself. The programs have been approved by SAP, but if you have questions or problems with the functionality, then you need to pay for support.

Implementation

General Principles

Figure 1 shows the standard SAP transaction to maintain partner roles. This transaction can be found within customizing following menu path project system > Structures > Operative Structures > Work Breakdown Structure (WBS) > Define Partner Determination Procedures and Roles > Definition of Partner Roles or start transaction OPSPAR1 directly. In the NoTpe column, the partner type is visible.

Figure 1

Partner roles

Also, when you process the additional transaction codes, only the standard SAP authorization is checked. The additional authorization is not used in these transactions.

Additional Transactions

ZWPS_AUTH_1 (Partner Role Authorization)

This transaction enables you to define per object which authorization belongs to a specific partner role. After you execute transaction code ZWPS_AUTH_1, the overview screen appears (Figure 2). On the right side of this screen, you can see the partner roles, and on the left side, you see the authorization objects.

Figure 2

The overview screen for partner role authorization

You can define the authorization per partner role. Select a partner role and double-click an object to maintain the authorization. In my example I select 14 Team Member and double-click the Project Definition folder. Figure 3 shows an example of what this configuration looks like for a team member. A team member has authorization for activities 03, 22, and 61. As roles are freely definable, you must define the authorization for all the partner roles you have set up. These are all display activities. Table 1 lists these display activities and explains what they are.

Figure 3

Authorization team member

Figure 4

Authorization for a project member

ZWPS_AUTH_2 (Maintain Partner Role Description)

Figure 5 shows an example of a changed partner role description. To add new entries, click the New Entries button.

Figure 5

Maintain the partner role description

ZWPS_AUTH_3 (Change User)

Figure 6 shows an example of this transaction. In this case the team member (partner function 14) KVANWEST is replaced by LVANWEST for selected projects, and because of the inheritance functionality, the replacement of KVANWEST by LVANWEST is also made for the allocated WBS elements.

Figure 6

Mass change to the partner role

ZWPS_AUTH_4 (Insert Partner Role in Project Definition)

Another example is the possibility to give users in a development environment access to all relevant projects. Figure 7 shows an example of the transaction whereby user ID KVANWEST is added to all projects whose numbers start with E. The partner role is safety coordinator (partner function 13).

Figure 7

Insert the partner role in project definition

ZWPS_AUTH_5 (Define Substitute)

At the bottom of the screen in Figure 8 you can see the choice between defining and deleting a substitute.

Figure 8

Define the substitute partner role

Report ZWPS_CHANGE_PROJ_PARGR (Change Partner Determination Procedure)

Figure 9 shows that for all project definitions having project profile KVW1, the partner determination procedure must be set to KWP. Be aware that this report can be started only by using transaction codes SA38 or SE38. In many SAP production environments, only a few users have authorization for these transactions. Also, mass change transaction CNMASS cannot update the partner determination procedure.

Figure 9

Mass update partner determination procedure

Additional BAdIs

The implementation of the project authorization based on partner roles enables you to give users project authorization based on the roles they have in the project. It is not a replacement of the standard SAP authorization; it is merely an extension of the authorization. The implementation is done by implementing the enhancement CNEX0002 as described in SAP Note 638781.

Kees van Westerop

Kees van Westerop has been working as an SAP consultant for more than 25 years. He has an MBA degree in mathematics and a degree in finance. Kees has been concentrating on the financial modules, especially in general ledger accounting, cost center accounting, and consolidation. He also has a great deal of experience with rollouts of kernel systems and integrating finance and logistics.

You may contact the author at keesvanwesterop@hotmail.com.

If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.