<?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 Authorization Issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120306#M1707684</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any User Exits/ Includes/Badis&amp;nbsp; to restrict&amp;nbsp; authorization to&amp;nbsp; sales document types in VA01.&amp;nbsp; &lt;/P&gt;&lt;P&gt;There are 10 sales document types in our system , except 5 users, no other users should be able to&amp;nbsp; use 2 sales document types in VA01 and VA02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I have checked it up standard authorization roles, it’s&amp;nbsp; too complicated to&amp;nbsp; restrict authorization to only selective sales document types&amp;nbsp; for selective users as there are multiple&amp;nbsp; roles has been assigned to users. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Nov 2012 22:34:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2012-11-08T22:34:05Z</dc:date>
    <item>
      <title>Authorization Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120306#M1707684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any User Exits/ Includes/Badis&amp;nbsp; to restrict&amp;nbsp; authorization to&amp;nbsp; sales document types in VA01.&amp;nbsp; &lt;/P&gt;&lt;P&gt;There are 10 sales document types in our system , except 5 users, no other users should be able to&amp;nbsp; use 2 sales document types in VA01 and VA02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I have checked it up standard authorization roles, it’s&amp;nbsp; too complicated to&amp;nbsp; restrict authorization to only selective sales document types&amp;nbsp; for selective users as there are multiple&amp;nbsp; roles has been assigned to users. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2012 22:34:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120306#M1707684</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-11-08T22:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120307#M1707685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why dont you do your validation in Include MV45AFZB ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 04:22:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120307#M1707685</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-11-09T04:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120308#M1707686</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rusheek ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try User Exit MV45AFZZ&lt;/P&gt;&lt;P&gt;Based on SY-TCODE , SY-UNAME and VBAK-AUART u can create a check.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 04:28:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120308#M1707686</guid>
      <dc:creator>Sijin_Chandran</dc:creator>
      <dc:date>2012-11-09T04:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120309#M1707687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The SAP standard provides authorization object V_VBAK_AAT for this purpose. It should be possible to solve this with a proper roles concept, rather than a probably unnecessary enhancement.&lt;/P&gt;&lt;P&gt;Please have a look in &lt;A __default_attr="2061" __jive_macro_name="community" class="jive_macro jive_macro_community" href="https://community.sap.com/"&gt;&lt;/A&gt; as well. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 09:56:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-issue/m-p/9120309#M1707687</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2012-11-09T09:56:11Z</dc:date>
    </item>
  </channel>
</rss>

