<?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 Objects field values in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088400#M1358201</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;You can assign those roles to test user in which these objects are.Then ask user to run that test user who needs that t-code.Just on system trace. They will provide some value and you will come to know which value they require.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Sep 2009 12:41:59 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-09-18T12:41:59Z</dc:date>
    <item>
      <title>Authorization Objects field values</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088396#M1358197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone tell me what filed value can be entered in the following authorization Object since these authorization object s are not belong to any functional folks. I was wondering if the functional folks know the value that needs to be entered in the following fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assigned MM01, MM02 MM03 in this end user role and received these authorization objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard   Authorization for Classification                                      C_KLAH_BKL&lt;/P&gt;&lt;P&gt;Activity                                                      01, 03                                                       ACTVT&lt;/P&gt;&lt;P&gt;Classification authorization g                          ?                                                           BGRKL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard   Authorization for Characteristics of Org. Area               C_TCLS_MNT&lt;/P&gt;&lt;P&gt;Activity                                                           23                                                       ACTVT&lt;/P&gt;&lt;P&gt;Class Type                                                   001                                                      KLART&lt;/P&gt;&lt;P&gt;Organizational Area Indicator                         ?                                                         SICHT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also same thing for this module PP (Production Planning), should I ask my FI/CO or MM functional team to tell me what values should be going into the following authorization Objects&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if anyone knows what values should be entered in the following authorization objects or  Should I talk to my MM functional team to tell me what values should be there because PP is not there expertise thatu2019s what I concern&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard   CC Change Master - Authorization Group                       C_AENR_BGR&lt;/P&gt;&lt;P&gt; Activity                                22                                                                          ACTVT&lt;/P&gt;&lt;P&gt; Authorization Group             ?                                                                            BEGRU&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard   CC Eng. Chg. Mgmt. Enhanced Authorization Check              C_AENR_ERW&lt;/P&gt;&lt;P&gt;   Activity                                                       22                                                        ACTVT\&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AEFUN     ?&lt;/P&gt;&lt;P&gt;AENST     ?&lt;/P&gt;&lt;P&gt;BEGRU    ?&lt;/P&gt;&lt;P&gt;RLKEY    ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance&lt;/P&gt;&lt;P&gt;Faisal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Faisal on Sep 16, 2009 10:03 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Sep 2009 18:36:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088396#M1358197</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-16T18:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Objects field values</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088397#M1358198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It depend on what you want to achieve when &lt;STRONG&gt;using&lt;/STRONG&gt; those transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your functional expert should have worked that out and should give you the values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is your job to consider whether it achieves that which the funkie wants, or whether the choice of transaction is the problem in the first place and conflicting with the role build concept you have given them (or negotiated with them, while explaining the pro's and con's).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you always just "make it work" and insert manually to achieve that then you are defeating the purpose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, think about those who will need to maintain or upgrade these roles in future when the business process, or organization or system technology changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is very easy to dog your own hole by taking a shortcut (or poping a * into a field).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My advise: Give them some feedback. Tell them you want proper information to work with. Have them test it (and do a few negative tests in your free time, also learn the business processes).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My 2 cents,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Sep 2009 20:12:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088397#M1358198</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-16T20:12:30Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Objects field values</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088398#M1358199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First you try to check the documentation of those Objects in SU21 and also in table TOBJ (TOBJT).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For fields and their respective tables, please check them in the table AUTHX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For probable values of the Objects, please check USOBT_C entries. Also you may review the entries in USOTT and in SU22.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know how much of you quires are left now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Dipanjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Sep 2009 20:12:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088398#M1358199</guid>
      <dc:creator>sdipanjan</dc:creator>
      <dc:date>2009-09-16T20:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Objects field values</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088399#M1358200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dipanjan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; First you try to check the documentation of those Objects in SU21 and also in table TOBJ (TOBJT).&lt;/P&gt;&lt;P&gt;In a win :win situation the Security admin would know the objects already and their dependencies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a loose : loose situation the Functional consultant doesn't know the objects and the customizing dependencies either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If all else fails SU24 will help you a part of the way, but it is not caste in stone and you still need to maintain fields which you don't possibly understand, without the help of a good funkie.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Sep 2009 21:09:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088399#M1358200</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-16T21:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Objects field values</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088400#M1358201</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;You can assign those roles to test user in which these objects are.Then ask user to run that test user who needs that t-code.Just on system trace. They will provide some value and you will come to know which value they require.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Sep 2009 12:41:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-objects-field-values/m-p/6088400#M1358201</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-18T12:41:59Z</dc:date>
    </item>
  </channel>
</rss>

