<?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: Obsolete authorization objects in APO in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433373#M1647807</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anika,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;have a look at SU21-&amp;gt;class AAAA (Obsolete authorization objects).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally objects contained in that class are really obsolete, so trying to insert them into a profile does not make too much sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use such objects for instance in own coding, either&lt;/P&gt;&lt;P&gt;a)change your coding to a still valid object&lt;/P&gt;&lt;P&gt;b)change your coding to a Z-object (won't get affected at upgrades)&lt;/P&gt;&lt;P&gt;c)worst option: change (modify) the obsolete object and chagne its class assignement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b.rgds, Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Dec 2011 06:38:21 GMT</pubDate>
    <dc:creator>Bernhard_SAP</dc:creator>
    <dc:date>2011-12-21T06:38:21Z</dc:date>
    <item>
      <title>Obsolete authorization objects in APO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433371#M1647805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have to create one role in APO in which I have to manually insert authorization objects.When I try to do so, for some authorization objects I get error message "Authorization object is obsolete" and the authorization object does not get inserted.This might have happened because of upgrade.&lt;/P&gt;&lt;P&gt;Is there anyway to determine how to find authorization object corresponding to obsolete authorization objects in upgraded system?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: AnikaGupta on Dec 20, 2011 1:41 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 12:40:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433371#M1647805</guid>
      <dc:creator>former_member230681</dc:creator>
      <dc:date>2011-12-20T12:40:45Z</dc:date>
    </item>
    <item>
      <title>Re: Obsolete authorization objects in APO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433372#M1647806</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;&lt;/P&gt;&lt;P&gt;I don't have much experience with APO security specifically or with regards to do what do with obsolete objects; but in general - I would say that obsolete auth object's description/documentation would provide hints to the object which should replace the object in context (for example object S_XMB_DSP). I would like to ask as to why are you trying to add this object manually - accepting if its an exception/necessary but see if you can resolve it by t-code addition in menu and checking what all auth objects are pulled - and building a solution based on SU24 proposals (depends if the obsolete object is called for this transaction in SU24 - maybe it does not)  -  if its an obsolete object you might want to edit its status in SU24 as do not check (apart from basis/hr objects)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 20:34:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433372#M1647806</guid>
      <dc:creator>former_member204634</dc:creator>
      <dc:date>2011-12-20T20:34:45Z</dc:date>
    </item>
    <item>
      <title>Re: Obsolete authorization objects in APO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433373#M1647807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anika,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;have a look at SU21-&amp;gt;class AAAA (Obsolete authorization objects).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally objects contained in that class are really obsolete, so trying to insert them into a profile does not make too much sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use such objects for instance in own coding, either&lt;/P&gt;&lt;P&gt;a)change your coding to a still valid object&lt;/P&gt;&lt;P&gt;b)change your coding to a Z-object (won't get affected at upgrades)&lt;/P&gt;&lt;P&gt;c)worst option: change (modify) the obsolete object and chagne its class assignement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b.rgds, Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Dec 2011 06:38:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/obsolete-authorization-objects-in-apo/m-p/8433373#M1647807</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2011-12-21T06:38:21Z</dc:date>
    </item>
  </channel>
</rss>

