Performing Special Transports

An import is performed with a single tp call that imports all waiting change requests:

tp import all <sapsid>

tp automatically ensures that change requests are imported in the correct order (in their export sequence).

However, in practice it is often necessary to give individual change requests priority.

Particularly with priority change requests, there are two aspects which can cause problems:

• Does the change request that is given priority overtake another change request that contains the same objects, but in an older version?

• In which order do the change requests have to be imported, if there is a delivery system?

If you are sure that no change requests with older versions of the same objects are overtaken, then these individual imports do not cause problems.

Otherwise, you have to ensure that the objects imported with an individual transport into the R/3 System are not overwritten by an older version, when the regular import of all waiting requests is started.

1. Perform individual imports with the Unconditional Mode 0 (U0), except in the special situations mentioned above:

   tp import <change request> <sapsid> U0

   In this mode, the change request remains in the list of transports registered for import. Therefore, when the regular transport takes place, the request will automatically be imported again.

   This is why change requests that are automatically forwarded to other R/3 Systems are reimported, even if they have already been transferred to the systems as individual imports. This guarantees that export and import sequences are always the same.

2. Do not subsequently change an object that has been included in an individual import (for example, by repairs). Experience has shown that the authors of a change request do not expect their repairs to be overwritten by a repeated import. If necessary, inform the authors of individually imported change requests of the possible consequences.