In system landscapes in which several releases are processed at the same time, changes can be made in different development systems: new developments can be made in the development system, and errors can be corrected or improvements can be made in a maintenance system for the production system landscape, at the same time. The system release levels must be adjusted regularly. Changes are made in parallel, so changes cannot be transport between systems in requests, because current software can be overwritten and inconsistencies can occur. To avoid this, import into the target system is controlled. This is called retrofitting.
A logical component in the SAP Solution Manager project contains at least one system with the role Retrofit System.
You have performed the task Assign Retrofit System to Development Systems in the overview of the task list, to specify into which system changes are to be imported.
When you define retrofit systems, the system only offers you transport requests from the maintenance systems you assigned to the development systems when you started the retrofit. If you have not made any assignments, the system offers you all transport requests from all
maintenance systems, when you start the retrofit.
You have created and saved BC sets in the maintenance system, to be able to transfer customizing settings from the maintenance system into the retrofit system.
For more information, see SAP Note 669542 and under Creating Business Configuration Sets and Activating Business Configuration Sets. The also applies to handling deleted objects in BC Sets.
You have created transport requests for the retrofit in the retrofit system into which you want to import the changes from the maintenance system.
Retrofit is available as part of Enterprise Edition for Solution Manager. There are no specific T-Codes, but rather actions in the Task List of a Solution Manager CHaRM enabled project. See this link on the service marketplace for a brief slide deck with some screen shots.
No comments:
Post a Comment