<?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 Details about authorization Object in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552471#M250502</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please help ,i had two fields ex sales org &amp;amp; distribution chanel and i have to write a code for authorization , is the authorization object which i wrote is right or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that we can use at max of 10 fields , but say vkorg / vtweg is used 5 times  with different variable name in same prog how to make sure that this code will work for authorization check on VKORG/ VTWEG can anybody please explain me in step's &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK&lt;/P&gt;&lt;P&gt;          OBJECT 'Z_zzlau'&lt;/P&gt;&lt;P&gt;          ID  'VKORG' FIELD  'S_VKORG'&lt;/P&gt;&lt;P&gt;          ID  'VTWEG' FIELD  'S_VTWEG'&lt;/P&gt;&lt;P&gt;          ID  'ACTVT' FIELD '02'&lt;/P&gt;&lt;P&gt;          ID  'ACTVT' FIELD '03'&lt;/P&gt;&lt;P&gt;          ID  'ACTVT' FIELD '70'.&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, 10 Aug 2006 16:57:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-08-10T16:57:27Z</dc:date>
    <item>
      <title>Details about authorization Object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552471#M250502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please help ,i had two fields ex sales org &amp;amp; distribution chanel and i have to write a code for authorization , is the authorization object which i wrote is right or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that we can use at max of 10 fields , but say vkorg / vtweg is used 5 times  with different variable name in same prog how to make sure that this code will work for authorization check on VKORG/ VTWEG can anybody please explain me in step's &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK&lt;/P&gt;&lt;P&gt;          OBJECT 'Z_zzlau'&lt;/P&gt;&lt;P&gt;          ID  'VKORG' FIELD  'S_VKORG'&lt;/P&gt;&lt;P&gt;          ID  'VTWEG' FIELD  'S_VTWEG'&lt;/P&gt;&lt;P&gt;          ID  'ACTVT' FIELD '02'&lt;/P&gt;&lt;P&gt;          ID  'ACTVT' FIELD '03'&lt;/P&gt;&lt;P&gt;          ID  'ACTVT' FIELD '70'.&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, 10 Aug 2006 16:57:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552471#M250502</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-10T16:57:27Z</dc:date>
    </item>
    <item>
      <title>Re: Details about authorization Object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552472#M250503</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;ACTVT field is used for checking the create /display / change authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;after creation of the activity group , add it to the user profiles which need authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;01-create 02-change 03-display &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;AUTHORITY-CHECK
