<?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 Merging Object Lists - Specific Versions in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/merging-object-lists-specific-versions/m-p/1687373#M302416</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'm on ECC 5.0 and have a problem that I was hoping Merge Object Lists (SE03 - RSWBOSSR) would solve.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our development system has multiple projects going on concurrently.  For example I may create a program for Project 1 that is going to go to production in January.  Through testing etc. I end up created 4 versions of the program all related to the January project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After I'm done with the changes, but before it has transported to production, another developer makes a new version (5) of the program for the February project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rather than transport versions 1 through 4 to production for the January project, I really only need version 4 to transport.  I thought I could run the Merge Object Lists program for the 4 CTS's I created related to the January project and it would create a new CTS with just version 4 in it.  However, it is really grabbing version 5 and putting that in the new CTS.  So if I transport this to production for the January project, I am really sending code that shouldn't go until February.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyway around this problem other than sending all 4 versions to production in their original CTSs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Nov 2006 17:48:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-11-06T17:48:45Z</dc:date>
    <item>
      <title>Merging Object Lists - Specific Versions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/merging-object-lists-specific-versions/m-p/1687373#M302416</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'm on ECC 5.0 and have a problem that I was hoping Merge Object Lists (SE03 - RSWBOSSR) would solve.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our development system has multiple projects going on concurrently.  For example I may create a program for Project 1 that is going to go to production in January.  Through testing etc. I end up created 4 versions of the program all related to the January project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After I'm done with the changes, but before it has transported to production, another developer makes a new version (5) of the program for the February project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rather than transport versions 1 through 4 to production for the January project, I really only need version 4 to transport.  I thought I could run the Merge Object Lists program for the 4 CTS's I created related to the January project and it would create a new CTS with just version 4 in it.  However, it is really grabbing version 5 and putting that in the new CTS.  So if I transport this to production for the January project, I am really sending code that shouldn't go until February.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyway around this problem other than sending all 4 versions to production in their original CTSs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Nov 2006 17:48:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/merging-object-lists-specific-versions/m-p/1687373#M302416</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-06T17:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: Merging Object Lists - Specific Versions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/merging-object-lists-specific-versions/m-p/1687374#M302417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jeff,&lt;/P&gt;&lt;P&gt;Activate the versions (in ur case make version 4 as active version) of all objects which you need to transport for january production. While doing so the SAP will ask for new request..create this and transport to production.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After releasing the above request the jan project is send to prod.&lt;/P&gt;&lt;P&gt;Now come back to your dev and again make version 5 as active version for all the objects which u r planning 2 send in FEB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats all ur job is done.. project 1 of jan is in prod and proj2 for FEB in dev ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if u need more inputs on this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enjoy SAP.&lt;/P&gt;&lt;P&gt;Pankaj Singh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Nov 2006 18:00:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/merging-object-lists-specific-versions/m-p/1687374#M302417</guid>
      <dc:creator>messier31</dc:creator>
      <dc:date>2006-11-06T18:00:20Z</dc:date>
    </item>
  </channel>
</rss>

