Segregating Releasing of Projects

[Former Member]

Hi

Does anyone know of a way to segregate the authorisations/user access of releasing a project (at project definition level)? We have an audit requirement to segregate this action.

I had thought that using a user status profile would allow this segregation but this does not prevent the end user changing the system profile (it only prevents the user changing the user status).

Thanks

[Former Member]

hi,

you could use authorization profile..

create an authorization profile which does not allow release of project (PFCG)

attach to user(s) (SU01)

BASIS consultant usually maintains these..

revert for follow up questions

[Former Member]

Hi Ramesh

I have already looked at the authorisation objects for PS, and there does not appear to be an auth object which 'controls' the system status (or to which system status the project definition can be moved to).

Thanks

[Former Member]

hi acorn,

hmmmm, seems you're right.. -will check again..

anyway you can however prevent/disallow release (system status) based on user status. (meaning once a certain status is set, release is not longer possible) and you can create authorization for setting of user status..

kindly revert if this wont work for you..

regards