GRC AC5.3 - SPM issue - IMPORTANT

[Former Member]

Dear Colleagues,

I hope you can help us, a prospect of our asked the below questions:

When using the SPM (based on FF ID) and approving a PO as part of the release strategy in MM, the user that is logged as entering the approval is the FF ID.

The requests are:

1. The user name shown as the approver will be the real username that used the FF ID to approve the PO (not the FF ID).

2. The FF ID owner (from the SPM) will be mentioned also so eventually the user that will be entered in the log will be USER X on behalf of manager/owner Y.

For example, the current situation is:

FFID used for PO approval - FF_MM

User assigned to the FF ID - SHIRAC

Owner of FFID - IRITS

Now - The user entered in the MM log as an approver is FF_MM.

The requested situation is that the user entered in the MM log as an approver - SHIRAC/IRITS (or in any other possible way that will show both users).

The suggestions offered to the customer and the customre's responses were:

1. The FF ID resolution will be in the same resolution as the user (only in cases when this is critical and the FFID is assigned with roles of approval) but this solution seems to be not acceptable to the customer since he does not want to duplicate the users and maintain them in parallel. This solution also requires that the username will be part of the FF ID name. this also does not answer the need to see the owner in the log.

2. To run the LOG REPORT in SPM to view who was the user that used the FF ID in the specific time and maybe add the owner field to the report so they will have all the data they need in one report. The problem with this solution is that the managers that need to approve the PO based on previous approvers won't have authorization to SPM and need to see it while reviewing the PO and approvers in the ECC.

Logically it is right to see the user that approved the PO but in the log we see only the FF ID with no indication of who really approve the PO and on behalf of whom.

We will appreciate if someone could assist what to advice our prospect.

Thanks in advanced

Rothem

[Former Member]

Hi Rothem,

The PO approvers don't need access to SPM cockpit. They just need access to report /VIRSA/ZVFAT_V01. To avoid unnecessary access to SA38 a developer could customize the report according to your customer needs and then make a transaction out of it.

One better solution I think is to use the Reason/Activity report (/VIRSA/ZVFAT_U03). It could be used like this:

Reason Code: PO-Approval

Reason: SHIRAC/IRITS

Activity: 45000001 approved

Good luck,

Vit