Release Strategies Roles
What is the best practice for creating release strategies roles? My problem is that I was informed that we will be developing around 2000-3000 release strategies roles. But we only have around 1000 users in SAP.
I'm not in favor of this and would like to know the best way to approach this.
Thanks in advance!
i basically agree that there should not be more roles than users. But here we might just catch up with the exception.
Be sure to investigte why there are so many variants of the release roles. And also how solid is the release strategy. I have seen companies struggle with the concept which meant moving release roles from one user to an other user almost every day. If you would have build a role per user you would have to change the roles every day.
Divide the access request between release values and org values, than look at the way the org values are created and try to limit on all possible release values and all org variants the business is going to have. Be sure to ask for the users as well and which Releases each should have as you might see that not all possible variants will be needed !
Anyway the only real way to limit the number of roles will be to ask the business which combinations are going to be used. Normally i come to around 60% of the possible combinations
Former Member replied