<?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: BAPI authorization doubt in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083967#M1902085</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you &lt;SPAN style="color: #333333; font-size: 12px;"&gt;Julius &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro_emoticon jive_macro jive_emote" src="https://community.sap.com/1291/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jun 2015 14:14:59 GMT</pubDate>
    <dc:creator>Ziv_Marcovich</dc:creator>
    <dc:date>2015-06-17T14:14:59Z</dc:date>
    <item>
      <title>BAPI authorization doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083963#M1902081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Hello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;I Run BAPI to update notification after the save of PM order &lt;BR /&gt;The user should have authorization to this code execution but not to tcode IW22&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Is it possible from authorization perspective&amp;nbsp; ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Ziv&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2015 11:35:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083963#M1902081</guid>
      <dc:creator>Ziv_Marcovich</dc:creator>
      <dc:date>2015-06-17T11:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI authorization doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083964#M1902082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, infact it is mandatory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2015 13:22:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083964#M1902082</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-06-17T13:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI authorization doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083965#M1902083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN style="color: #333333; font-size: 12px;"&gt;Julius,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to conirm You mean that&amp;nbsp; the user will not have dialog IW22 authorization , yet he can run the BAPI that update the notification .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regads,&lt;/P&gt;&lt;P&gt;Ziv&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2015 13:33:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083965#M1902083</guid>
      <dc:creator>Ziv_Marcovich</dc:creator>
      <dc:date>2015-06-17T13:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI authorization doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083966#M1902084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yep, the definition of a BAPI is that it must functionally perform the same processing as dialog functions and must be remote enabled, but is not allowed to check S_TCODE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the entry point for the user is the BAPI, then you should authorize S_RFC plus the application authorizations needed. S_TCODE is not needed even if functionally the same as IW22.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2015 13:46:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083966#M1902084</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-06-17T13:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI authorization doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083967#M1902085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you &lt;SPAN style="color: #333333; font-size: 12px;"&gt;Julius &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro_emoticon jive_macro jive_emote" src="https://community.sap.com/1291/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2015 14:14:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083967#M1902085</guid>
      <dc:creator>Ziv_Marcovich</dc:creator>
      <dc:date>2015-06-17T14:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI authorization doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083968#M1902086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;BTW: what is the concern with IW22? It is a bit of an overkill to access CAD drawings and the SU24 proposals for changing the user status are very blunt, but other than that the transaction is harmless and one would be happy if people did their work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I generally observe that customers do not care much about I* authorizations in PM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2015 19:08:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-authorization-doubt/m-p/11083968#M1902086</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-06-17T19:08:25Z</dc:date>
    </item>
  </channel>
</rss>

