ChaRM question about authorizations

[Former Member]

Dear all,

I have some question about the ChaRM process and related authorizations.

I would assume the following:

1. Requester should be able to send to validation
2. Requester should not be able to "release for approval"
3. Change manager should be able to send to validation
4. Change manager should be able to change project and solution
5. Developer should be able to "Pass change to test" in Change Document
6. All ChaRM users should be able to send email from "More" button in ChaRM

We copied the following standard comp roles and their single roles to customer namespace and assigned to users:

SAP_CM_REQUESTER_COMP

SAP_CM_CHANGE_MANAGER_COMP

SAP_CM_DEVELOPER_COMP

SAP_CM_TESTER_COMP

SAP_CM_OPERATOR_COMP

SAP_CM_ADMINISTRATOR_COMP

However the above assumption doesn't work. I would firstly ask, if I made some wrong assumption, secondly, how they can be correct.

Our Solman is 7.1 SP7.

Thanks!

[Former Member]

hi

Please refer the usecases here, similar to yours

http://wiki.sdn.sap.com/wiki/display/SMAUTH/UC00030

http://wiki.sdn.sap.com/wiki/display/SMAUTH/UC00043

http://wiki.sdn.sap.com/wiki/display/SMAUTH/UC00044

Thanks

Jansi

[former_member245797]

To add more, the exact authorization object controlling status is B_USERSTAT.

Check for this object in the role and maintain appropriate AUTH KEYS based on your needs

~Waseem

[Former Member]

Hi ,

ChaRM role are working with concept of authorization key, every status gas it own authorization key.

Please answer below question,

1.Are you using custom transcation type for Rfc ( ZMCR or YMCR) . if not plz create it

2. mapped the Authorization code in status profile

3. add the authorization code in role depend upon usage.

4. map the custom status profile (ZMCRHEAD or YMCRHEAD) in thr role.

5. remove the remaining authorization key in the role.

it will help to get proper status change by the user in Rfc.

Rg,

Karthik