Show TOC

Function documentationTask List Variants

 

A change cycle defines the system landscape (change control landscape and branch) and the transport tracks you use in Change Request Management. Each change cycle has a defined set of phases depending on its type. The phases define which activities are permitted as part of change control. The transport tracks are defined in the Transport Management System (TMS).

If you use Change Request Management, your systems are set up in such a way that you can only perform the transport tasks (create, release, and import transport requests) in Change Request Management. This is determined by the Central Transport System (CTS) project assigned to the transport requests, and the CTS status switch which defines that you cannot create, release, or import transport requests using transactions SE09 and STMS. Only the Change Request Management programs can perform these functions based on the task list assigned to every change cycle.

Features

There are two SAP standard task list variants that determine the import strategy of changes:

  • SAP0: Standard import strategy (recommended)

    Distinguishes between two types of import:

    • Normal changes are always imported into the system together (that is, all transport requests for a CTS project in the import buffer) in the order of their release. The transport requests are then removed from the import buffer.

      You can perform a preliminary import of normal changes to accelerate the transport process. In this case, the transport requests of the normal change stay in the import buffer.

    • Urgent changes are transported separately and as quickly as possible. After import, the transport requests of the urgent change stay in the import buffer. They are imported with other related CTS project transport requests in the order of their release, and only deleted from the buffer during the mass import.

    Note Note

    You must ensure consistency between urgent changes manually, that is, you must ensure that the import sequence of urgent changes matches the release sequence, especially, if they are interdependent.

    Because normal and urgent changes are imported together as part of the CTS project import based on their release sequence, any inconsistencies caused by urgent changes may be repaired.

    End of the note.
  • SAP1: Deletion of import buffer strategy

    All imports are handled like urgent changes, but the transport requests are removed from the import buffer after import. If you do not import in the release sequence, inconsistencies can occur. You cannot repair these by performing the CTS project import because the buffer entries no longer exist.

    Caution Caution

    Use this import strategy with caution. Use it only if you are making small changes that are not interdependent. Note that only the developer can determine which transports are to be determined if there are interdependencies. ln such a case, import the transport requests separately using this import strategy, and not as part of a CTS project import.

    End of the caution.