OBJECT 'Z_zzlau'
ID 'VKORG' FIELD 'S_VKORG'
ID 'VTWEG' FIELD 'S_VTWEG'
ID 'ACTVT' FIELD '02'
ID 'ACTVT' FIELD '03'
ID 'ACTVT' FIELD '70'.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you are checking authorizations with the selection screen parameters then change your code like below:(if change is required)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;AUTHORITY-CHECK
OBJECT 'Z_ZZLAU'
ID 'VKORG' FIELD S_VKORG
ID 'VTWEG' FIELD S_VTWEG
ID 'ACTVT' FIELD '02'.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and also check SAP help on this :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic form &lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT object &lt;/P&gt;&lt;P&gt;    ID name1  FIELD f1 &lt;/P&gt;&lt;P&gt;    ID name2  FIELD f2 &lt;/P&gt;&lt;P&gt;    ... &lt;/P&gt;&lt;P&gt;    ID name10 FIELD f10. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;Explanation of IDs: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object &lt;/P&gt;&lt;P&gt;Field which contains the name of the object for which the authorization is to be checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;name1 ... &lt;/P&gt;&lt;P&gt;Fields which contain the names of the &lt;/P&gt;&lt;P&gt;name10 &lt;/P&gt;&lt;P&gt;authorization fields defined in the object. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;f1 ... &lt;/P&gt;&lt;P&gt;Fields which contain the values for which the &lt;/P&gt;&lt;P&gt;f10 &lt;/P&gt;&lt;P&gt;authorization is to be checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK checks for one object whether the user has an authorization that contains all values of f (see SAP authorization concept). &lt;/P&gt;&lt;P&gt;You must specify all authorizations for an object and a also a value for each ID (or DUMMY). &lt;/P&gt;&lt;P&gt;The system checks the values for the IDs by AND-ing them together, i.e. all values must be part of an authorization assigned to the user. &lt;/P&gt;&lt;P&gt;If a user has several authorizations for an object, the values are OR-ed together. This means that if the CHECK finds all the specified values in one authorization, the user can proceed. Only if none of the authorizations for a user contains all the required values is the user rejected. &lt;/P&gt;&lt;P&gt;If the return code value in SY-SUBRC is 0, the user has the required authorization and may continue. &lt;/P&gt;&lt;P&gt;The return code value changes according to the different error scenarios. The return code values have the following meaning: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4 &lt;/P&gt;&lt;P&gt;User has no authorization in the SAP System for such an action. If necessary, change the user master record. &lt;/P&gt;&lt;P&gt;8 &lt;/P&gt;&lt;P&gt;Too many parameters (fields, values). Maximum allowed is 10. &lt;/P&gt;&lt;P&gt;12 &lt;/P&gt;&lt;P&gt;Specified object not maintained in the user master record. &lt;/P&gt;&lt;P&gt;16 &lt;/P&gt;&lt;P&gt;No profile entered in the user master record. &lt;/P&gt;&lt;P&gt;24 &lt;/P&gt;&lt;P&gt;The field names of the check call do not match those of an authorization. Either the authorization or the call is incorrect. &lt;/P&gt;&lt;P&gt;28 &lt;/P&gt;&lt;P&gt;Incorrect structure for user master record. &lt;/P&gt;&lt;P&gt;32 &lt;/P&gt;&lt;P&gt;Incorrect structure for user master record. &lt;/P&gt;&lt;P&gt;36 &lt;/P&gt;&lt;P&gt;Incorrect structure for user master record. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the return code value is 8 or 24, inform the person responsible for the program. If the return code value is 4, 12, 16 or 24, consult your system administrator if you think you should have the relevant authorization. In the case of errors 28 to 36, contact SAP because authorizations have probably been destroyed. &lt;/P&gt;&lt;P&gt;Individual authorizations are assigned to users in their respective user profiles, i.e. they are grouped together in profiles which are stored in the user master record. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note &lt;/P&gt;&lt;P&gt;Instead of ID name FIELD f, you can also write ID name DUMMY. This means that no check is performed for the field concerned. &lt;/P&gt;&lt;P&gt;The check can only be performed on CHAR fields. All other field types result in 'unauthorized'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example &lt;/P&gt;&lt;P&gt;Check whether the user is authorized for a particular plant. In this case, the following authorization object applies: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table OBJ: Definition of authorization object &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;M_EINF_WRK &lt;/P&gt;&lt;P&gt;   ACTVT &lt;/P&gt;&lt;P&gt;   WERKS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here, M_EINF_WRK is the object name, whilst ACTVT and WERKS are authorization fields. For example, a user with the authorizations &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;M_EINF_WRK_BERECH1 &lt;/P&gt;&lt;P&gt;   ACTVT 01-03 &lt;/P&gt;&lt;P&gt;   WERKS 0001-0003 . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can display and change plants within the Purchasing and Materials Management areas. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Such a user would thus pass the checks &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT 'M_EINF_WRK' &lt;/P&gt;&lt;P&gt;    ID 'WERKS' FIELD '0002' &lt;/P&gt;&lt;P&gt;    ID 'ACTVT' FIELD '02'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT 'M_EINF_WRK' &lt;/P&gt;&lt;P&gt;    ID 'WERKS' DUMMY &lt;/P&gt;&lt;P&gt;    ID 'ACTVT' FIELD '01': &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but would fail the check &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT 'M_EINF_WRK' &lt;/P&gt;&lt;P&gt;    ID 'WERKS' FIELD '0005' &lt;/P&gt;&lt;P&gt;    ID 'ACTVT' FIELD '04'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To suppress unnecessary authorization checks or to carry out checks before the user has entered all the values, use DUMMY - as in this example. You can confirm the authorization later with another AUTHORITY-CHECK. &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;Appana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2006 17:02:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552472#M250503</guid>
      <dc:creator>Laxmana_Appana_</dc:creator>
      <dc:date>2006-08-10T17:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: Details about authorization Object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552473#M250504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Authorization object 'Z_zzlau' should be given in CAPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prakash.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2006 17:03:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552473#M250504</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-10T17:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: Details about authorization Object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552474#M250505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;delete the quotes for 'z_zzlau'&lt;/P&gt;&lt;P&gt;try this:&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK&lt;/P&gt;&lt;P&gt;OBJECT Z_ZZLAU&lt;/P&gt;&lt;P&gt;ID VKORG FIELD 'S_VKORG'&lt;/P&gt;&lt;P&gt;ID VTWEG FIELD 'S_VTWEG'&lt;/P&gt;&lt;P&gt;ID ACTVT FIELD '02'&lt;/P&gt;&lt;P&gt;ID ACTVT FIELD '03'&lt;/P&gt;&lt;P&gt;ID ACTVT FIELD '70'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REGARDS,&lt;/P&gt;&lt;P&gt;KEERTHI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2006 17:12:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/details-about-authorization-object/m-p/1552474#M250505</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-10T17:12:03Z</dc:date>
    </item>
  </channel>
</rss>

