Mass Role Creation

[Former Member]

Hello,

We need to create som 800 new roles in a single system for our go-live support. could you please provide me with best possible solution to do this hence I reduce the manual effort and save time?

Thanks in Advance for your response.

Regards,

Jeevan.

[Former Member]

Best possible solution is to seriously question why you need 800 roles to support a golive. In all seriousness that is a daft requirement which is solved by a redesign of support roles.

Addressing the symptom but not the problem, you can use eCATTs (lots of tutorials on the internet) to automate lots of your manual tasks in the role build but that does depend on your design (single roles 'vs' derived roles, creating new roles from scratch, copying existing roles & updating with new org data etc).

[Former Member]

The only scenario that i can think off is a Country rollout where seperate role sets are required for large organisations...which are based on their template roles but the org levels change based on the country where SAP is going live.. If the go live is such a big deal involvign 800 roles, and 1000 of users, i would say go for custom development which should be useful for any future rollouts... in general, the Org values are fed into a table and custom programs are used to replicate them to various child roles or new roles... if that is a difficult route, as suggested by Alex and Raghu go for ECATTS...

~Sri

[Former Member]

Hi Jeevan,

As mentioned by Alex, you can use ECATT scripts to create the roles. But, you should understand that automatic maintenance of values is not possible using eCATT scripts. The only task that you can achieve quickly is create the role, and generate the profile for it.

Also, as highlighted by Alex, why do you need 800 roles??? May be you can look at the role design and remove some of the roles. The best recommended approach is creating roles based on business processes and then tagging them to Job roles (composites). This way you can minimize the role count to the maximum possible.

Regards,

Raghu

[Former Member]

Dont you think that 800 roles for a single orgset of roles for an entity is a symptom of some design error in the role concept?

There are several ways to anaylze roles and assignments to (re)compute optimate role builds, but much like the initial task it is an art form.

Just curious: how many users will need these 800 new roles?

Cheers,

Julius