If you want to avoid the limitations of derived roles, such as for example when this does not hold true...
The difference in these roles is only by different organizaiotnal levels.
... then a usefull trick is also to ensure that all menu transactions in the series of roles have intact authorization proposals (no changed fields or deleted objects) and identical menus and the new change creates ideally only standard authorization instances.
--> They you can use SUPC to jump into each of the menues once and re-import the menu from the first role you change and then read new / merge old once as well. You can then mass generate the profiles for the lot in one go.
This is a little bit more work than derived roles but without all the other disadvantages.
Cheers,
Julius
