<?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>Question Re: Does not match component version in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497238#M3019743</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aidan, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the information.Is it ok If I don't set the parameter, atleast we are aware that the transports have component mismatch and we should have problems if we import the transport. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best practice followed? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards!! &lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Jan 2012 09:39:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2012-01-18T09:39:26Z</dc:date>
    <item>
      <title>Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaq-p/8497236</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;We have four system landscape. We have already upgrade our DEV and ITT to EHP5.We still have to upgrade our UAT and prod to EHP5. When I see the transport queue on ITT system.I see all the transport that was imported on ITT before the upgrade is showing as "Does not match component version".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can understand that the version before the upgrade was different so it should show that message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just wanted to check if this is normal or I need to make changes to TMS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 09:27:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaq-p/8497236</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-18T09:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497237#M3019742</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;You can do as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Switch it off with parameter : SP_TRANS_SYNC = OFF&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call transaction STMS&lt;/P&gt;&lt;P&gt;Goto 'Systems Overview'&lt;/P&gt;&lt;P&gt;Double click &amp;lt;SID&amp;gt; you wish to add the parameter to&lt;/P&gt;&lt;P&gt;Goto 'Transport Tool' tab&lt;/P&gt;&lt;P&gt;Goto 'change mode'&lt;/P&gt;&lt;P&gt;Add  SP_TRANS_SYNC  to parameter column and OFF to value column&lt;/P&gt;&lt;P&gt;Save, activate and distribute&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Version SAP_BASIS 702 a new feature was added to the TMS system,&lt;/P&gt;&lt;P&gt;tp is now checking the component version of the transport which was&lt;/P&gt;&lt;P&gt;released and the component version of the system where the transport is&lt;/P&gt;&lt;P&gt;going to be imported. If there is a difference, this difference is&lt;/P&gt;&lt;P&gt;highlighted in the import queue (transaction stms_import) and if you try&lt;/P&gt;&lt;P&gt;to import the transport, the import will stop with a warning message&lt;/P&gt;&lt;P&gt;about the difference in the SAPCOMPONENT versions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you wish to by-pass with warning then you can choose 'Ignore invalid&lt;/P&gt;&lt;P&gt;Component version'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aidan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 09:34:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497237#M3019742</guid>
      <dc:creator>former_member264034</dc:creator>
      <dc:date>2012-01-18T09:34:17Z</dc:date>
    </item>
    <item>
      <title>Re: Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497238#M3019743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aidan, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the information.Is it ok If I don't set the parameter, atleast we are aware that the transports have component mismatch and we should have problems if we import the transport. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best practice followed? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards!! &lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 09:39:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497238#M3019743</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-18T09:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497239#M3019744</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;Please be aware that SAP does not recommend to switch off the&lt;/P&gt;&lt;P&gt;component version check in general.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would advise though to leave it on and tick the relevant option&lt;/P&gt;&lt;P&gt;on a need basis only, once you have taken the warning into&lt;/P&gt;&lt;P&gt;consideration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As reference for the parameter please see SAP notes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; #[1581638  |http://service.sap.com/sap/support/notes/1581638]SAP component checks no longer working  in TMS&lt;/P&gt;&lt;P&gt; #[1577714  |http://service.sap.com/sap/support/notes/1577714]Transport requests in Check requirements phase&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aidan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 09:43:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497239#M3019744</guid>
      <dc:creator>former_member264034</dc:creator>
      <dc:date>2012-01-18T09:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497240#M3019745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ravi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i would strongly advise you to go thru Note 1090842 - Composite note: Transport across several releases as transport from different version is not a good practise. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Nicholas Chang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 09:50:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497240#M3019745</guid>
      <dc:creator>nicholas_chang</dc:creator>
      <dc:date>2012-01-18T09:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497241#M3019746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nicholas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are not doing any transport betweent the different release.I just wanted to check if its normal message that is being displayed,as we are in porcess of EHP upgrade and yet we stillh ave to upgrade UAT and Prod environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also after the EHP5 do I have to live with this in my STMS queue or I can should deactivate it as Aidan suggested?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards!!&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 10:48:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497241#M3019746</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-18T10:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Does not match component version</title>
      <link>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497242#M3019747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ravi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What adrian advised is correct, this is normal when different components in your STMS landscape as for 702 release. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers, &lt;/P&gt;&lt;P&gt;Nicholas Chang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 11:47:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/does-not-match-component-version/qaa-p/8497242#M3019747</guid>
      <dc:creator>nicholas_chang</dc:creator>
      <dc:date>2012-01-18T11:47:10Z</dc:date>
    </item>
  </channel>
</rss>

