<?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: Return Code 8 tranport request in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622300#M1570393</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;there is no best way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can reduce the difficulties by creating less transports or by merging transports into one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create one transport, create tasks for all the developers.  Ask the developers to keep their developments in a transportable active version - new processes may be temporarily excluded by IF or CHECK statements so that any early transport will not harm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way, transport errors are extremely rare.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Feb 2011 20:59:16 GMT</pubDate>
    <dc:creator>Clemenss</dc:creator>
    <dc:date>2011-02-15T20:59:16Z</dc:date>
    <item>
      <title>Return Code 8 tranport request</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622298#M1570391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Experts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sometimes I am getting Return Code 8 while transporting from DEV System to Q-System because the transport is consisting&lt;/P&gt;&lt;P&gt;of many transport requests and there are as far as I know dependencies between them. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The sequences of the requests must be transported and followed strictly otherwise I am getting RC 8 etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I generally prevent such circumstances. How can I findout generally which transport is the first one... the next one..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Marco&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Feb 2011 20:01:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622298#M1570391</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-15T20:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: Return Code 8 tranport request</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622299#M1570392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On very large changes with many developers, this can be very difficult.  I try to put domains and data elements first, then tables, ending up with programs...But sometimes, the only thing one can do is to go into the target instance and verify that the return code 8 objects activated, and to generate/activate if needed and  possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Feb 2011 20:06:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622299#M1570392</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-15T20:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: Return Code 8 tranport request</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622300#M1570393</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;there is no best way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can reduce the difficulties by creating less transports or by merging transports into one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create one transport, create tasks for all the developers.  Ask the developers to keep their developments in a transportable active version - new processes may be temporarily excluded by IF or CHECK statements so that any early transport will not harm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way, transport errors are extremely rare.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Feb 2011 20:59:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/return-code-8-tranport-request/m-p/7622300#M1570393</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2011-02-15T20:59:16Z</dc:date>
    </item>
  </channel>
</rss>

