cancel
Showing results for 
Search instead for 
Did you mean: 

Transport with SPS upgrades in different environments

Former Member
0 Kudos

Experts,

Does anyone know if there are any compability issues when we are moving transports from environment  A to environment B and vice versa. Environment A has SPS 11 upgrade and Environment B doesnt have the upgrade.

Would this cause any error while moving transports?

Thanks,

Ketul

Accepted Solutions (1)

Accepted Solutions (1)

paul_power
Active Contributor

Dear Ketul,

Yes, it is dangerous to transport between system of different sp levels.

For example, if you transport the higher release SP11 into a system that is at a lower release, then objects in the transport may include or relly on objects which dont yet exist in the target system as they were brought in with the newer support packages.

Transports should only be done between like for like systems. Transporting from a lower release to a higher release is less risky.

regards,

Paul

Former Member
0 Kudos

Thanks Paul for your reply!

tomas_black
Active Contributor
0 Kudos

Hello Ketul,

adding to Paul's information, there's a new 'check' that can be done when transporting CRs throughout your landscape. It is the unconditional mode "Ignore Invalid Component Version".

This feature (check the component version) was included with SAP_BASIS 702, so the tp checks the component version of the system where the transport was released (this information is included in the transport) and the component version of the system where the transport is going to be imported.

 

This component version check feature will check all the components version between source and target system. So before choosing the 'Ignore' option, please try to make sure that the software component version that the objects contained in the request belongs to, should be the same between the systems, to avoid any inconsistencies. It is recommended to transport request in systems which are on the same support level or use the same add-ons.

 

The component check is a hint that you will import a transport which come from a system which is different from the target system. It only checks the installed add-ons and support packages. This means if you have in the source system installed a add-on which is not present in the target system of the transport you should aware that you import no objects which depends on the add-on which is not present in the target system, the same point belongs also to different support package

releases. This option was implemented to reduce the risk of inconsistencies. If you import the transport please use transport option "ignore invalid component version".

 

This import option means that transport requests can be imported even if  their component version does not match the current component version (including Support Package Level) of the system. This is the case if the component version of the system is either new (the Support Package Level

is higher than that of the export system) or too old (you first have to have imported the Support Packages before you can import the request). You should only use this option if you are sure that the content of the transport request is independent from the component version.

If it is required to avoid this check you could set transport parameter SP_TRANS_SYNC with value OFF and this check will be not performed from tp, but I would recommend to use import option "ignore invalid component version" before you would import the transport.

transport parameter SP_TRANS_SYNC = OFF.

Parameter SP_TRANS_SYNC is delivered ON by default.

This option will avoid the check of the component version.

Some notes regarding this feature:

1581638 - SAP component checks no longer working in TMS

1577714 - Transport requests in Check requirements phase

1650265 - TMS workflow: 'Ignore Invalid Component Version' missing

1742547   Information about component version check in TMS

1756116   TMS Component Check: Fix for excluded component logic

Best regards,

Tomas Black

Former Member
0 Kudos

Thanks Tomas for your response.

Answers (0)