<?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: very important OSS Note issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921408#M939512</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Gaurav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From my understanding, this note was two steps of implementation:&lt;/P&gt;&lt;P&gt;- Manual steps&lt;/P&gt;&lt;P&gt;- Program corrections&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In manual steps, it seems you have to use transaction SE01 to change some configuration. To do this, check:&lt;/P&gt;&lt;P&gt;- Enter SE01 transaction&lt;/P&gt;&lt;P&gt;- Click on icon 'Transport Organizer Tools'&lt;/P&gt;&lt;P&gt;- Double click on entry 'Display/Change Namespaces'&lt;/P&gt;&lt;P&gt;- Search for entry namespace /SAPDMC/ and change 'namespace role' attribute from P to C.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For program corrections, you can implement them using SNOTE. It is the most recomended procedure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that this may help you.&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 08 Jun 2008 18:26:30 GMT</pubDate>
    <dc:creator>BGarcia</dc:creator>
    <dc:date>2008-06-08T18:26:30Z</dc:date>
    <item>
      <title>very important OSS Note issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921407#M939511</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;i have to implement an OSS Note 409645 .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we need to do very small changes in Program  /SAPDMC/LLSMW_GLO_020F03.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But we are getting information message '' No valid change license available for namespace /SAPDMC/  ''  after this action terminates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i am unable to understand some points mentioned in description of OSS Note&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can any one please help me in understanding it and help us how to implement this note&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Long Text&lt;/P&gt;&lt;P&gt;  Symptom&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When importing a project (export/import via text files), the following&lt;/P&gt;&lt;P&gt;error occurs:&lt;/P&gt;&lt;P&gt;Error while importing project xxxxxxx (table /SAPDMC/LSMCUST)&lt;/P&gt;&lt;P&gt;Message number /SAPDMC/LSMW_GLO_010046&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Additional key words&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Cause and preconditions&lt;/P&gt;&lt;P&gt;  The error was caused by an incorrectly exported record.&lt;/P&gt;&lt;P&gt;  Solution&lt;/P&gt;&lt;P&gt;  If you have not yet done so, change the namespace role of the /SAPDMC/&lt;/P&gt;&lt;P&gt;  namespace from 'P' to 'C' using the tools in transaction SE01.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Then implement the attached correction in the include&lt;/P&gt;&lt;P&gt;  /SAPDMC/LLSMW_GLO_020F03 of the exporting system.&lt;/P&gt;&lt;P&gt;  Repeat the export, the export should then no longer export the incorrect&lt;/P&gt;&lt;P&gt;  line. After that, repeat the import into the target system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2008 09:35:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921407#M939511</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-06T09:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: very important OSS Note issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921408#M939512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Gaurav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From my understanding, this note was two steps of implementation:&lt;/P&gt;&lt;P&gt;- Manual steps&lt;/P&gt;&lt;P&gt;- Program corrections&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In manual steps, it seems you have to use transaction SE01 to change some configuration. To do this, check:&lt;/P&gt;&lt;P&gt;- Enter SE01 transaction&lt;/P&gt;&lt;P&gt;- Click on icon 'Transport Organizer Tools'&lt;/P&gt;&lt;P&gt;- Double click on entry 'Display/Change Namespaces'&lt;/P&gt;&lt;P&gt;- Search for entry namespace /SAPDMC/ and change 'namespace role' attribute from P to C.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For program corrections, you can implement them using SNOTE. It is the most recomended procedure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that this may help you.&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Jun 2008 18:26:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921408#M939512</guid>
      <dc:creator>BGarcia</dc:creator>
      <dc:date>2008-06-08T18:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: very important OSS Note issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921409#M939513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Nov 2011 03:34:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/very-important-oss-note-issue/m-p/3921409#M939513</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-10T03:34:57Z</dc:date>
    </item>
  </channel>
</rss>

