Applying Single Support Packages 
Use
If you want to update only particular software components that are deployed in the system and do not want to apply complete support package stacks, you can apply single support packages. The import time is shorter for single support packages than for support package stacks.
Prerequisites
...
You have downloaded the support packages you want to apply to the global EPS inbox directory <Drive>:\usr\sap\trans\EPS\in. For more information about SAP products, see SAP Service Marketplace at service.sap.com/swdc.
Procedure
...
1. Choose the Deployment tab, select the Single Support Packages indicator and choose Next.
Support packages that are available for deployment from the Inbox directory are displayed. By default, the target SP level is the latest available SP.
2. Select the support packages you want to apply.
3. If you do not want to apply the latest support package, from the Target SP Level dropdown box, select the SP level you want and choose Next.
In this step, the JSPM checks the deployment queue. The status of the selected support packages can be:
¡ OK
¡ WARNING
You can go on with the deployment.
You can view the details about the software component by choosing Show Details.
You can change the content in the global EPS inbox directory and go back to the Select Package Type wizard step.
¡ REVISE
You cannot go on with the deployment.
You can view the details about the software component by choosing Show Details.
You have to change the content in the global EPS inbox directory and go back to the Select Package Type wizard step.
4. If the status of the selected support packages is OK, choose Next.
You will be informed if the J2EE Engine will be restarted during the deployment.
If you have selected to update the kernel, you will
be prompted to stop any running dialog instances and close the Microsoft
Management Console (MMC). For more information, see 
Starting and Stopping
the J2EE Engine.
The JSPM starts the deployment of the selected support packages and the status changes to SCHEDULED. The deployment of the support packages can finish with the one of the following statuses:
¡ DEPLOYED
If you have selected to update the JSPM, when it has been updated, for the update to take effect, you will be prompted to restart it. If there are still support packages in status NOT DEPLOYED, JSPM will proceed with their deployment when you start it again.
Bear in mind that you must not change the content of the global EPS inbox directory before the deployment has finished.
¡ DEPLOYED WITH WARNING
The support package has been deployed but it is possible that it will not work properly with other deployed software components.
You can view the details about the support package by choosing Show Details.
You can also view the details about the support packages by choosing the Deployed Components tab (see Viewing the Deployed Components).
You can also view the log files.
¡ ERROR
An error has occurred during the deployment of the support package. You can proceed as described for a deployment, which has finished with status DEPLOYED WITH WARNING.
In addition, if you receive an error during deployment message, you have the following options:
If you have corrected the error, but not by changing the content of the global EPS inbox directory, you can choose Retry.
If you have corrected the error by changing the content of the global EPS inbox directory, you can choose New Deployment and try to deploy the support package again.
You can stop JSPM by choosing Exit.
Next time you launch JSPM, the Broken Deployment screen appears and you will have the two options: to retry the deployment or to start a new deployment.
¡ NOT DEPLOYED
JSPM has not attempted to deploy the support package. You can proceed as described for a deployment that finished with status ERROR.
5. If the deployment of the support packages has finished with status DEPLOYED, you can choose New Deployment or Exit.
Result
The support packages you have selected are deployed. On the Deployed Components tab page, the details about the SP level and counter of the respective deployed components are updated.
See also: