on 05-13-2015 4:14 PM
Hi Experts!
System: GRC AC v10 SP14
When I transport a ruleset the first time to our GRC Production system using GRAC_RULE_TRANSPORT , I must regenerate the ruleset. This creates the new generated rules and the unique rule IDs. Now, I have made a change to the ruleset in GRC Development and want to transport the ruleset through the landscape to GRC Production using GRAC_RULE_TRANSPORT. Do I:
Need to Regenerate The Ruleset again in GRC Production? (I know the answer to this is probably yes)
Once I Regenerate the Ruleset again in GRC Production, will the unique Rule IDs change?
Is there a better way to do this besides having GRC Production ruleset that is changed through GRC WF approvals and never transported across the GRC AC Landscape?
Thanks,
-john
Hi John,
Depending on how many Functions you have changes and corresponding Risk IDs affected you can just generate rules for those risk Ids in production after transport from DEV.
But when you are transporting from DEV make sure to uncheck the checkbox "Include All Action Rules".
By this way your existing rules doesn't get changed and for the risk IDs to which you made changes you can generate the rules.
To enable the option to "Include All Action Rules" with GRAC_TRANSPORT_ACCESS_RULES program implement below SAP note:
2007158 - Generated Action Rules are not transported
Regards,
Madhu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
As per my understanding on rule generation logic from the program level, when you try to generate the rules 2nd time rule IDs will be created/disabled for the modified objects in the ruleset level. no change will happen for non modified objects.
Also there are only 2 methods for maintaining the ruleset in prod 1) change in dev and then move to prod using transport/import-export 2) directly change in prod with WF but this still needs to be imported to non prod GRC systems.
Regards,
Venkata Bavirisetty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.