Roles in GRC returning from Production to Development automatically

[DG2323]

Hello!

How can I avoid the roles in GRC returning from Production to Development status every time I update any other field and save the changes?

Every time I update any field in a role, such as Role Owner, it returns to Development status in the Provisioning tab. And I have to update manually to Production status again. This happens when I update the role from NWBC -> Access Management -> Role Search.

#GRC #Access Control #Role Management

[dyaryura]

Hi

This was handled with a parameter (3005) in older versions of GRC. Check https://me.sap.com/notes/0002422525

This now works giving you the option to reset or not the methodology if you use the Role Mass Maintenance only.

Once you choose the role and the owners to be updated you have the option to configure "reset methodology=NO" if you have your parameter 3005 configured.

Thanks

Diego

[Ra32]

Hello Diego,

unfortunately this only works in AC 10.0 and 10.1.

In AC 12.0 the parameter can be set to NO and will still be ignored.

Regards

[dyaryura]

This parameter also works in 12. you can check the help guide of GRC 12: https://help.sap.com/docs/SAP_ACCESS_CONTROL/6c75bb80954e4543b4a4dfb68d6a4998/c03e3e90c45141d7bb870f...

[Ra32]

It works for not resetting the methodology, yes. But the role will still be set into the status Development.

[dyaryura]

what I mean is that you can use the "mass maintenance" instead of the single rol maintenance to update the role owners. if you do so, your role won't get back to Development phase when changing the Role owners. As mentioned in the note this was previouly used in the "normal" single role maintwnance but removed afterward and only possible as part of the mass maintenance

[DG2323]

This issue is coming in single role maintenance. I have updated the parameter 3005 to NO and the role keeps returning to Development after the update. I even have parameter 3004 (Default Role Status) as PRD.

[Ra32]

I would be very interested in a possible solution as well.

We are currently using a workaround which consists of making every role status productive in SPRO customizing. However this is suboptimal.