topic Re: SPRO, SM30 in Application Development and Automation Discussions

SPRO, SM30

Former Member — Fri, 04 Jan 2008 17:25:03 GMT

Hi All,

I am working with a CRM user.

The user's path is : SPRO - IMG - CRM - Transactions - Settings for Opportunities - Define Opportunity group, priority and origin - Define source for opportunities.

When she clicks on the clock at this stage, she gets the msg " you dont have authorization for SM30".When i asked her, she told me she needs to update the table adding some data.

I am a little apprehensive about the change access to SM30. Any alternatives on how we do this ?

Appreciate in Advance.

Re: SPRO, SM30

Former Member — Fri, 04 Jan 2008 17:33:14 GMT

Hi Reel,

In which environment is she trying to do this, is it in DEV, QA or Prod.

Thanks.

Re: SPRO, SM30

Former Member — Fri, 04 Jan 2008 17:34:02 GMT

In all 3 of them.

Re: SPRO, SM30

Former Member — Fri, 04 Jan 2008 18:05:32 GMT

One soultion is to find the table the user is trying to update and create a custom transaction code for it and then assign it to the user so that he can update and view only that table.

Following is the link to create a custom Tcode for a view .

Hope this helps you.

Re: SPRO, SM30

Former Member — Fri, 04 Jan 2008 18:36:27 GMT

Is this configuration transportable? If it is, she should do it in dev and transport to QA and production. Configuration in production should rarely (if ever!) be done in the IMG.

Re: SPRO, SM30

Former Member — Fri, 04 Jan 2008 20:47:20 GMT

The system might be throwing a message with sy-tcode as the missing authorization, even although the check failed elsewhere.

Ask the user to create a shortcut with transaction SU53 entered in it, and drop it into the "no authorization" popup. What is the last failed authority check (before the popup is called)?

It is also recommendable to trace the user, as the SU53 only shows the last failed authority check... which may, or may not, be the reason.

Once you know exactly the reasoning behind this popup (the message number is often very usefull for a search in "OSS"!), then it is easier to comment.

Cheers,

Julius

PS: Of course, answers to make the problem go away come "cheeper" (but not necessarily in the long run) than analysis of the cause of the problem.