Closing the Task List

Each project you manage with Change Request Management, and each task list associated with it, has a phase model of its stages. You can subdivide your projects and task lists into cyclical time periods, for clarity. Each project cycle is represented and controlled by a task list.

Each task list must run through all phases of the cycle in a fixed sequence. You can reset task lists to previous phases, but you can neither return to the initial phase, nor leave the last phase. There can only be one cycle at a time for your project, so there is only one active task list. You must first finish the current task list before starting a new cycle.

Note Note

You switch from one project phase to the next with the required action in the project or maintenance cycle in the WebClient UI. This procedure describes how to use the maintenance cycle to switch project phases. Example: In a three-system landscape, all transport requests for urgent changes that have the status To be Tested are in the import buffer of the production system. If you switch the phase in the task list and not in the maintenance cycle, the system does not issue a warning, and the urgent changes would be imported into the production system without being tested. If you switch the phases in the maintenance cycle, the transport requests are checked. The user is informed, and can act accordingly.

End of the note.

When you want to activate Change Request Management for a project, one of the prerequisites is to create an IMG-CTS project in the development system for each logical system. A CTS project is a container for all transport requests for the logical system, and is therefore an attribute of each of these transport requests. When you finish a task list, the CTS project separates itself from the system and is no longer available.

In production processing, it is often difficult to complete all change plans in a system and release CTS project transport requests, at the same time. So when closing a project or maintenance cycle, Change Request Management allows you to release the current CTS project and remove the CTS project from the open, not release, transport requests. Then, when creating a new project or maintenance cycle and a new task list, a new CTS project is created and the system copies the saved transport requests to the new CTS project.

This graphic is explained in the accompanying text.

Completion Task List with Transfer of Transactions and Transport Requests

Prerequisites

You have created a task list that is ready to be completed.

Procedure

To complete a project or maintenance cycle, go to the cycle in the WebClient UI and via Actions, switch the phase of the cycle until you reach the Competed phase.
You go to the Checks to Complete the Cycle.

In the overview, the system lists the checks it performs, in chronological order, before setting the status to Completed:
- Checks that must be passed for completion are under Required. Resolve any errors and repeat the completion.
  If a check is not obligatory, you can ignore any errors that occur in it, and close the task list anyway.
- You can display a description of the check under Help.
To start the checks, choose Continue.
While performing checks, the system displays messages about the checks steps, the possible consequences, and possible courses of action, in dialog boxes .

The system displays a message if it cannot complete a phase for technical reasons.

Note
You can cancel the completion process if messages and warnings occur.

End of the note.
You can also perform the checks separately, by performing the task Completion of Maintenance Cycle, in the group General Completion Tasks, in the task list. You can see the check results in the monitor, in the daily overview, by double-clicking on the scheduled instance.
All checks are displayed at the start of an overview dialog. If a check in this overview is flagged as required, you cannot skip it, i.e. you can then not complete the task list. If a check is not obligatory, you can ignore any warnings that occur in it, and close the task list anyway. If you need more information than the check short text, choose Help.
If the system has performed all checks, if at least the obligatory checks have been passed, and if you continue with the completion process, the system then starts it.
1. The system logs the check results, and actions that it performs internally.
  
  Note
  You can display the logs in the overview display of existing task lists in the application log, in transaction /TMWFLOW/MAINTINST. Navigate to the tab page with your project type (usually the maintenance project), choose all cycles by choosing Status, select a task list, and choose Messages about Changes.
  
  To show the completed task list in the overview, choose Status, to include completed task lists.
  
  End of the note.
2. During the completion process, the system saves your changeable transport requests, open processes, and urgent correction task lists. When you create a new maintenance cycle, these processes and objects are automatically assigned to it, so that you can continue to use them.
  These processes and objects are:
  - 'Urgent Change' processes
  - 'Normal Change' processes
  - 'Default Correction' processes
  - 'Urgent Change' task lists
  - Not-released transport requests
  - Transport requests which have not yet been imported into all production systems
  - Transport requests which have not been retrofitted, if this function is available
  Note
  The system also saves the transport requests in import buffers and not yet imported into the production systems, i.e. the CTS project of the completed cycle as well as the current CTS project.
  
  End of the note.
  
  Caution
  After completing the task list, your changeable transport requests are no longer assigned to a CTS project. It is technically possible to release these transport requests manually. Do not do so, because the adjustment to the procedures in which the transport requests were created, will fail.
  
  End of the caution.
To be able to edit the changeable transport requests, open processes, and task lists for urgent changes again, create a new task list for the project in project administration; choose the System Landscape tab page, the Change Management tab page, and Create Task List.
The system assigns all saved objects to the new task list or CTS project.

The system logs the assignment information. To display the log:
- In project administration, choose the System Landscape tab page, the Change Requests tab page, and Application Log.
- In the task lists overview display for the new task lists, choose Messages at Time of Creation.

Result

You can continue to use the existing procedures and transport requests in the new cycle with the new task list.

More Information

Phases in the Project and Maintenance Cycle