Importing a Queue 
Support Package Manager offers you two scenarios for importing Support Packages or queues:
Test scenario
Before starting the import process, use the test scenario to detect any conflicts or problems (for example, repairs that have not been released), or any requirement for modification adjustments.
This scenario helps you to estimate and minimize the time and effort needed to import Support Packages. This scenario does not import any data into the system. If errors do occur, you can continue the import without correcting them.
You must choose the test scenario explicitly.
Note
After the test scenario has run, the queue is empty, and you need to define it again. You then have to choose the standard scenario explicitly.
Standard scenario
The standard scenario imports all Support Packages in the queue. If errors occur, you have to resolve them before you can continue with the import.
If you have chosen the standard scenario, you can also choose between the conventional import mode and the import mode downtime-minimized in order to reduce the downtime.
You have already defined the queue.
To set the test scenario, choose .
On the Import Queue tab page, choose Test and define the other settings for the import.
Choose .
You can also use this function to restart a terminated import.
The status line informs you of the progress of the test import and the current Support Package Manager phase. You may have to perform a modification adjustment during the import (with transactions SPDD or SPAU). Note that the modification adjustment is only available in display mode. You can only perform it if you are importing the Support Packages in the standard scenario.
To set the standard scenario, choose .
On the Import Queue tab page, choose Standard and define the other Settings for the import.
Choose the import mode you require.
Choose .
You can also use this function to restart a terminated import.
A dialog box is displayed, where you can select the Start Options. Define the start options you require and confirm the dialog box.
Support Package Manager continues processing with your chosen import mode and start options.
Conventional Import Mode
If you have accepted the standard options without making any changes then the import starts after you have confimed the start options. The Support Package Manager executes the entire processing in dialog. Since the whole import process is run through in this case without stopping, your system must already be non-productive at this time.
Note
To bring the system to a non-productive status in an orderly way, reschedule all scheduled background jobs using the BTCTRNS1 report and let any background jobs that are running complete, or terminate them manually. Prompt all users to close any transactions they are working in and to log off from the SAP system.
If you have selected a start time or Continue Manually for module Import 2, your system can stay in production operation until module Import 2 starts.
After starting the import, the program runs through a Support Package Manager. If errors occur in any of these phases, the import process terminates, and a description of the error is provided. When the problem is corrected, you can continue with the import.
Firstly, the Support Package Manager performs all the preparation and test steps (module Preparation). If any errors in this module cannot be resolved, you can reset the queue.
Note
For more information on the check steps in the Preparation module, see Checks with Importing a Queue.
Then it executes the import steps of the Import 1 and Import 2 modules.
Caution
Since the database is already changed in these phases, you cannot reset the import once the Import 1 module has started. You have to continue it after correcting any possible errors.
Import Mode Downtime-Minimized
If you have accepted the default start options, your system can remain productive, as Support Package Manager tells you explicitly when to stop production operation.
Firstly, the Support Package Manager performs all the preparation and test steps (module Preparation). If any errors in this module cannot be resolved, you can reset the queue.
Note
For more information on the check steps in the Preparation module, see Checks with Importing a Queue.
It then runs through the import steps that can be performed during production operation (module Import 1).
Caution
Since the database is already changed in these phases, you cannot reset the queue once the Import 1 module has started. You have to continue the import after correcting any possible errors.
The development environment is blocked when module Import 1 starts, thus ensuring that modifications do not endanger the consistency of the system. Support Package Manager then displays a dialog box prompting you to stop production operation for the next import module (Import 2).
Set your system to a non-productive status.
For this, cancel any background jobs using the BTCTRNS1 report and, if necessary, allow any running background to complete, or teminate them manually. Prompt all users to close any transactions they are working in and to log off from the SAP system.
To continue the import, choose . This module (Import 2) activates the inactively imported objects and imports the remaining objects from the Support Packages in the queue.
Once this module has been completed, Support Package Manager informs you that you can restart production operation in your system.
Note
This applies only if you have made either no or very few modifications to SAP objects. Otherwise the modification comparison must be executed before the productive status is restored.
If you have made modifications to SAP objects, Support Package Manager prompts you to perform a modification adjustment.
You must adjust Dictionary objects immediately (with transaction SPDD). As far as Repository objects are concerned, you can either adjust them now or later (with transaction SPAU). To do this, proceed as described under Adjusting Modifications.
To complete the import process, choose Import Queue again.
During the next import module (Clean Up), post processing steps are performed. The installation process is complete.
Note
You can restore the productive operation in parallel to this import module, or you can start with the preparation activities for restoring the productive operation. (for example, execute ABAP Mass Generation with SAP Load Generation). You can schedule the previously canceled background jobs using the BTCTRNS2 report.