Managing Software Collection transports during the... - SAP Community
source link: https://community.sap.com/t5/technology-blogs-by-sap/managing-software-collection-transports-during-the-upgrade-phase-for/ba-p/13587841
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Dear Community,
- Export from the development system.
- Import into the test system.
- Forward from the test system.
- Import into the production system.
Scenario 2: Development System is on Release n, Test System on n+1 and Production System on Release n.
For Key User Extensibility, you can:
- Export from the development system
- Import into the test system*
- Forward from the test system
- Import into the production system
*The capability to import into the test system depends on the content of the key user extensibility transport. Some key user items are not yet enabled to be imported into release n+1. Transport with these content types are flagged as outdated in the test system.
For Developer Extensibility and Customizing transports, you can:
- Export from the development system
- Import into the test and production system
Scenario 3: Transports on Release n and All Systems on Release n+1.
For Key User Extensibility, you can:
- Export from the development system
- Import into the test system*
- Forward from the test system
- Import into the production system
*The capability to import into the test system depends on the content of the key user extensibility transport. Some key user items are not yet enabled to be imported into release n+1. Transport with these content types are flagged as outdated.
If the import into the production system is not possible (transport is outdated), you can re-export the same content again.
For Developer Extensibility and Customizing Transports, you can:
- Import into the test and production system (for transports created on release n and n+1)
As mentioned above, some key user items are not yet enabled to be imported into higher releases and transport with these content types might result in issues in your system.
Therefore, it's important to know how to check which items are enabled for importing in n+1 releases. Check the step by step below:
- In your S/4HANA Cloud System, go to Extensibility Settings app
- In Key User Namespaces section, click on your namespace
- Go to "Supported Item Types" tab
- Check the "Import to Higher Version Supported" column. The items with "yes" can be imported to higher releases.
I want to highlight the importance of planning your transports during the Upgrade period, because the development and production system are upgraded to n+1 only after a certain period of time and at this point, you may not be able to import older key user extensibility transports that were created on release n.
Before the upgrade deployment, there's also the preprocessing phase where transports are not allowed. This is described in the maintenance schedule according to the System Landscape:
I hope this blog was helpful for the process of transporting releases during upgrade period.
Below there are some references with detailed information about more specific topics related to Transport Management and Software Collections:
Thank you & Best Regards,
Tayane.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK