Component Version Mismatch problem - Affected Urgent Change

[Former Member]

Hi Experts,

There is a component version mismatch and due to this in an urgent change transports are not getting imported into test system on status change. As a result status change fails (To Be Tested) and resets back to 'In Development'.

So to import transport into test system import option 'Ignore invalid component version' needed to choose for each urgent change. Is there any way to automate transport import into test system (for urgent change only) having component version mismatch problem.

Br,

Omkar

[Former Member]

Hi Rishav,

Thanks for the information. According to KBA 2025332 component version check parameter has to keep off at STMS level to bypass this situation.

If we deactivate component version check then will there be any effect on production system import ?

and also if we need to keep component version check active and automate the import procedure by ignoring 'component version mismatch' then is there any way out.

Br,

Omkar

[rishav54]

Hi Omkar

It should not have any production system import issue.

However, there is one alternative , there is one table where you can maintain which component version mismatch you want to ignore. Check with your basis team once.

Also check below

1744389 - ChaRM & QGM: import fail due to invalid component version

1581638 - SAP component checks no longer working in TMS

Thanks

Rishav

[Former Member]

Hi Omkar,

You should deactivate the component version check in stms configuration.

But be careful, you should know that you maybe have issues if the source system have an version more actualized than the QA and Prod system.

Best regards and good luck

José Henrique

[rishav54]

Hi Omkar

It is known issue, find below the note for same.

• 2025332 - Urgent change import fails with requests does not match the component version of the targe... 

  Thanks

  Rishav