<?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>topic Re: Authorization debugging in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249414#M1913722</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you suggest, if debugging can be used to see the exact missing auth. object, for a user.&lt;/P&gt;&lt;P&gt;i tried setting break point for statement ' AUTHORITY-CHECK', for a user having insufficient auth., but it still showed in green these statements. i understand that setting up breakpoint statement, will &lt;/P&gt;&lt;P&gt;show all such statements, because that is what i set. But my requirement is to see where the missing auth. check is. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Plaban&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Aug 2015 23:56:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-08-04T23:56:26Z</dc:date>
    <item>
      <title>Authorization debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249410#M1913718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have been through Auth. debugging in &lt;A __default_attr="53426" __jive_macro_name="document" class="jive_macro_document jive_macro" data-orig-content="How to analyze authorization issues in debug" href="https://community.sap.com/" modifiedtitle="true" title="How to analyze authorization issues in debug"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;but i could not see what purpose it serves. I can search AUTHORITY-CHECK statements through CTRL+ F/Find button . So, could you suggest, what benefit does debugging give&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Plaban&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 07:22:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249410#M1913718</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-08-04T07:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249411#M1913719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi CTRL-F only works for the set of code you are in at the time.&amp;nbsp; Debugger lets you identify all (well most of) the checks that are performed for an actual execution, regardless of the programs, FM's etc that are executed on the way to a specific outcome.&amp;nbsp; It is also a much quicker way of identifying the relevant auth checks than manually reviewing code. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 11:08:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249411#M1913719</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-08-04T11:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249412#M1913720</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ok, but my doubt is , will Debugging for Breakpoint statement eg. Breakpoint at statement &lt;SPAN style="font-size: 13.3333330154419px;"&gt;AUTHORITY-CHECK, &lt;/SPAN&gt;show/does anything else except finding out the AUTHORITY-CHECK statements, in the program of the t-code&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Plaban&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 11:23:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249412#M1913720</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-08-04T11:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249413#M1913721</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, one big benefit is that the debugger will show you what values are being passed into the check (so it will show object + activity/plant etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the debugger certainly isn't a replacement for code review but should be seen as an additional tool with some of the benefits already mentioned.&amp;nbsp; In the same way that SU53 has it's place 'vs' the better info in ST01, debugging can give benefits over code review.&amp;nbsp; There is a time &amp;amp; place for all of the tools.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 11:34:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249413#M1913721</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-08-04T11:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249414#M1913722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you suggest, if debugging can be used to see the exact missing auth. object, for a user.&lt;/P&gt;&lt;P&gt;i tried setting break point for statement ' AUTHORITY-CHECK', for a user having insufficient auth., but it still showed in green these statements. i understand that setting up breakpoint statement, will &lt;/P&gt;&lt;P&gt;show all such statements, because that is what i set. But my requirement is to see where the missing auth. check is. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Plaban&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 23:56:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249414#M1913722</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-08-04T23:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249415#M1913723</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Plaban,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Debugging can help but it will depend on how the check is coded.&amp;nbsp; It could well be that the check is in a logical database (common in HR) or via a macro which are harder to debug and in this respect debugger is useful as you can track through the code line by line or section by section.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Aug 2015 08:39:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-debugging/m-p/11249415#M1913723</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-08-10T08:39:55Z</dc:date>
    </item>
  </channel>
</rss>

