topic Re: MM Release Strategy Security Question in Application Development and Automation Discussions

MM Release Strategy Security Question

Former Member — Wed, 25 Nov 2009 08:34:25 GMT

Hello,

We have a rather complex release strategy.

We have 41 different release groups and 8 different release codes.

We have 56 different people who need the authorization to release POs.

We are trying to set up the security around all this using the authorization object M_EINK_FRG... and needless to say, this is turning out to be quite a bear.

Since each user (who is allowed to release) needs access to different release groups and different release codes, we are going to have to set up roles specific to every user.

This is going to be a maintenance nightmare.

Are we doing something wrong?

What is the best practice for this?

Thanks,

Anisha.

Re: MM Release Strategy Security Question

Former Member — Wed, 25 Nov 2009 09:04:57 GMT

Hi Anisha,

using the authorization object M_EINK_FRG

we are going to have to set up roles specific to every user

There is nothing wrong in this.

We can create each role for each user.You can carryon.

Thanks & Regards,

Nagendra.

Re: MM Release Strategy Security Question

Former Member — Wed, 25 Nov 2009 10:07:08 GMT

Hi Aninsha,

This is very common when you have complex release strategies.

The effort in maintaining this is less than putting in a development to automate the process so I would stick with what you have.

Re: MM Release Strategy Security Question

Former Member — Thu, 10 Dec 2009 00:05:38 GMT

I assume you are using Derived roles which is common for MM relase group/code security roles. That should make it easy.