on 09-30-2009 12:11 PM
Dear All,
CJ20N is being used by many users. At present all the users who has access to CJ20N can Release the created projects (change its status). Now we need to restrict this, so that only authorized users would be able to release the created projects. How can we do this?
Do we need to create a new role for this, if yes what object should be included in the role.? Please help.
Thanks.
Create User Status Profile in Tcode: OK02
While defining the Usersatus profile you can forbid the status which you want to control for example Release.You will be selecting Object types(Project definition, WBS, Network) also in this Customisation. In our case we have Forbidden the Partial release status also, as forbidding only Release status may permit partial release of Project definition or WBS element.
Define the authorisation Key in Tcode BS52
You can create the authorisation key based on your requirement and the number of Userstatus you have defined in your User status profile.
Default User status Profile in Project Profile & Network profile in OPSA & OPSC (Based on the object types you have selected )
To control the authorisation the object to be used in Tcode PFCG is B_USERSTAT.Here you can control the Authorisation key , object category of the Userstatus profile based on the role you define.This step is to be executed by BASIS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As an alternative, You can use user status for this. Forbid release for some user status and allow release for next status level, You can give authorization for changing the user status for a group of person who has the authority to release the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For Example Have two user status, one as PLAN - and other as EXEC. Set the initial status as PLAN. click object types and select Project Definition. Give an authozisation key for both user status profile(Authorization key to be created separately)
Double click PLAN status, select forbid button for Release. then select EXEC status and select allowed button for release.
Assign this user status profile to the project profile.
Inform your BASIS about these Authorization keys and who should have which authorization key.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.