In any implementation, upgrade, template or maintenance project, you must activate Change Request Management if you want to work with requests for change in the respective project. You can also make other settings and perform checks in the project administration.
In the project administration, you can make the following settings under
Activate Change Request Management
If you select this indicator, all systems of a logical component are selected on the Systems
tab page and are thus included in change request management.
You can now start managing all changes in the system landscape using requests for change. Transports are then only possible in conjunction with change request management.
Mark the Use Central Change and Transport Infrastructure
checkbox if you want to activate enhanced flexibility features for change request management based on the central Change and Transport System (central CTS) infrastructure. For more information, see Change Control Management Using Central Change and Transport System.
Assign System Clusters
This checkbox is displayed, if you have activated central CTS for your project. You can assign system clusters to the displayed system roles.
If the value help for system clusters and domains is empty, there is no transport route from the already defined system clusters to the system cluster you would like to choose. In order to check the transport routes of your cluster configuration, choose Go to Cluster Configuration
.
If no task list has been created yet, you can change the cluster assignment. Choose Reset System Cluster Assignment
to do so. All assignments are deleted and you can assign the clusters anew.
If your system landscape has changed, you cannot change the cluster assignment manually if a task list has been created for the project. The cluster assignment is automatically recovered from historical transport tracks, and this assignment cannot be changed. You can assign clusters for Change Request Management only, and you are not allowed to add new systems.
After you have finished the system cluster assignment, save your data.
Assign Variant for Task List
You can choose from two SAP standard variants with different transport procedures to the production system: You use SAP0 if you work with urgent and normal corrections. You use SAP1 if you only work with urgent corrections.
Create Task List
The system creates a project or a maintenance cycle and a task list.
Show Task List
You display the generated task list. The task list receives all jobs (methods) that must or can be executed for a project.
Display Change Cycle
You can access the processing functions for the project or maintenance cycle in the WebClient UI and change the phase, for example. For more information, see Processing a Project Cycle and Processing a Maintenance Cycle.
Refresh
Updates the settings that have been made for the project, for example, with regard to the transport tracks. If errors occur, the system displays a message telling you what to change. Otherwise, it displays an information message and a task list can be created.
Check
You can check the configuration of a project and display details for the individual results. For more information, see Configuration Check.
Task Lists
You can view all task lists, change documents, project and maintenance cycles, and other data assigned to the project, and can display related detail information.
Trans. Monitor
Go to transaction monitor for list display of service transactions
Quality Gate Management
For more information, see Checking the Quality Gate Configuration.
A Change Request Management project is locked in table /TMWFLOW/PROJMAP
if your STMS configuration and your logical component definition are not consistent with each other.
Note
Clarify first that the project is locked for all the logical components, for all TMS landscapes managed in the project, and not only for the TMS landscape.
A Change Request Management project is locked if one of the following conditions applies:
Domain controller system is unavailable
No transport should be performed in this transport domain. As Change Request Management cannot retrieve the STMS configuration, a consistency check is not possible and the project is locked. For more information, see SAP Note 1322696.
An RFC destination to a managed system is not working correctly, because of a momentary network error or because the user used in the TMW or READ RFC connection is locked.
You have changed the STMS settings after the change cycle has been generated, for example, you have replaced the QAS system with a new one, but in the logical component, the new system has not been inserted.
You have changed the logical component settings in the project, for example, you have changed the QAS system role from ‘Target System’ to ‘Single System’.
As long as the lock is not caused by instable network connections, you can perform a configuration check to find the cause of the lock. To avoid these errors, you can take the following precautions:
Keep the RFC destinations to your managed systems stable, especially to the domain controller systems.
In case there are RFC errors and the project is locked, perform a configuration check. After you have solved the error, refresh the project to unlock it.