Inactivated Auth objects get deleted in Parent role post creation of derived role using BRM:

[former_member272370]

Hi Thr,

The below is the issue we have encountered and attempting to fix. Please update your inputs at the earliest.

When any authorization object is inactivated in the parent role and if we then create a new derived role using the BRM, than the authorization objects in the parent role get deleted automatically. (we can see this when we see through the Target system > PFCG > Change authorization data to replicate

the issue.

[former_member204479 · Accepted solution]

Hi Arun,

Also Please take a look at 1903792 - BRM - Problem when Propagate Derived Roles. This might solve the issue.

Thanks,

Sammukh

[former_member272370 · Accepted solution]

Thanks Sammukh !

Implemented the note and the objects do show up in the parent roles now.

Cheers

Arun

[former_member272370]

Hi All,

We have made progress by implementing the below notes accordingly.

Note: 1903792 - BRM - Problem when Propagate Derived Roles (in GRC) ----> implemented to fix the issue ---> When any authorization object is inactivated in the parent role and if we then create a new derived role using the BRM, than the authorization objects in the parent role get deleted automatically.

Note: 2002343_ Manually added custom objects are coming up as standard.(in ECC) ---> Implemented to fix the issue ---> Manually added custom objects are coming up as standard

However post implementation of the 2002343, we now have a new issue  "Some of the standard object getting manual" .

Please update your views on why / how this can be fixed.

Regards,

Arun

[alessandr0]

Hi Arun,

does this happen during role generation in BRM? Are you on AC 10.0 SP13?

Regards,

Alessandro

[former_member272370]

Hi Alessandro,

Yes. This issue happens during role generation is in BRM. We are in AC 10 SP10.

Regards,

Arun

[alessandr0]

Hi Arun,

we had a similar issue with manually added objects in role generation phase. Not sure wheather this is also applicable to you. May you have a check in the note: http://service.sap.com/sap/support/notes/2002343

Hope it helps.

Regards,

Alessandro

[former_member272370]

Thanks for your attempt to help out !

The note was more appropriate to our situation.

1903792 - BRM - Problem when Propagate Derived Roles.

Thanks

Arun