<?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 su21 - edit existing object? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/su21-edit-existing-object/m-p/796805#M40531</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;
  &lt;P&gt;I have created authorization object and I have used the same object in Program .Authorization object assigned in role as well . Role also moved to production and program also moved to production. Now authorization object working in lIve. My requirement is one more filed is required in same authorization object for further correction. But system says&lt;/P&gt;
  &lt;P&gt;below&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/303415-capture.png" /&gt;&lt;/P&gt;
  &lt;P&gt;How to solve it.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:11:12 GMT</pubDate>
    <dc:creator>sivakumar_mobility</dc:creator>
    <dc:date>2019-03-12T05:11:12Z</dc:date>
    <item>
      <title>su21 - edit existing object?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/su21-edit-existing-object/m-p/796805#M40531</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
  &lt;P&gt;I have created authorization object and I have used the same object in Program .Authorization object assigned in role as well . Role also moved to production and program also moved to production. Now authorization object working in lIve. My requirement is one more filed is required in same authorization object for further correction. But system says&lt;/P&gt;
  &lt;P&gt;below&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/303415-capture.png" /&gt;&lt;/P&gt;
  &lt;P&gt;How to solve it.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:11:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/su21-edit-existing-object/m-p/796805#M40531</guid>
      <dc:creator>sivakumar_mobility</dc:creator>
      <dc:date>2019-03-12T05:11:12Z</dc:date>
    </item>
    <item>
      <title>Re: su21 - edit existing object?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/su21-edit-existing-object/m-p/796806#M40532</link>
      <description>&lt;P&gt;First you should read some OSS note &lt;A href="https://launchpad.support.sap.com/#/notes/2650524"&gt;2650524 - SU21 maintenance to existing custom objects not possible.&lt;/A&gt; (with referenced note that implemented the checks &lt;A href="https://launchpad.support.sap.com/#/notes/1135888"&gt;1135888 - SU21: General optimization&lt;/A&gt;)&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;'Create the SAP authorization objects with the utmost caution. After the creation, you can change the authorization field assignments only if the relevant transport request has not been exported yet. In addition, deleting or recreating the object no longer works after this&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;The standard solution is now &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;'move the object to the "obsolete authorization objects" object class and create a suitable new authorization object.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Then change every call of authorization objects and role containing the obsolete object in your system.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:52:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/su21-edit-existing-object/m-p/796806#M40532</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2019-03-12T06:52:27Z</dc:date>
    </item>
  </channel>
</rss>

