05-05-2015 2:32 PM
Hi!
due to the implementation of the new G/L we have to adjust lots of authorization roles ....
We have changes related to a high number of roles quite often.
We are using already derived roles....this is only helpful if you want to add new transactions - it does not help for new authorization-objects. Isnt it?
Any ideas on how to make a mass change?
Table MASSFUNC maybe, or is there already a mehtod existing.
thanks in advance.
05-06-2015 6:05 AM
Hi Florian
We are using already derived roles....this is only helpful if you want to add new transactions - it does not help for new authorization-objects
You can add an object into the parent and propagate to derived roles. However, as Julius has mentioned, you should aim to utilise SU24 as much as possible.
If you are doing constant changes it sounds like an opportunity to build your roles from the start and build them clean. Put the time and effort into refining the SU24 proposals so PFCG becomes less time-consuming to maintain.
Do you have changes to a high number of roles due to new requirements? Part of this might also be rationalising your role design (e.g. reduce the number of roles with same transaction and so on).
Regards
Colleen
05-05-2015 8:42 PM
The solution is to have less roles but therefore more robust ones. Then you can either easily add the new G/L tcodes or if the user anyway cannot see the menu then bold the new G/L tcodes and objects onto the old G/L tcodes in SU24 and simply merge all the roles.
If you have lots of little roles without connect to their SU24 proposals (manual or changed or not merged), then there is no real solution and any trick should not continue to support such a design in my opinion. Some might suggest eCatts for it, but that is also your problem and I do not recommend it for PFCG. Others might suggest even more little roles ontop of the already many little roles, which I do not recommend either.
Cheers,
Julius
05-06-2015 6:05 AM
Hi Florian
We are using already derived roles....this is only helpful if you want to add new transactions - it does not help for new authorization-objects
You can add an object into the parent and propagate to derived roles. However, as Julius has mentioned, you should aim to utilise SU24 as much as possible.
If you are doing constant changes it sounds like an opportunity to build your roles from the start and build them clean. Put the time and effort into refining the SU24 proposals so PFCG becomes less time-consuming to maintain.
Do you have changes to a high number of roles due to new requirements? Part of this might also be rationalising your role design (e.g. reduce the number of roles with same transaction and so on).
Regards
Colleen