Error - User status could not be set because of the status profile customizing

[Former Member]

Hi.

I'm currently testing CHARM in Solman 7.1.

After I approved the ZMCR (Request for Change) and released for development, the system has created the ZMHF (Urgent Change). I entered valid value in the developer and tester fields and when I saved the document, it displayed error "User status could not be set because of the status profile customizing". It actually saved the document even there was an error.  I exit the screen and try to display the ZMHF document again, but the error is still there.

I didn't change anything in the configuration of the ZMHF status profile after I copied from the standard SMHF status profile.

Has anyone got any idea why I get this error?

The status of the document is still "Created" and I'm not setting the status yet to "In Development".

Thanks,

Tess

[Former Member · Accepted solution]

Hi Tess,

I am also now getting the same error when trying to Release for Approval. This was working fine previously. The only thing I changed was implementing an Approval Procedure. For now I am not using the newly created Approval Procedure. The user has SAP_ALL but I need Security to update the roles with the B_USERSTAT object to have Status Profile * instead of specific values.

Thanks,

Shawn

[Former Member · Accepted solution]

Thanks for all your suggestions.

I have already resolved this issue by adding auth object B_USERSTAT with auth key "SMHF_00" (status=Created) to the test userid (developer) who is entering/assigning the developer/tester fields.

The Change Manager userid has this access that's why I don't get this error when I tested using the Change Manager userid to assign the developer/tester.

Regards,

Tess

[viktor_misurak]

SAP Note 1805404 - Creating MOpz transaction returns "User status could not be set because of the status profile customizing"

User creating MOpz requires roles SAP_MAINT_OPT_ADMIN and SAP_MAINT_OPT_ADD

[Former Member]

Hi, Teresita.

Please, check whether you have authorizations for setting status "In development".

Best regards,

Artem

[former_member206552]

Hi Teresite

As suggested by Artem check the authorizations, as a test you can assign SAP_ALL to the ID and test again to see if the problem I solved. as per http://scn.sap.com/thread/3199950

you can assign the authorization object called B_USERSTAT.

http://www.consolut.com/en/s/sap-ides-access/d/s/doc/YV-AI_CRM_CM_MESSAGE070

Best Regards

Marius

[Former Member]

Thanks for your reply, Marius and Artem.

I have already tested with userids that have SAP_ALL, but I'm still getting the error. I also ran the authorization trace but I cannot see any error in the trace file.

I noticed that I'm only getting this error on ZMHF documents that were created by the test user ids  (ie. Change Manager test user). The test user ids  don't have SAP_ALL.

The ZMHF documents that I created using my userid (with SAP_ALL) doesn't show this error.

Regards,

Tess

[Former Member]

Hi,

SAP_ALL doesn't work with solution manager scenario specific capabilities.

You need to assign the specific auth. Could you please check your status profile name and auth key restrictions on B_USERSTAT

you can find the better use cases here

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

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

Thanks

Jansi