Reassigning Change Transactions to Other Change Cycles
You can reassign change transactions to other change cycles. The following conditions apply:
Change Transaction | Target Change Cycle With Task List | Target Change Cycle Without Task List |
|---|---|---|
on a change cycle with / without task list | Allowed | Allowed |
on a change cycle with a task list | Allowed | Not allowed |
on a change cycle without a task list | Not allowed | Not allowed |
Request for change on a change cycle with a task list | Allowed | Not allowed |
Request for change on a change cycle without a task list | Allowed | Allowed |
Note
Normal changes can only be reassigned to other change cycles as long as the change document has not been approved to be imported preliminarily. Once a preliminary import has been started, for example, by importing the original transport of a normal change into a quality assurance system, you can no longer reassign it to another change cycle.
If you have activated central CTS, you can reassign change transactions with released transport requests. The systems between the development and production systems (for example, the quality assurance system) in a transport track can differ between the source and target cycles. The system displays a warning message if released transport requests exist and the source and target landscapes (including all transport tracks and all cluster assignments in the transport tracks) are not identical. The warning message says that the import buffer of the affected systems needs to be adjusted after the reassignment.
Caution
Reassign a change to another change cycle with caution because not only the change documents are affected, but also the source and target cycles.
We recommend that you do not reassign urgent changes.
Prerequisites
You can only reassign a change if the following prerequisites are fulfilled:
All transports of copies of the original transport requests have been imported before you can reassign a normal change.
If you have not activated the central Change and Transport System (central CTS) for your change cycle, all transport requests of the change must be modifiable. If you have activated central CTS, this prerequisite does not apply.
The current status of the change document allows the change to be reassigned. You can define this in Customizing under
SAP Solution Manager
Capabilities (Optional)
Change Control Management
Change Request Management Framework
Adjust UI Objects by User Status
. NoteBy default, the change document needs to have the status “In Development” for you to reassign it. However, you can change this in Customizing.
End of the note.Change documents that have an ITPPM project assigned must be allowed to be reassigned to another cycle. If the ITTPM project does not allow the transaction to be reassigned, the system displays an error message.
You can only reassign a change if the following prerequisites for the target change cycle are met, that is, for the cycle to which the change is to be reassigned.
For the transport requests of the change, the respective development systems need to be available as the target cycle's development systems.
The production system that is identified by the IBase component of the change needs to be available in the target cycle. Its system role type is
production system
.The target change cycle is not the source change cycle.
The phase of the target cycle allows the change to be reassigned.
For more information about the status of the change transactions to be reassigned and the phases of the target change cycles, see Reassigning Change Transactions: Statuses and Change Cycle Phase.
Activities
To reassign a change document to another change cycle, proceed as follows:
In the change document, choose
More
Change Cycle Assignment
.The system displays a dialog box.
Search for the change cycle to which you want to reassign the change.
Select the cycle and choose
Reassign Change Transaction
.
Note
If a change document is linked to a request for change that contains more than one document, the change document is unlinked from the request for change.
If a change document is linked to a request for change that only contains one document, the request for change is reassigned to the target cycle as well.