SAP GRC 10.1 EAM - Design Gap - How to address?

[former_member187795]

Hi GRC Community,

We are using SAP GRC 10.1 EAM and we have seen that there is a design gap in the existing functionality and this is causing issue with the review of logs by our controllers. Just wanted to know experts advise on how the design gap can be effectively handled using any work arounds.

Steps in EAM end to end process:

1. User requests for FF ID to use Tcodes A, B and C based on a Incident (ticket)
2. FF ID Owner reviews the incident details and grants FF ID access to the user
3. User logs in to FF session and mentions to use Tcodes A,B,C,D and E and uses all mentioned Tcodes.
4. Controller when receives the log review workflow will review based on what user has mentioned in the planned activity field and not based on what was requested.

As mentioned above, user requested to use Tcodes A,B,C but used Tcodes A,B,C,D and E. So, the review performed by controller logically is not correct. Is there any way to link FF ID request number with log review which will make the controllers job easy for reviewing the logs.

Appreciate your thoughts on this.

~ Sai

[madhusap · Accepted solution]

Hi Sai,

I understand your query and if your intention is that reviewers have trouble identifying what was requested and what was used in the FF session then may be you can create FF IDs specific to Tcodes or specific to your incidents based on your tickets trend analysis which may result in the creation of lot of FF IDs but will be helpful for reviewers as they no need to worry about what was requested since the access was already limited to the Firefighter ID itself. (I too feel that there should be link between FF ID request to Log review but since it is not available in standard design, may be you can consider this option if it is feasible).

Regards,
Madhu