import-transport-requests-d2005d5.md

Import Transport Requests

SAP Cloud Transport Management allows you to flexibly manage the import of transport requests in transport nodes.

Prerequisites

• To run an import of all transport requests in the import queue, you need the authorization from the ImportOperator role. To run an import of selected transport requests in the import queue, you need the authorization of the TransportOperator or the ImportSelectedOperator role. For more information, see Security.

• You're in the import queue of the transport node where you want to run an import. For more information, see Prerequisites for Using the Import Queue.

Context

In an import queue, you have the following options to import transport requests:

• Manually start imports:

  • Import all transport requests in an import queue
  • Import one or more selected transport requests in an import queue
  • Import all transport requests up to a selected transport request

• Schedule imports of all transport requests in an import queue to run at regular intervals

• Enable automatic imports of transport requests as soon as they enter an import queue

Note:

It's possible that an option isn't available. This can happen if the content type you're importing doesn't support the option or if you don't have the necessary user permissions.

All transport requests with an Initial, Fatal, or Repeatable status can be imported.

Procedure

• Manually import transport requests:

  1. Ensure the filters in the import queue are set correctly to display all relevant transport requests.

  2. To start the import, choose one of the following options:

  • Import All

    To import all transport requests in the import queue, choose Import All.

    All transport requests are imported in the sequence in which they’re placed in the import queue.

    Caution:

    The import also includes any importable transport requests that may currently not be visible because of your filter settings.

  • Import Selected (not available for content type BTP ABAP)

    To import individual transport requests, select one or multiple transport requests, and choose Import Selected.

    The selected transport requests are imported in the sequence in which they’re placed in the import queue.

    Note that the import of individual transport requests can lead to inconsistencies in the target runtime if dependent transport requests aren’t imported. SAP Cloud Transport Management doesn’t perform any dependency checks on the selected transport requests.

  • Import Upto (available for content type BTP ABAP)

    To import all requests in the import queue up to a specific transport request, select a transport request, and choose Import Upto.

    The selected transport request and all previous requests are imported in the sequence in which they are in the import queue.

    Note:

    If relevant transport requests are hidden because of your filter settings, SAP Cloud Transport Management displays an error message. Adjust your filter settings to display the relevant transport requests, and restart the import.

  The import starts immediately.

• Schedule imports of all transport requests to run at regular intervals.

  For more information, see Schedule Imports.

• Enable the automatic import of transport requests as soon as they enter an import queue.

  For more information, see Enable Automatic Import.

Results

If the transport node has a content type and a valid destination assigned, the transport requests are imported into the runtime of the transport node and get a Succeeded status.

If transport requests are imported in virtual nodes, they are forwarded to the import queues of the target nodes. In the virtual node itself, they get a Skipped status.

If multiple transport requests of content type BTP ABAP are imported using Import Upto, and all requests contain references of the same software component, only the content of the selected request is imported. All previous requests get a Skipped status.

For more information, see Statuses of Transport Requests.

Note:

If a transport request with a Multitarget Application archive (.mta) is imported in a subaccount of the Neo environment, the archive is afterward visible in the Standard Solutions category in the Solutions page in the SAP BTP Cockpit of the subaccount. For more information on solutions, see Operating Solutions in the SAP BTP documentation.

Check the status and the logs to make sure that the import was successful.

For more information, see Options to Display Information about Transport Requests.

Transport Request Forwarding

Depending on the Forward Mode defined for the transport node, transport requests are automatically forwarded to the target nodes or not. For more information, see Create Transport Nodes.

If automatic forwarding takes place, the transport requests are forwarded into all target transport nodes according to the transport routes defined for the node where the import was started.

Forwarded transport requests are added to the end of the import queues of the target nodes. If any forwarded transport requests are already part of the import queue of a target node, they’re moved to the end of this import queue. The status of a moved transport request changes as follows:

• Initial remains Initial.
• Deleted, Error, Fatal, Skipped, Succeeded, and Warning change to Repeatable.
• Repeatable remains Repeatable.

If the Forward Mode is Manual, manually forward the transport requests as required. For more information, see Forward Transport Requests.

Related Information

Troubleshooting Issues when Transporting Multitarget Applications (MTAs)