why derived roe?

[Former Member]

hi all

i am ramesh, i have a doubt for so many days. that is in which kind of environment we use derived role?

[Former Member]

In general it is best suitable for large companies especially when a lot of BG's or countries with specific OrgLevel needs are involved, Maintenance wise it save

s a lot of time. Hope this answers your question?

[Former Member]

Hi ramesh,

I hope this example will clarify your doubt.

xxx organization maitainning different plants on diffrent locations like birla cement having plants on entaire india.

For each plant maintanence thay required manager.

Managers roles will be same but plants numbers are diffrent.

We can create a role and we derive n number of roles differ by the organization levels(plant no's).

i hope it will help you.

kiran kumar.v

[manohar_kappala2]

Say in ur organization

There is a role with some tasks. Now these are 10 distinct locations with the same activity but since they are distinct so they will have different Organizational Level values...

If you were to create Separate single roles then u needs to create 10 different roles. further going forward if there are another 10 distinct entitiies being added then u have to again go for another ten and so on. And also to make common change acroos all the roles then u need to modify each role separately. To overcome this inefficinecy in role maintainence SAP has come up with Master Derived Roles.

In this new approach u built one Master Template(master role) and make others copies of this role with only the Org Level field values being different. This reduces the administration of the roles and easy to maintain and monitor and extend going forward with addition of new tasks and org levels...

This is where Derived roles come handy...

hope this helpss...

Cheers

Manohar

[former_member190272]

Hi ramesh kaluri

Derived roles refer to roles that already exist. The derived roles inherit the menu structure and the functions included (transactions, reports, Web links, and so on) from the role referenced. A role can only inherit menus and functions if no transaction codes have been assigned to it before.

The higher-level role passes on its authorizations to the derived role as default values which can be changed afterwards. Organizational level definitions are not passed on. They must be created anew in the inheriting role. User assignments are not passed on either.

Derived roles are an elegant way of maintaining roles that do not differ in their functionality (identical menus and identical transactions) but have different characteristics with regard to the organizational level.

The menus passed on cannot be changed in the derived roles. Menu maintenance takes place exclusively in the role that passes on its values. Any changes immediately affect all inheriting roles.

You can remove the inheritance relationship, but afterwards the inheriting role is treated like any other normal role. Once a relationship is removed, it cannot be established again.

Thanks & Regards

Pankaj Kumar

[Former Member]

Also remember, once user assigned to composite role, he will get access to all the child roles and the respective access.