<?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: Difference between Change Authorization Data / Display Authorization Data in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099606#M1616229</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually I started off my question with the "implementation of treble control" that SAP course AD940 suggests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending upon the volume of work my SAP implementation has, the approarch to me looks practical.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Secondly, SAP profile is also available for these adminstrators but it is not working the way it is supposed to.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 17 Jul 2011 12:49:06 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-07-17T12:49:06Z</dc:date>
    <item>
      <title>Difference between Change Authorization Data / Display Authorization Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099604#M1616227</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is wrt to implementation of "principle of treble control" i.e three SAP administrators i.e. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Authorization data administrator&lt;/P&gt;&lt;P&gt;2. Authorization profile administrator&lt;/P&gt;&lt;P&gt;3. User Administrator&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have created a role &amp;amp; added a transaction to it e.g. "FAGLL03" or "FF67".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No authorization data is displayed in the authorization tab unless I enter authorization tab with change button and provide inputs for org level field &amp;amp; generate profile. Even when I save the profile with the proposed name, it status still says "No authorization data exists". Since no authorization data is available, administrator 2 is unable to generate profile. If administrator 1 has to generate profile then why is administrator 2 required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Definition of Administrator 1 is:&lt;/P&gt;&lt;P&gt;The authorization data administrator creates the roles, selects transactions and&lt;/P&gt;&lt;P&gt;maintains the authorization data. He or she simply saves the data in the Profile&lt;/P&gt;&lt;P&gt;Generator since he does not have the necessary authorization for generating the&lt;/P&gt;&lt;P&gt;profile. He or she accepts the proposed profile name &amp;#147;T-...&amp;#148;. The authorization data&lt;/P&gt;&lt;P&gt;administrator may not change users, nor generate profiles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Definition of Administrator 2 is:&lt;/P&gt;&lt;P&gt;The authorization profile administrator starts transaction &amp;#147;SUPC&amp;#148; and chooses All&lt;/P&gt;&lt;P&gt;Roles. He or she then restricts his selection, for example by entering the ID of the&lt;/P&gt;&lt;P&gt;role to be edited. On the next screen, he or she chooses Display Profile to check&lt;/P&gt;&lt;P&gt;the data. If all the data is correct, he or she generates the authorization profile. The&lt;/P&gt;&lt;P&gt;authorization profile administrator may not change users, change the data for roles,&lt;/P&gt;&lt;P&gt;nor generate profiles containing authorization objects beginning with S_USER*.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jul 2011 09:33:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099604#M1616227</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-07-17T09:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Change Authorization Data / Display Authorization Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099605#M1616228</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If administrator 1 has to generate profile then why is administrator 2 required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I think that is the question you need to get answered. What risk is there if you combine the two functions? I do not see why one would try to separate the creation of the roles and the generation of the profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you tell us why it has been designed in this way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jul 2011 09:51:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099605#M1616228</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2011-07-17T09:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Change Authorization Data / Display Authorization Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099606#M1616229</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually I started off my question with the "implementation of treble control" that SAP course AD940 suggests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending upon the volume of work my SAP implementation has, the approarch to me looks practical.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Secondly, SAP profile is also available for these adminstrators but it is not working the way it is supposed to.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jul 2011 12:49:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099606#M1616229</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-07-17T12:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Change Authorization Data / Display Authorization Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099607#M1616230</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually I started off my question with the "implementation of treble control" that SAP course AD940 suggests.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I had never heard of this treble control and the added value of splitting rolebuilding and profile generation doesn't make much sense to me but that's my personal opinion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the technical side of things: in your first post you state "No authorization data is displayed in the authorization tab unless I enter authorization tab with change button and provide inputs for org level field &amp;amp; generate profile." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is also possible to change the data and save this but not generate the profile yet. I just tried this by doing the following:&lt;/P&gt;&lt;P&gt;Create role&lt;/P&gt;&lt;P&gt;Add transactions to menu&lt;/P&gt;&lt;P&gt;Edit profile, org levels &amp;amp; authroization data.&lt;/P&gt;&lt;P&gt;Hit 'save'.&lt;/P&gt;&lt;P&gt;Accept proposed profile name.&lt;/P&gt;&lt;P&gt;Go back to PFCG main screen and ignore message of profile not being generated. (Click 'continue')&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And this leaves me with a role with yellow traffic light on the authorization tab an the profile status is: "Current version not generated"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it should be possible to maintain roles and profiles separately.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jul 2011 13:06:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099607#M1616230</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2011-07-17T13:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Change Authorization Data / Display Authorization Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099608#M1616231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;Actually I started off my question with the "implementation of treble control" that SAP course AD940 suggests.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;The standard role SAP_BC_ENDUSER mentioned in that course is typically enough to perform all three tasks anyway...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, with modern workflows and provisioning this double and triple concept decreasingly relevant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A better option would be to implement a QA step in the transporting of the roles and profiles. That will still be with us for some time to come IMHO. You can also integrate other checks into the CTS.&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>Sun, 17 Jul 2011 20:27:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-change-authorization-data-display-authorization-data/m-p/8099608#M1616231</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-07-17T20:27:13Z</dc:date>
    </item>
  </channel>
</rss>

