Symptom
A customizing transport request that was exported from the customizing tenant(release n) using the Export Customizing Transports app and hasn't been imported the subsequent target tenant(release n+2 or higher) became Outdated.
Environment
SAP S/4HANA Cloud
Cause
As per Transport Dependencies | SAP Help Portal : You can't import a transport created on release n into release n+2 and higher, which means that you have to recreate the transport in the development system. However, it is not possible to recreate CBC transports. In this case, you have to create a support incident.
Resolution
Please follow the below steps to re-transport the configurations recorded in the outdated transports from customizing tenant.
- Create a new customizing request using the app Export Customizing Transports.
- Then, as a developer, use the ADT to open the created request i.e. from Transport Organizer view, right click on the project and click on Open Transport Request or Task.
- Once the request is opened, right click on the request in the Objects section and click on Include Objects-->Add Objects from Request.
- Provide the outdated transport and click on Save button.
- Repeat the step 4 to include the objects from all outdated transports.
- Once all the objects are included, release the task and request using Export Customizing Transports app.
See Also
Export Customizing Transports | SAP Help Portal
Transport Management Summary | SAP Help Portal
3-System Landscape and Transport Management | SAP Help Portal
Keywords
n+2, customizing transport request, outdated, import collection, recreate customizing transport request , KBA , BC-CUS-TOL-CTO , Export Customizing Transports App , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem