3734559 - Transport Request status shows "Set to outdated" in the app "Import Collection" after system upgrade– SAP S/4HANA Cloud Public Edition

The transport request status shows "Set to outdated" and cannot be imported anymore.

SAP S/4HANA Cloud Public Edition

An outdated collection version can’t be imported anymore. The collection version is automatically set as outdated when the release at export is older than the current release according to the following rules:

• In 2SL: Collection versions of the type Key User Extensibility are set as outdated after one or two releases, depending on the content of the collection. Collection versions of the type Customizing are set as outdated after one release.
• In 3SL: Collection versions of the type Customizing are set as outdated only after two releases. Collection versions of the type Key User Extensibility are set as outdated after one or two releases, depending on the content of the collection.

It is not possible to import a transport created on release n into release n+2 and higher, which means that it is needed to recreate the transport in the development system.

Refer to 3610869 - 3-System Landscape: Downward Compatibility Rule - SAP for Me 

Note :As mentioned in the document Transport Dependencies | SAP Help Portal , It is not possible to recreate CBC transports. In this case, need to create a support incident.

3557161 - How to import Outdated customizing type of transport request to test system and production system? - SAP S/4HANA Cloud Public Edition - SAP for Me

Transport Dependencies | SAP Help Portal

3610869 - 3-System Landscape: Downward Compatibility Rule - SAP for Me

Transport request, set to outdated, CBC transports , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem