
The following import options exist in the Import Queue Web UI.
The options you have depend on which import method you have chosen (mass or single import) and whether you want to import ABAP or non-ABAP transports.
|
Option |
Description |
|---|---|
|
Select All Transports for Later Import |
The transports remain in the import queue after the import and can be imported again. This option is useful, for example, if you want to import all transports in another client and you have not activated extended transport control. |
|
Leave Transport in Queue for Later Import |
This causes these transports to be imported again in the correct order with the next import of all transports. This option is useful if you have to make preliminary imports for individual requests. This ensures that the objects of the request will be imported again in the correct version at the next regular import of all transports (prevents the overtaker problem). However, if you provide a system only with individual transports, this option is not useful since the transports remain in the queue after the import and have to be manually deleted from the import queue. |
|
Import Transport Again |
This transport is imported again even if it already has been completely imported. |
|
Overwrite Originals |
Objects are also imported if they are the originals in the target system. The object directory entry determines the SAP System where the original version of an object is located. Note This option is only relevant for ABAP transports.
|
|
Overwrite Objects in Unconfirmed Repairs |
Objects are also imported if they were repaired in the target system and the repair is not yet confirmed. Note This option is only relevant for ABAP transports.
|
|
Ignore Non-Permitted Transport Type |
The transport is imported even if this transport type was excluded by particular settings in the transport profile. |
|
Ignore Non-Permitted Table Class |
Data records of a table are imported even if the delivery class of the table does not permit the data records to be imported. Note This option is only relevant for ABAP transports.
|
|
Ignore Predecessor Relations |
You can choose this option if you want to import all the transports for one or several projects, but additional transports from other projects exist for which there are dependencies. This option is switched off by default, which means the project predecessor's relationships are checked before the import. The import only takes place if the project predecessor's relationships will remain intact. Note This option is only relevant for ABAP transports.
|
|
Ignore Component Check |
This import option means that transports 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 transport). You should only use this option if you are sure that the content of the transport is independent of the component version. Note This option is only relevant for ABAP transports.
|
|
Import Checks: Perform Predecessor Check |
The transports are only imported if there are no overlapping objects found between the selected transports and the transports that were previously added to the import queue, but which were not selected. Note The dialog box displays a warning message if this option is not selected.
|
|
Import Checks: Perform Downgrade Check |
The transports are only imported if none of the selected transports contains a version of an object that was exported earlier than those that have already been imported. Importing the object would result in a downgrade of the object. Note The dialog box displays a warning message if this option is not selected.
|