<?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: Regarding Authorization object in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903650#M1793055</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should always check first whether there is really a need for a new authorisation object. Most simpler tasks can be solved by using existing objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What exactly needs to be checked in your scenario? For simple may execute/may not execute scenarios, look at the authorisation groups in the program attributes, which is linked to S_PROGRAM (and S_DEVELOP) authorisation objects. Study the online documentation of these objects, also speak to your system and/or security administrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Dec 2013 08:48:44 GMT</pubDate>
    <dc:creator>ThomasZloch</dc:creator>
    <dc:date>2013-12-04T08:48:44Z</dc:date>
    <item>
      <title>Regarding Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903646#M1793051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Every one,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a custom report and it needs to have authorizations. it means that only few users should be able to execute the report.&lt;/P&gt;&lt;P&gt;I am following the below path. Please let me know, if my approach is wrong or not a best practice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I went to SU20 created a authorization field ztrxn with data-element as tcode.&lt;/P&gt;&lt;P&gt;Went to SU21 created an authorization object Z_AUTH_OBJ1, and assigned the above field to it.&lt;/P&gt;&lt;P&gt;In PFCG, i am trying to assign this authorization object to the user profile.&lt;/P&gt;&lt;P&gt;After this i am planning to use this auth-object created in the SU21&amp;nbsp; as below code snippet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT 'Z_AUTH_OBJ1' &lt;/P&gt;&lt;P&gt;&amp;nbsp; ID 'ACTVT'&amp;nbsp; FIELD '02' &lt;/P&gt;&lt;P&gt;&amp;nbsp; ID 'CUSTTYPE' FIELD 'B'. &lt;/P&gt;&lt;P&gt;IF SY-SUBRC &amp;lt;&amp;gt; 0. &lt;/P&gt;&lt;P&gt;&amp;nbsp; MESSAGE E... &lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) How do i make use of the ACTVT and CUSTTYPE&amp;nbsp; fields ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) What is the authorization field 'ztrxn'&amp;nbsp; created above ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 05:32:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903646#M1793051</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-12-04T05:32:20Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903647#M1793052</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; You need to maintain the assignments of authorization objects in tcode: SU24.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ztrxn (as you mentioned above) is the field name used inside authorization objects.&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;Madhumahesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 05:37:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903647#M1793052</guid>
      <dc:creator>koolspy_ultimate</dc:creator>
      <dc:date>2013-12-04T05:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903648#M1793053</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 11.818181991577148px; color: #333333;"&gt;&lt;STRONG&gt;ACTVT&lt;/STRONG&gt; field points what kind of authority you want to check for, 02 indicates that you are checking to make sure that the user has been granted the authority to change.&lt;/P&gt;&lt;P style="font-size: 11.818181991577148px; color: #333333;"&gt;&lt;STRONG&gt;CUSTTYPE&lt;/STRONG&gt; field is for only certain CUSTTYPE's have the ACTVT = 02 setup which means only certain user will have the authority to change.&lt;/P&gt;&lt;P style="font-size: 11.818181991577148px; color: #333333;"&gt;&amp;nbsp;&amp;nbsp; When the statement you have given is executed, this statement will check the configuration of authorization object 'S_TRVL_BKS' to see if the current user has the authority to change for CUSTTYPE = B. If the user does have the authority to change the sy-subrc will be zero, else it will be non-zero, in which case a message will be shown.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 06:09:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903648#M1793053</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-12-04T06:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903649#M1793054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chandra&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically here you want to check whether use has change/display/create etc (ACTVT) for CUSTYPE values&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read F1 documentation for this&lt;/P&gt;&lt;P&gt;Nabheet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 06:32:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903649#M1793054</guid>
      <dc:creator>nabheetscn</dc:creator>
      <dc:date>2013-12-04T06:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding Authorization object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903650#M1793055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should always check first whether there is really a need for a new authorisation object. Most simpler tasks can be solved by using existing objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What exactly needs to be checked in your scenario? For simple may execute/may not execute scenarios, look at the authorisation groups in the program attributes, which is linked to S_PROGRAM (and S_DEVELOP) authorisation objects. Study the online documentation of these objects, also speak to your system and/or security administrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 08:48:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-authorization-object/m-p/9903650#M1793055</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2013-12-04T08:48:44Z</dc:date>
    </item>
  </channel>
</rss>

