Start of Content Area

Background documentation Starting an Import: Options  Locate the document in its SAP Library structure


All the possibilities for starting an import in TMS are listed here. The options you have depend on which import type you have chosen (project or individual import, import all requests, transport workflow).

      Select All Requests for Later Import

The requests remain in the import queue after the import and can be imported, for example, into another client. This is only useful if you have not switched on extended transport control, but you want to provide several clients with requests.

      Leave Transport Request in Queue for Later Import

This causes these requests to be imported again in the correct order with the next import of all the requests. This option is useful if you have to make preliminary imports for individual requests. This prevents older objects from being imported at the next regular import of all the requests (overshooter problem).

However, if you provide a system only with individual transports, this option is not useful since the requests remain in the queue after the import and have to be manually deleted from the import queue.

The option Leave transport request in queue for later import is activated as a default only for Customizing requests and transportable change requests.

      Import Transport Request Again

The transport control program also imports the transport request if it already has been completely imported.

      Overwrite Originals

The transport control program also imports objects if the objects are the originals in the target system. The object directory entry determines the SAP System where the original version of an object is located.

      Overwrite Objects in Unconfirmed Repairs

The transport control program also imports objects if they were repaired in the target system and the repair is not yet confirmed.

      Ignore Non-Permitted Transport Type

The transport control program imports the transport request if this transport type was excluded by particular settings in the transport profile.

      Ignore Non-Permitted Table Class

The transport control program imports data records of a table even if the delivery class of the table does not permit the data records to be imported.

      Ignore Predecessor Relationships

You can choose this option if you want to import all the requests for one or several projects, but additional requests from other projects exist for which there are dependencies. This option is switched off by default, which means the predecessor's relationships are checked before the import. The import only occurs if the predecessor's relationships will not be damaged.

      Ignore Non-Matching Component Versions

This import option means that transport requests can be imported even if their component version does not match the current component version (including Support Package Level) of the system. This is the case if the component version of the system is either new (the Support Package Level is higher than that of the export system) or too old (you first have to have imported the Support Packages before you can import the request). You should only use this option if you are sure that the content of the transport request is independent from the component version.


End of Content Area