(SAP Support Package)

You can only import SAP Support Packages by using transaction SPAM.

(Client transport)

Do not import client transports together with all the other requests in the import queue. Therefore, you must import all client transport requests before you can import the remaining requests in the import queue.

(Data file must be transferred)

The data file of the request is not yet in the transport directory.To be able to import the request, you must first transfer it.

More information: Adjusting the Import Queue

(Request must still be approved)

The request is in the QA worklist because it has not yet been approved completely.

More Information: TMS Quality Assurance.

(Request rejected)

The request was rejected while in the QA worklist.

(Request does not match component version)

The component version (including Support Package Level) at the time of export of the transport request does not match the component versions (including Support Package Level) of the system into which the transport request is to be imported. The component version of the system is either new (the Support Package Level is higher than that of the export system) or it is too old (you first have to have imported the Support Packages before you can import the request). You can display the detailed information by double-clicking.

(Request will not be imported)

These requests are not imported due to specific settings made in the transport control program, or because the system is managed by central CTS.

If you choose  Edit Display more , which displays more technical information, the column I (import flag) gives you a more precise explanation. F4 gives you a description of the various tp import flags.

(Request after end mark)

Requests after the end mark are not imported during the next import of all requests. The end mark is automatically deleted only when the next import has completely ended. Afterwards, the requests can be imported.

(Request is ready for import again)

The request was already imported into the target system beforehand. To avoid inconsistencies that can occur when changing the import order, this request is imported again during the import of all requests. Therefore, this request stays in the import queue until all the requests have been imported.

(Request waiting to be imported)

The change request will be imported into the target system during the next import of all requests.

(Import is scheduled)

The import of the request is scheduled to run in the background at a later point in time.

(Import running)

The request is currently being imported.

(Request already imported)

The request was imported into the target system. These requests will not be imported again during the next import of all requests.