topic Re: Authorization Problem to access a custom TCode in Application Development and Automation Discussions

Authorization Problem to access a custom TCode

Former Member — Tue, 18 Jan 2011 05:49:39 GMT

Hi Everybody,

I developped a custom report with a z tcode in development server and transported to testing server.

Report and Tcode doesn't have any authorization object.

User is not able to access the tcode in Test server . He is gwtting a message like " no authorization to access the t code ... ".

though the report and tcode doesn't have any authorization object.

What could be the reason ? Solution.

Thanks and Regards

Srikanta

Re: Authorization Problem to access a custom TCode

Former Member — Tue, 18 Jan 2011 05:57:38 GMT

Hi srikanta,

This t code need to be assigned in authorization profile of user.

Get help of your basis for same.

This will solve your problem.

Thanks,

Dhiraj.

Re: Authorization Problem to access a custom TCode

GauthamV — Tue, 18 Jan 2011 06:16:13 GMT

Users will not have authorizations to any transaction unless they are asigned to their roles or profiles.

Ask the user to send a mail to basis person for authorization to this Z transaction.

Whenever they have problem for authorization they can just send screenshot of SU53 transaction to basis people.

Re: Authorization Problem to access a custom TCode

Former Member — Tue, 18 Jan 2011 11:19:21 GMT

Hi,

After running this t-code open another session of tcode su53.

There you can see the objects which are failing . Because of this the user is not able to access that t-code. Once you got that su53 screen shot sit with your basis people and sort out the issue.

With Regards,

Sumodh.P

Re: Authorization Problem to access a custom TCode

Former Member — Tue, 18 Jan 2011 11:23:58 GMT

Hi Srikanta,

I think there is some problem with the role or profile that is assigned to your user id. Please check whether S_TCODE authorization object is assigned to your id in test server or not.

The best way to find this is " First run the transaction that you had created in Test server, after you got the error message. Run Su53 transaction and send that screenshot to BASIS team' They will take care of the issue.

Thanks