<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: SU53 in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861087#M817634</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SU53 shows last failed authorization check.Whenever a user has some authorization issues, tell him to send a screenshot of &amp;#147;su53&amp;#148;. In that screenshot SAP will clearly mention what all authorizations are required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For sending su53 results:  instead of sending screen shots of their su53 results, you can ask the user to run su53 transaction at there end.&lt;/P&gt;&lt;P&gt;after the user is using SU53, you do the same and press &amp;#145;F5&amp;#146; &lt;/P&gt;&lt;P&gt;you will be prompted to enter the user ID of the &amp;#145;remote&amp;#146; user&lt;/P&gt;&lt;P&gt;And there you go with the users last failed authorization check. &lt;/P&gt;&lt;P&gt;And alsO it is important the user run SU53 immediately after failed authorization check, as only the last object the failed authorization check is saved. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Prayag&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Jan 2007 21:29:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-05T21:29:10Z</dc:date>
    <item>
      <title>SU53</title>
      <link>https://community.sap.com/t5/technology-q-a/su53/qaq-p/1861086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi SAP gurus&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the purpose and use of t-code SU53. Can any one please explain with example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SV&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 20:24:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/su53/qaq-p/1861086</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-05T20:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: SU53</title>
      <link>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861087#M817634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SU53 shows last failed authorization check.Whenever a user has some authorization issues, tell him to send a screenshot of &amp;#147;su53&amp;#148;. In that screenshot SAP will clearly mention what all authorizations are required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For sending su53 results:  instead of sending screen shots of their su53 results, you can ask the user to run su53 transaction at there end.&lt;/P&gt;&lt;P&gt;after the user is using SU53, you do the same and press &amp;#145;F5&amp;#146; &lt;/P&gt;&lt;P&gt;you will be prompted to enter the user ID of the &amp;#145;remote&amp;#146; user&lt;/P&gt;&lt;P&gt;And there you go with the users last failed authorization check. &lt;/P&gt;&lt;P&gt;And alsO it is important the user run SU53 immediately after failed authorization check, as only the last object the failed authorization check is saved. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Prayag&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 21:29:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861087#M817634</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-05T21:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: SU53</title>
      <link>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861088#M817635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SU53 is used for authorization issues.  If someone tries to execute a transaction and they receive a "not authorized to use transaction xxxx" error message, they can do a /nSU53 and the missing authorization object(s), and transaction codes will be displayed.  This information can then be sent to your security group to be used to fix your security.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Karin Tillotson&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 21:32:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861088#M817635</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-05T21:32:12Z</dc:date>
    </item>
    <item>
      <title>Re: SU53</title>
      <link>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861089#M817636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SU53 T code is used for finding missing authorizations&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example you tpe command level SM50 but you don't have authorization to work on SM50.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you type know SM53 it will give you which authorization object is missed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You go and assign this authorization object in PFCG u will get the authorization to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i think it will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kiran kumar.v&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Jan 2007 10:12:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861089#M817636</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-06T10:12:44Z</dc:date>
    </item>
    <item>
      <title>Re: SU53</title>
      <link>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861090#M817637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks guys for all ur answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SV&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 18:50:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/su53/qaa-p/1861090#M817637</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T18:50:42Z</dc:date>
    </item>
  </channel>
</rss>

