<?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 Write-protected sources in Eclipse after changing Original System in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protected-sources-in-eclipse-after-changing-original-system/m-p/12699037#M2018233</link>
    <description>&lt;P&gt;For a package coming from a different system, I have mass-changed its Original System to match the current system. SE03 shows, that all objects were affected by the change, SE80 opens the code without modification assistant.&lt;/P&gt;
  &lt;P&gt;Eclipse ADT also opens the files without warning, but there are two classes that open in Eclipse write-protected (in the screenshot only line 59 is editable). The same classes open in SE80 without any limitations.&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2123772-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;What can be wrong with those two classes, how can I fix that? There are also FMs in the same subpackage, they open without write-protection. &lt;/P&gt;</description>
    <pubDate>Thu, 22 Dec 2022 14:07:39 GMT</pubDate>
    <dc:creator>yuriy_dzhenyeyev</dc:creator>
    <dc:date>2022-12-22T14:07:39Z</dc:date>
    <item>
      <title>Write-protected sources in Eclipse after changing Original System</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protected-sources-in-eclipse-after-changing-original-system/m-p/12699037#M2018233</link>
      <description>&lt;P&gt;For a package coming from a different system, I have mass-changed its Original System to match the current system. SE03 shows, that all objects were affected by the change, SE80 opens the code without modification assistant.&lt;/P&gt;
  &lt;P&gt;Eclipse ADT also opens the files without warning, but there are two classes that open in Eclipse write-protected (in the screenshot only line 59 is editable). The same classes open in SE80 without any limitations.&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2123772-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;What can be wrong with those two classes, how can I fix that? There are also FMs in the same subpackage, they open without write-protection. &lt;/P&gt;</description>
      <pubDate>Thu, 22 Dec 2022 14:07:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protected-sources-in-eclipse-after-changing-original-system/m-p/12699037#M2018233</guid>
      <dc:creator>yuriy_dzhenyeyev</dc:creator>
      <dc:date>2022-12-22T14:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: Write-protected sources in Eclipse after changing Original System</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protected-sources-in-eclipse-after-changing-original-system/m-p/12699038#M2018234</link>
      <description>&lt;P&gt;Did you check whether the affected objects are considered as modified? You can check this in the modification browser (transaction SE95).&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 08:46:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protected-sources-in-eclipse-after-changing-original-system/m-p/12699038#M2018234</guid>
      <dc:creator>schneidermic0</dc:creator>
      <dc:date>2023-01-03T08:46:40Z</dc:date>
    </item>
  </channel>
</rss>

