Deploying Transports of a Feature

After you've assigned transports to a feature, you can deploy all transports that have the status Released or Deployed.

Prerequisites

The following prerequisites are only relevant for CTS and CTMS.

  • The status of the feature is In Implementation, In Testing, or Ready for Production.

  • The status of the transport is Released or Deployed in <system - client>. If any transport has the status Scheduled In, the Deploy button isn't active.

  • The target system for at least one transport is filled.

  • You have the Deployment Manager role.

For CTS, make sure you've installed ST-PI 740 SP31 and SAP Note 3623614 Information published on SAP site. This provides access to the latest functionalities.

For more information about the integration of deployment tools, see Integration of Deployment Tools.

Context

The target column always indicates the system and client where a transport will be deployed into. There are three cases:

  • Target shown in black: indicates where this transport request will be deployed into next.

  • Target shown in gray: indicates that this transport can't yet be deployed into this system.

  • No target: production system and client reached; no further deployment possible.

Target systems include quality assurance, pre-production, and production systems from a system group, which are assigned to the project via the deployment plan. The deployment is performed using the landscape defined in TMS or CTMS, not the one defined in the system groups.

For more information about system groups and deployment plans, see System Groups.

Transport Sequence

Transports are always imported according to their order in the TMS import queue and with the TMS import option Import Transport Request Again. You can't manually change the transport sequence.

Transports assigned to a feature that haven't been imported to a quality assurance system are deployed into a quality assurance system first. Then, they’re deployed to the productive system as a package. For example, you want to correct a test defect and retest in your quality assurance system. To do this, you switch the status of your feature to In Implementation and create a new transport. Once you release the transport and deploy it, the import is only into your quality assurance system to correct the defect. There's no deployment into your pre-production or production systems.

When you schedule the deployment for one or more features, the Change and Transport System (CTS) transports are deployed in the following way:

All transports are deployed together according to the import subset method. The import subset method is an import all approach limited to the transports of the selected features. This means that every technical import step is performed for all transports before the next import step is performed. If you have more than one transport with the same object, then the latest version of the object that was exported or imported to the previous system is the active version at the end of the import. This ensures a correct sequence. For more information, see Performing Imports.

If a Component Version Mismatch error in the SAP Cloud ALM import logs prevents your deployment, you can disable the component version check. This can be applied to the entire system or to specific software components, allowing to continue your deployment. For additional details about the component version check and setup, see SAP Note 1742547 Information published on SAP site.

Procedure

  1. In the Transport section, choose Deploy.

    This moves the transports to the next transport target and/or to the level of the most advanced transport of a feature.

  2. Continue with the deployment until the transport is in your production system.

If you encounter issues, refer to Issues and Solutions.