<?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: authority check in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531963#M574222</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;perform authority_check using w_indir.
form authority_check using x_indir.
authority-check object 'S_DATASET'
id 'PROGRAM' field sy-repid
id 'ACTVT' field '33'
id 'FILENAME' field x_indir.
endform. " AUTHORITY_CHECK &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;'S_DATASET' -&amp;gt;&amp;lt;/b&amp;gt;  Consist of  ACTVT  &amp;amp; FILENAME  2  parameters .  so  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;'ACTVT'  -&amp;gt;&amp;lt;/b&amp;gt;activity   means  ...&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt; " Read , Write  , Display  ..  NOT Authoprised&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;, to the File  etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;'FILENAME' -&amp;gt;&amp;lt;/b&amp;gt; will have the Particular Object (File) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally   'S_DATASET'   Authoirasation will be checked  in the   Applcation  server level  data file fetching and   uploading  into the sap  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;using Function Modules  :&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;1.OPEN_DATA_SET  &lt;/P&gt;&lt;P&gt;2.UPLOAD  ....AND  &lt;/P&gt;&lt;P&gt;3.CLOSE_DATA_SET ..&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above  3 Function Modules   while OPEN_DATA_SET    the  'S_DATASET'  will be called  and checked  for activity  and file name  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if it is usefull....&lt;/P&gt;&lt;P&gt;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jul 2007 07:04:21 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-19T07:04:21Z</dc:date>
    <item>
      <title>authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531958#M574217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please tell me whts the use of the following piece of code???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;perform authority_check using w_indir.&lt;/P&gt;&lt;P&gt;form authority_check using x_indir.&lt;/P&gt;&lt;P&gt;  authority-check object 'S_DATASET'&lt;/P&gt;&lt;P&gt;          id 'PROGRAM'  field sy-repid&lt;/P&gt;&lt;P&gt;          id 'ACTVT'    field '33'&lt;/P&gt;&lt;P&gt;          id 'FILENAME' field x_indir.&lt;/P&gt;&lt;P&gt;endform.                    " AUTHORITY_CHECK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2007 06:50:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531958#M574217</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-19T06:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531959#M574218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;perform authority_check using w_indir.&lt;/P&gt;&lt;P&gt;form authority_check using x_indir.&lt;/P&gt;&lt;P&gt;authority-check object 'S_DATASET'&lt;/P&gt;&lt;P&gt;id 'PROGRAM' field sy-repid&lt;/P&gt;&lt;P&gt;id 'ACTVT' field '33'&lt;/P&gt;&lt;P&gt;id 'FILENAME' field x_indir.&lt;/P&gt;&lt;P&gt;endform. " AUTHORITY_CHECK &lt;/P&gt;&lt;P&gt;This peice of code is to check if you have therequired authorization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK statement checks whether authorization is entered in the user master record of the current user or the user specified in user for the authorization object S_DATASET, and whether this authorization is sufficient for the request specified in the statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2007 06:54:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531959#M574218</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2007-07-19T06:54:48Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531960#M574219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This statement checks whether authorization is entered in the user master record of the current user ( sy-uname) for the authorization object entered in the field S_DATASET and whether this is sufficient for the request specified in the statement. A flat character-type field that contains the name of an authorization object is expected for S_DATASET. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With id1 ... id10, you must have at least one and can have a maximum of 10 authorization fields listed for the authorization object specified. With id1 ... id10, "flat", character-type fields are expected that contain the name of the authorization fields in uppercase letters. If an authorization field is specified that does not appear in the authorization object, no check can be executed and sy-subrc is set to 4. For each specified authorization field, you must specify with FIELD either a value to be checked in a flat, character-type field val1 ... val10 or the language element DUMMY. &lt;/P&gt;&lt;P&gt;&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;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2007 06:56:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531960#M574219</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-19T06:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531961#M574220</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 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 appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An 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 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 use the existing authorization objects to protect your data. But new developments may require that you define new 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 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 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, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these 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;&amp;lt;b&amp;gt;Reward points for useful Answers&amp;lt;/b&amp;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>Thu, 19 Jul 2007 06:57:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531961#M574220</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-19T06:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531962#M574221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&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 appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An 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 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 use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prajith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2007 06:58:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531962#M574221</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-19T06:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531963#M574222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;perform authority_check using w_indir.
form authority_check using x_indir.
authority-check object 'S_DATASET'
id 'PROGRAM' field sy-repid
id 'ACTVT' field '33'
id 'FILENAME' field x_indir.
endform. " AUTHORITY_CHECK &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;'S_DATASET' -&amp;gt;&amp;lt;/b&amp;gt;  Consist of  ACTVT  &amp;amp; FILENAME  2  parameters .  so  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;'ACTVT'  -&amp;gt;&amp;lt;/b&amp;gt;activity   means  ...&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt; " Read , Write  , Display  ..  NOT Authoprised&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;, to the File  etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;'FILENAME' -&amp;gt;&amp;lt;/b&amp;gt; will have the Particular Object (File) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally   'S_DATASET'   Authoirasation will be checked  in the   Applcation  server level  data file fetching and   uploading  into the sap  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;using Function Modules  :&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;1.OPEN_DATA_SET  &lt;/P&gt;&lt;P&gt;2.UPLOAD  ....AND  &lt;/P&gt;&lt;P&gt;3.CLOSE_DATA_SET ..&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above  3 Function Modules   while OPEN_DATA_SET    the  'S_DATASET'  will be called  and checked  for activity  and file name  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if it is usefull....&lt;/P&gt;&lt;P&gt;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2007 07:04:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531963#M574222</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-19T07:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: authority check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531964#M574223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main use of Authority Check is to give authorization to the specific users. If Authority check is not given any user can use the program or table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ex:- In the below example i am applying the authority check for the specific t_code. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT 'S_TCODE'&lt;/P&gt;&lt;P&gt;                                   ID            'TCD'&lt;/P&gt;&lt;P&gt;                                    FIELD     c_tcode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  IF sy-subrc NE 0.&lt;/P&gt;&lt;P&gt;    MESSAGE e000(38) WITH text-002.&lt;/P&gt;&lt;P&gt;  ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in the above example 'S_TCODE'is the Object name, &amp;#145;TCD&amp;#146; is the object id  and c_tcode is the field name which we have used in our program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if it is useful....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Vasudeva Rao.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2007 07:40:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authority-check/m-p/2531964#M574223</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-19T07:40:43Z</dc:date>
    </item>
  </channel>
</rss>

