<?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 authority check in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/3008651#M710909</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. What is Authorit object? How do we find &amp;amp; create them? What is necessatiy for doing it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 10 Nov 2007 12:37:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-10T12:37:58Z</dc:date>
    <item>
      <title>authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/3008651#M710909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. What is Authorit object? How do we find &amp;amp; create them? What is necessatiy for doing it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Nov 2007 12:37:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/3008651#M710909</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-10T12:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/3008652#M710910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;In general different users will be given different authorizations based on their role in the orgn.&lt;/P&gt;&lt;P&gt;We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Codes.&lt;/P&gt;&lt;P&gt;USe SUIM and SU21 T codes for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appropriate authorization is required before a user can carry out certain actions in the system. When you log on to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;authorization check is implemented for every sensitive transaction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This means you have to allocate an authorization object in the definition of the transaction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;program an AUTHORITY-CHECK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT &amp;lt;authorization object&amp;gt; &lt;/P&gt;&lt;P&gt;ID &amp;lt;authority field 1&amp;gt; FIELD &amp;lt;field value 1&amp;gt;. &lt;/P&gt;&lt;P&gt;ID &amp;lt;authority field 2&amp;gt; FIELD &amp;lt;field value 2&amp;gt;. &lt;/P&gt;&lt;P&gt;... &lt;/P&gt;&lt;P&gt;ID &amp;lt;authority-field n&amp;gt; FIELD &amp;lt;field value n&amp;gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The OBJECT parameter specifies the authorization object. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ID parameter specifies an authorization field (in the authorization object). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The FIELD parameter specifies a value for the authorization field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use the existing authorization objects to protect your data. But new developments may require that you define new &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;authorization objects and fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;authorization checks. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;authorization object field values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You program the authorization check using the ABAP statement AUTHORITY-CHECK.&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT 'S_TRVL_BKS' &lt;/P&gt;&lt;P&gt;ID 'ACTVT' FIELD '02' &lt;/P&gt;&lt;P&gt;ID 'CUSTTYPE' FIELD 'B'. &lt;/P&gt;&lt;P&gt;IF SY-SUBRC &amp;lt;&amp;gt; 0. &lt;/P&gt;&lt;P&gt;MESSAGE E... &lt;/P&gt;&lt;P&gt;ENDIF. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'S_TRVL_BKS' is a auth. object&lt;/P&gt;&lt;P&gt;ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;This Authorization concept is somewhat linked with BASIS people.&lt;/P&gt;&lt;P&gt;As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;authrization objects and TCodes for a  profile and that profile in turn attached to a particular user.&lt;/P&gt;&lt;P&gt;Take the help of the basis Guy and create and use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Nov 2007 13:34:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/3008652#M710910</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-10T13:34:00Z</dc:date>
    </item>
  </channel>
</rss>

