<?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 object in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533295#M1264013</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The [standard authorization concept|http://help.sap.com/saphelp_nw70/helpdata/EN/52/67167f439b11d1896f0000e8322d00/frameset.htm] is based on the ABAP statement [AUTHORITY-CHECK|http://help.sap.com/abapdocu/en/ABAPAUTHORITY-CHECK.htm] and roles.&lt;/P&gt;&lt;P&gt;If you like to use it you would create some customer authorization objects with corresponding authorization fields, use [AUTHORITY-CHECK|http://help.sap.com/abapdocu/en/ABAPAUTHORITY-CHECK.htm] and work with roles to assign authorizations to users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You describe another approach: "The user should be able to open the transaction only if the value is 'Y' in the database table for the user."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well, there exist applications for which is the correct technique: If the data already exist than it is ok to check these database entries. (Example: Everyone is allowed to maintain his or her own data.) &lt;/P&gt;&lt;P&gt;However, if an administrator has the task to maintain the permission assignments, than I recommend to go for the standard authorization concept.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Frank Buchholz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Apr 2009 11:11:21 GMT</pubDate>
    <dc:creator>Frank_Buchholz</dc:creator>
    <dc:date>2009-04-29T11:11:21Z</dc:date>
    <item>
      <title>Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533294#M1264012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have to add authorization to a z transaction in the dialog program.The user should be able to open the transaction only if the value is 'Y' in the database table for the user.Please suggest how should I do it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2009 04:41:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533294#M1264012</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-29T04:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533295#M1264013</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The [standard authorization concept|http://help.sap.com/saphelp_nw70/helpdata/EN/52/67167f439b11d1896f0000e8322d00/frameset.htm] is based on the ABAP statement [AUTHORITY-CHECK|http://help.sap.com/abapdocu/en/ABAPAUTHORITY-CHECK.htm] and roles.&lt;/P&gt;&lt;P&gt;If you like to use it you would create some customer authorization objects with corresponding authorization fields, use [AUTHORITY-CHECK|http://help.sap.com/abapdocu/en/ABAPAUTHORITY-CHECK.htm] and work with roles to assign authorizations to users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You describe another approach: "The user should be able to open the transaction only if the value is 'Y' in the database table for the user."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well, there exist applications for which is the correct technique: If the data already exist than it is ok to check these database entries. (Example: Everyone is allowed to maintain his or her own data.) &lt;/P&gt;&lt;P&gt;However, if an administrator has the task to maintain the permission assignments, than I recommend to go for the standard authorization concept.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Frank Buchholz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2009 11:11:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533295#M1264013</guid>
      <dc:creator>Frank_Buchholz</dc:creator>
      <dc:date>2009-04-29T11:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533296#M1264014</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shashi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ask the developer to put an authorization group on the program and then you can restirct it in the user role using S_PROGRAM and specifying the auth group for that program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Khan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 May 2009 16:48:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object/m-p/5533296#M1264014</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-04T16:48:11Z</dc:date>
    </item>
  </channel>
</rss>

