Importing Support Packages Using SPAM (SAP Library - SAP Patch Manager (SPAM) (BC-UPG-OCS))

Importing Support Packages Using SPAM

Use

Use Transaction SPAM to import Support Packages into your system, whether they come from SAPNet - R/3 Frontend, SAPNet - Web Frontend or from Collection CDs.

Prerequisites

User:

You must have the relevant authorization for the SAP Patch Manager.

You must be logged on to Client 000.

You must have called Transaction SPAM.

Choose Tools ® ABAP Workbench ® Utilities ® Maintenance ® Patches, or enter the transaction code SPAM.

The initial screen gives an overview of the status of the last queue that was imported. If the Support Package import is incomplete, the last (terminated) step processed by SPAM is displayed.

System:

Check the correct function of the transport tools by choosing Utilities ® Check transport tool.

Make sure that there is enough space in the transport directory (size of the OCS files multiplied by 2) (use Transaction AL11 to see the profile parameter DIR_TRANS or use Transaction SE38 and the report program RSPARAM). It is particularly important that there is enough space in the subdirectories trans/EPS/in and trans/data .

Use the newest SPAM update.

Check if the SPAM update offered in SAPNet - R/3 Frontend or SAPNet - Web Frontend is newer than the one in your system. (The version of the SPAM update in your system appears in the title bar of the SPAM screen.) To avoid problems when importing Support Packages, we recommend always first importing the newest SPAM update. You import a SPAM update in the same way that you import Support Packages.

You cannot have any incompletely imported Support Packages in your system.

To check this, under Directory choose Aborted Support Packages and then choose Display. No Support Packages should appear. Under the section Package, the status should display a green traffic light. If this is not the case, look at the detailed status and log information of all Support Packages found in the system. To do this, choose Goto ® Status and/or Goto ® Log.

Activities

Load the Support Package.

Define a queue.

Import the queue.

If necessary: Adjust modifications.

Check logs.

Confirm the queue.