topic Re: Dispute Management Authorization error in Application Development and Automation Discussions

Dispute Management Authorization error

Former Member — Wed, 22 Dec 2010 17:03:24 GMT

Hi guys,

I'm stack with this dispute management auth error. There is no Su53, there is no issue showing up in trace everything is RC=0.

My functional team doing configuration testing in dispute management and having this error that has no error on su53 no trace and they have SAP_ALL plus some roles I assign to them. I searched SDN and I Google it but there is nothing out there that can resolve this issue.

Please give me some idea so I can at least try to resolve this issue. Here is the error:

You are not authorized to perform this action

Message no: SCMG_CASE009

Diagnosis

You tried to perform an action for which you do not have authorization

System Response

You can not perform this action

Procedure

Check whether you are allowed to perform this action

Procedure for system administration

Assign the relevant authorization, if the user is allowed to perform this action

The internal code for the activity is MODI.

Please advice so I can get to the right direction

Thanks in advance

Faisal

Re: Dispute Management Authorization error

jurjen_heeck — Wed, 22 Dec 2010 17:56:10 GMT

Have you tried running the transaction with the debugger on and breakpoints at AUTHORITY-CHECK statements? That should at least reveal the check that fails and give you something to search for in your roles etc.

Another one could be that SAP_ALL is incomplete and needs to be regenerated.

Re: Dispute Management Authorization error

Former Member — Wed, 22 Dec 2010 18:31:23 GMT

Thanks for replied.

I can talk to my developer to check the programmer and see if they can find anything that fails.

But how do you regenerate SAP_ALL, I never heard of this before. SAP_ALL default /delivered profile, how can you regenerate SAP_ALL?

Can you please explain how to do this?

Thanks in advance

Faisal

Re: Dispute Management Authorization error

Former Member — Wed, 22 Dec 2010 19:33:46 GMT

We have this same error at my client. It was not happening till two days ago. If anyone finds a solution please reply.

Thanks once again

Suraesh Bala

Re: Dispute Management Authorization error

jurjen_heeck — Wed, 22 Dec 2010 19:41:26 GMT

But how do you regenerate SAP_ALL, I never heard of this before.  SAP_ALL default /delivered profile, how can you regenerate SAP_ALL?

Start transaction SU21 and hit the button called "Regenerate SAP_ALL" (SAP_ALL is client dependent, like all other roles/profiles so you may have to do it more than once).

This action makes sure SAP_ALL is up to date with all objects brought in by upgrades and support packs. Do make sure you have sufficient rights throught roles/profiles other than SAP_ALL. I wouldn't trust changing wheels while I'm driving the car

Cheers

Jurjen

Re: Dispute Management Authorization error

mvoros — Thu, 23 Dec 2010 05:19:16 GMT

Hi,

you can always try ST01 to get all authorization checks. SU53 displays result of last authorization check. In this case it should be one of authorization objects S_SRMGS*. That check is not easy to find because it is performed by calling method IS_AUTHORIZED of object which implements interface IF_SRM_DOCUMENT. Fortunately, there are only 2 objects which implement this interface. I am not sure how ST01 can handle dynamic call of method.

Cheers

Re: Dispute Management Authorization error

Former Member — Thu, 20 Oct 2011 13:47:24 GMT

Hello,

Did you ever get to the bottom of this issue? We are having the same issue.

Thanks, Kevin

Re: Dispute Management Authorization error

Former Member — Thu, 20 Oct 2011 16:04:31 GMT

Likewise having the same error. Our user has SAP_ALL and (because there is a PLOG authorization check) also has the ALL structural authorization. SAP_ALL is current (as evidenced by the complete success noted in ST01 and SU53). Debugging is enormously challenging. No results in a SAP notes search. We also in some cases get error SRMF075 which says Called service provider: no authorization.

Edited by: Corwin Slack on Oct 20, 2011 12:04 PM