Controls the following activities in change control management over the whole duration of a project:
Requests for change and the resulting changes in the systems that are used in your project
Transporting changes to the follow-on systems
Change logistics, that is, which transports can be transported into the follow-on systems at which point in time
You create a project cycle for implementation, upgrade, and template projects.
From a technical perspective, the project cycle is a preconfigured service transaction (delivered by default as transaction type SMDV).
Note
The Maintenance Cycle is a special type of project cycle where it is possible to pass through the stages several times. It is created for maintenance projects.
You always create a project cycle for a project if you want to work with change transactions. You use the project cycle to control which changes activities are permitted in which phase. The project cycle phases determine the sequence of tasks in task lists. Through its phase structure, the project cycle offers an operational enhancement to the project plan.
The following functions are available by means of assignment blocks in the project cycle:
Project phases
For more information, see Phases in the Project and Maintenance Cycle.
Details
Contains general administration data for the project cycle, such as when and by whom it was created, and the current project cycle phase.
Text
For more information, see Using Texts and Text Templates.
Landscape
For more information, see Using the Landscape Assignment Block.
Related transactions
Contains links to the task list and all change documents that use this project or maintenance cycle.
Application log
For more information, see Using the Application Log.
You activate a project cycle for a project and thereby also activate the specific corresponding task list.
Note
Each project cycle has just one task list, which is used for the entire project and all corresponding change transactions.